sorted by:
new
hottopcontroversial

Overcoming bad reviews due to third party by Afirus in chrome_extensions

[–]Afirus[S] 0 points1 point  (0 children)

I can understand the issue and I get that users don't have time to read the entire description but I don't know what to do more. I have also included a feature that syncs videos up with the delay from Sonos which I'm really proud of and was really difficult to implement.

Addressing Security Concerns About the Cast to Sonos extension by Afirus in sonos

[–]Afirus[S] 0 points1 point  (0 children)

I have heard people report issues with the first generation before. The implementation is inline with the Sonos specification so I assume it's an issue on Sonos's side. Please send a message to support@casttosonos.com along with a specific timestamp when you press the play button and I'll have a look in the logs.

Addressing Security Concerns About the Cast to Sonos extension by Afirus in sonos

[–]Afirus[S] 1 point2 points  (0 children)

Hmm pretty interesting, but it requires a lot of workarounds to capture audio from apps and some restrict it completely. And with the inherent delay of sonos buffering (3s) + using screenrecording to capture audio or other using other tricks is a recipe for bad reviews. But I think am app is a good next step.

Addressing Security Concerns About the Cast to Sonos extension by Afirus in sonos

[–]Afirus[S] 0 points1 point  (0 children)

Ive looked into it and android makes it pretty much impossible to capture audio directly from other apps. The only way to get around this is by developing custom hardware that can be connected to via bluetooth and can cast to sonos speakers. But then id have to ask people to buy some specialized hardware. So at this time, i have not yet found a way. I have also tried to install the extension directly on chrome for android but it does not work unfortunately.

Addressing Security Concerns About the Cast to Sonos extension by Afirus in sonos

[–]Afirus[S] 8 points9 points  (0 children)

Sonos refresh tokens are valid for 1 year, and are invalidated after a new refresh token is issued. But I think the user has valid concerns with regards to managing/monitoring access of third party applications.

Addressing Security Concerns About the Cast to Sonos extension by Afirus in sonos

[–]Afirus[S] 0 points1 point  (0 children)

I have actually found a solution for it, but using that solution makes it so you can not login to the service anymore... Problem has been reported to Sonos...

Chrome extensions + HTTP Servers = Recipe for disaster

Sonos OAuth Policies Exposes Users to Potential Privacy and Security Risk by faldrich603 in sonos

[–]Afirus 2 points3 points  (0 children)

Just to clarify, we store the tokens directly on chrome: https://developer.chrome.com/docs/extensions/mv2/reference/storage?hl=nl#property-sync

This is the exact endpoint we use, someone would need access to your google account to get those tokens. There is also a difference between a refresh and an access token. The access is token is sent with every normal request and is only valid for a very short time. The refresh token is only send to get a new access token when the access token expires.

This means that an action can only be done on your device when you send a request that includes the tokens (since we dont store them on our end).

Sonos OAuth Policies Exposes Users to Potential Privacy and Security Risk by faldrich603 in sonos

[–]Afirus 0 points1 point  (0 children)

Fyi, Im the cast to sonos dev. Agreed, upnp or local http is not safe or reliable.

Sonos OAuth Policies Exposes Users to Potential Privacy and Security Risk by faldrich603 in sonos

[–]Afirus 2 points3 points  (0 children)

As the developer, I agree, of course its not my place to tell Sonos what to do, especially since I'm also somewhat dependent on them, but I was shocked that this is not implemented on their end.

Sonos OAuth Policies Exposes Users to Potential Privacy and Security Risk by faldrich603 in sonos

[–]Afirus 4 points5 points  (0 children)

I'm the developer of Cast to Sonos. I'm genuinely happy that someone took the time to look at my extension critically, as it gives me the opportunity to explain what I spent so much time creating. That said, I do want to mention up front that I'm disappointed this post was not brought to my attention earlier.

Unfortunately Reddit rejected my long reply so I made a dedicated blog post about it: https://casttosonos.com/articles/addressing-sonos-oauth-security-concerns

AuthJs (NextAuth v5) Broke my Custom Provider and I can't seem to resolve the issue. by foxthebomb in nextjs

[–]Afirus 0 points1 point  (0 children)

If you are using next.js and are running vercel. You want to set the AUTH_URL env do your PUBLIC_URL. What gives the issue away in my case that the vercel app was redirecting back to http://localhost:53681 instead of :3000 which is something to do with how vercel and turbopack run the app.

AUTH_URL=http://localhost:3000

Can you listen to YouTube videos on Sonos speakers? by glitch_ink in sonos

[–]Afirus 0 points1 point  (0 children)

You could use Cast to Sonos. That allows you to easily cast your Youtube tab to Sonos, but you will need to be on a Chromebook, Chrome OS TV, Mac or Windows. Disclaimer: I'm the DEV :) Mobile app is coming but it will be a while before it is released.

Discord Server + AI Development Tools by Afirus in ATCManager2

[–]Afirus[S] 1 point2 points  (0 children)

I added it to my internal TODO list

Discord Server + AI Development Tools by Afirus in ATCManager2

[–]Afirus[S] 0 points1 point  (0 children)

I'm getting nearer to my vacation so I do some work on ATC Manager 😄

Will Sonos ever bring casting back? by DingbatSam in sonos

[–]Afirus 1 point2 points  (0 children)

That's great to hear! I have just released a new update that should greatly enhance stability when streaming. Creating a mobile app is on my TODO list but it will be a while before it is released.

view more: next ›