This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.
It's definitely laudable. But does raise the question... why was the API not open in the first place.
Bose has released API docs and opened the API for its EoL SoundTouch speakers
321–330 of 416 posts
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#322This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#323Earlier quoted context omitted.
Would you elaborate? Because my understanding is that Apple has offered outstanding support for older devices in terms of iOS support for quite old devices.
Whilst the support might be "outstanding" - the discussion is what happens once devices are no longer supported.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#324Earlier quoted context omitted.
Bose should not receive praise for this move. Bose only took this action after community backlash. In an older version of their end-of-life announcement, most functionality of the speaker systems would have removed and transformed the devices into dumb-speakers/amps. Good that they changed their statement and took the right action. Even better for the community for stepping up and 'forcing' Bose to do so. Sources: ht…
> Bose should not receive praise for this move. Remind me of any other vendor in recent history that end of lifed a hardware product and then open sourced it whether they got backlash or not. Because I can’t think of a single one. So yes, Bose absolutely deserves praise.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#325Earlier quoted context omitted.
Build quality of Bose products is good in my opinion. The headphones are alright but so are Sony, Plantronics and Apple. I love the sound of Airpods Pro in particular even if they don't want to stay in my ears [1] and the pairing experience even with the iPhone isn't what I expect of >$100 headphones in 2016. If you want really good stereo or 5.1 sound there is no substitute for big speakers that can move a lot of ai…
If you haven't tried foam replacement tips, they make a world of difference for me. I couldn't use the airpods (non-pro) at all. I could barely use the silicon tipped pros. But when I put a foam tip on them it not only blocks out ambient sound better, they stay in place. Unfortunately the foam wears out rather quickly and I replace them around three times a year.
On the newest ones, the tips have a foam core inside them.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#326Earlier quoted context omitted.
Please suggest better alternatives
Beyerdynamic DT1990s run circles around consumer-grade stuff.
I recommend HiFiMan Sundara/Ananda if they fit your head and there aren't any CPU fans in your room.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#327As others have said already, they are just un-obscuring the server API and restoring local control to your speakers when they discontinue the service. There is nothing noble about this, it is almost least they could do. I walked away from a large investment in Sonos gear over forcing legacy equipment into the cloud, this sort of thing is why.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#328This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.
Bose should not receive praise for this move. Bose only took this action after community backlash. In an older version of their end-of-life announcement, most functionality of the speaker systems would have removed and transformed the devices into dumb-speakers/amps. Good that they changed their statement and took the right action. Even better for the community for stepping up and 'forcing' Bose to do so. Sources: ht…
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#329Earlier quoted context omitted.
Would you elaborate? Because my understanding is that Apple has offered outstanding support for older devices in terms of iOS support for quite old devices.
Whilst the support might be "outstanding" - the discussion is what happens once devices are no longer supported.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#330Earlier quoted context omitted.
> Bose should not receive praise for this move. Remind me of any other vendor in recent history that end of lifed a hardware product and then open sourced it whether they got backlash or not. Because I can’t think of a single one. So yes, Bose absolutely deserves praise.
Google refunded all Stadia purchases, both hardware and software, after they discontinued the platform/product. Then they added functionality (the ability to operate the controller as a generic Bluetooth controller) afterward to keep the hardware from becoming e-waste.