I think it would be a good idea to tax companies significatnly when bricking their devices, it's creating e-waste. Open sourcing them like this would be a way for them to avoid fines.
Bose has released API docs and opened the API for its EoL SoundTouch speakers
31–40 of 416 posts
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#32This 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.
I agree, but there can be IP rights involved that make this difficult.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#33Providing API specs is not open-sourcing them. Where's the source code?
Firstly, the source code is probably being used on newer devices, so Bose would not like sharing their proprietary solutions which might contain thirds party code they cannot share.
Secondly, these devices are basically one step above embedded. It's highly unlikely you can load and run anything custom on them.
Since they are opening up the API, you can keep using them for what they were made for, which is at least a solid basic liberty
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#34Meanwhile they "bricked" the login in their app for some countries arbitrarily: https://www.reddit.com/r/bose/s/ijKcvl09FW
Now users like me can't configure their devices (because the login is mandatory for using anything in the app). Some users report they aren't even able to use it with a VPN.
The over-reliance on closed source apps with mandatory logins for configuring devices you own must come to an end.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#35Good for them. Makes me more likely to consider buying a Bose in future, not just because I know it won't be bricked, but also for the environmental impact of this. Kudos.
If only their sound signature was a bit better... they went all in on engineering tricks to make things small and cheap to produce, but it shows in their sound quality. Their QC headphones are the best in noise cancellation, and the sound quality is good enough that they're my pair of wireless headphones.
A long while ago i heard something (that might have been a urban myth) about Bose putting useless weight into their headphones to make them appear more "substantially professional". Is that a myth or they have pivoted towards actual quality since early days?
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#36The released documentation: https://assets.bosecreative.com/m/496577402d128874/original/... From a quick glance it looks like you are just able to do high level playback controls, similar to what you'd do using their on-device UI. Perhaps that's enough?
I mean, suppose a CD player only used proprietary CDs. If the company dropped support and opened it to every other CD brand, would you complain that you can't load cassettes? Or burn ISOs with it?
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#37Hey Sonos, this is how you handle old products, and this is why most of us wont touch your hardware ever again.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#38This 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.
I agree, but there can be IP rights involved that make this difficult.
Sure but that should be an up front conversation. "OK, how do we make sure as few of these turn into bricks?"
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#39Earlier quoted context omitted.
Backtracked or not I won't ever buy Sonos because of that move.
Yeah, I couldn't even get the damn thing to work reliably when it was new. Oh but you can rest assured that it had no problem exfiltrating all that precious data of mine about what I was doing, and any other things they could suck out of my Android phone. No way in hell will I EVER buy another Sonos product.
we've got a pair of Sonos One speakers airplay(2?) connected to our Apple TV (recent generation): the sound is excellent but connection over airplay regularly is dropped, which might be Apple's doing, since they may well favor device testing with homepods. it drives some here to anger...it is a pisser because the sound quality is great.
I noticed Sonos speakers are featured in some upscale cars now, Audi for example.
Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers
#40Earlier quoted context omitted.
If only their sound signature was a bit better... they went all in on engineering tricks to make things small and cheap to produce, but it shows in their sound quality. Their QC headphones are the best in noise cancellation, and the sound quality is good enough that they're my pair of wireless headphones.
A long while ago i heard something (that might have been a urban myth) about Bose putting useless weight into their headphones to make them appear more "substantially professional". Is that a myth or they have pivoted towards actual quality since early days?
There used to be a whole culture of bose kind of being a-holes. (Like 20 years ago.) I used to work at CNET back then and there was a kind of "yeah bose is ok" kind of vibe but it was always tinged with "but they want to sue you if you say mean things" whether they did or not.
As far as I know now, things have changed substantially. I would assume this includes engineering quality and honesty.
This bricking avoidance seems like another note in that positive direction.