The soundtouch web api which is what was "open sourced" was already an existing thing for a long time. You just had to access it from the bose developer portal I think. I don't think anything actually happened here. I'm so surprised that HN is excited about this story because nothing seems to have been released.
> We’re making our technical specifications available so that independent developers can create their own SoundTouch-compatible tools and features. The documentation is available here: SoundTouch API Documentation (https://assets.bosecreative.com/m/496577402d128874/original/...).
AFAIK, the soundtouch web API was already accessible via some bose developer portal. It doesn't seem like they are open sourcing anything. This API just allows you to make basic requests to do things like change volume on the speaker.
To support the smart features of the SoundTouch speakers, we would the soundtouch user management service. Speakers connect to this very frequently and its where refresh tokens for music services and presets are stored. The speaker firmware itself has lots of source code, including the bit to handle music services and playback. There is an abstraction layer for music service APIs. There is a process on the speaker that reaches out to a music service registry, which is an index of bose music service adapters. Each of these adapters essentially proxies a music service like tunein, spotify, and even the "stream a custom station" feature.
If bose open-sourced the speaker firmware, we could make a firmware build which talks to a 3rd party user management service, and reaches out to a 3rd party music service registry. Then we could add and maintain music service playback for the community. But there is no open sourcing of any actual code here and this soundtouch web api cannot change the URLs on the existing firmware of the user management service or the music service registry.
So to my eye this story seems misleading and just some PR nonsense. It's a little frustrating reading all of the "great job, Bose!" comments here like anything was actually done... Disclaimer: I used to work at Bose.
Thanks for this link. Opening reddit links on mobile is very frustrating for me because it opens the app and messes with the browser back button for me. Not sure if others have that problem too.
That's because you're not supposed to open reddit links anymore, you can just share your content directly with AI companies and ad brokers and cut out the middleman.
On iOS Safari, long-press the link and select Open (or Open in Background). That will open the link in the browser instead of in the app, and Safari will remember that preference for the app. Select Open in Reddit to revert.
I'm a grovelling Linux fiend and usually support related posts. I tried to visit the url and saw it was blocked. Didn't want the post to die so archived it asap.
Note too, that NextDNS blocks archive.is et al by default unless you manually add redirects.
I’ve noticed that even on VPNs, US exit points sometimes block archive.is. Not sure if that is DNS related or what. Non-US VPN exit points don’t seem to be blocked at those times that the site navigation fails on US ones.
I believe NextDNS is headquartered in the US, which may be related to the site nav issues we’re both experiencing.
Curiously, uBlock Origin and my blocklists seem to block content on archive.is from loading from mail.ru, which may be related to the blocks, but I have never heard anyone on HN or elsewhere mention this, so I am, so that it can be known and explained if any explanation exists for why mail.ru scripts on archive.is are present. I don’t seem to see those scripts on the Tor version of archive.today, which archive.is is a mirror of today; apparently the original domain is the .is one, in any case.
Consider my curiousity piqued!
More info about the archive.is|.today mirrors including the Tor (.onion) version of the site are on the Wikipedia entry for the site:
I'm sorry I was unable to add anything. Keep digging though and it'll all soon be clear. And if you find anything substantial, butt into one of my comments sometme and let me know
Appreciate the feedback, I will do so more research and see what I can turn up. I had a quick question if you have a sec.
> Note too, that NextDNS blocks archive.is et al by default unless you manually add redirects.
Can you explain a bit about what you had to do to get archive.is to work with NextDNS? I have used their service/app before, but I’ve never dug into redirects via NextDNS, as I didn’t even know that was a thing you could do via the service.
I mean that the page doesn’t even begin to load. I get early and often Google reCAPTCHAs on archive.is and its mirrors under normal operation over HTTPS/Tor, but I was referring to the site not loading in at all, and getting some kind of PTR/SSL error iirc when it happens, which is most/all of the time when using US VPN exit points over HTTP(S). I don’t experience these errors at all over Tor, because their Tor site doesn’t use certificates. I run HTTPS-only mode in the clearnet, so perhaps others don’t experience this issue on their machine(s), but I don’t want any kind of MITM and/or downgrade attacks to slip through the cracks, just in case.
On Android "Redreader" is the only third-party Reddit app that somehow survived the third-party-app-purge. Still free and open source, and much more pleasant than the official one.
The day Apollo died is the day I stopped logging in to Reddit, or going there regularly. I use old when I have to go there for more than a top-level reply from a Google search. I want to say they really goofed up, but tbh Reddit seems fine without me. I’m mostly fine without it, but I do miss a few of my communities.
Thanks for this, I was resorting to creating a PWA on old reddit (which has horrible ergonomics for mobile) per subreddit (you can't rename them so I remember which is which by position) thinking all the reddit clients that don't require login are gone.
reply