Live data from Hacker News

Bose has released API docs and opened the API for its EoL SoundTouch speakers

arstechnica.com

51–60 of 416 posts

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#51

Providing API specs is not open-sourcing them. Where's the source code?

Source code to what? This is making them controllable. The headline may be inaccurate, but I'm not clear on what source code you'd even want. To the firmware do you mean? A documented API seems like the most useful option here.

The title of the article is misleading. The API documentation is indeed useful but I wouldn't call publishing the API documentation open source.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#52
Reword a public announcement [1], slap on a misleading title, put it behind a cookie banner and paywall and boom - Journalism! "Bose is releasing documentation for EOL smart speaker HTTP API" would be more apt. Not even Bose is claiming that anything has been open-sourced in their statement. Titling the section "Open-source options for the community" is as close as they come to that.

Still, props to Bose for actively helping to keep their old devices usable.

[1] https://www.bose.com/soundtouch-end-of-life

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#53
This is not open sourcing any actual software or hardware it is “open-sourcing the API documentation for its SoundTouch smart speakers”. You might be able to point them at an alternative back-end¹ if you want the cloud features, but that will need to be written from scratch rather than being forked from code provided by Sonos.

> When cloud support ends, an update to the SoundTouch app will add local controls to retain as much functionality as possible without cloud services

This is a far bigger move than releasing API information, IMO bigger than if they had actually open sourced the software & hardware, from the point of view of most end users - they can keep using the local features without needing anyone else to maintain a version.

--------

[1] TFA doesn't state that this will be possible, but opening the API makes no sense if it isn't.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#54
post #32

Earlier quoted context omitted.

I agree, but there can be IP rights involved that make this difficult.

They're just publishing API documentation. No source code of the device got published. At least people can create their own implementation of the API tho.

If the publish the API for the server, as well as allow the device to specify the API hostname to connect to, that's all I need. We can write our own server implementation fairly easily, and this saves us the hassle of having to reverse-engineer the API, plus makes setup much easier if we can just tell the device where to connect.

I wish more manufacturers would unlock their devices for local use when they don't want to support them any more. Or maybe even, hear me out, before support ends! Maybe we could even vote with our wallets and buy open stuff instead of walled gardens.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#55

Earlier 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?

That was Beats. Pre acquisition IIRC, it was years ago.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#56
post #8

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.

This is the way! (And should be the law, maybe enforced by mandalorians taking greedy CEOs!)

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#57

Earlier 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?

You’re probably thinking of Beats. But even then, it turns out that the original story was wrong because they were knock-off Beats.

https://www.core77.com/posts/38311/Teardown-Reveals-Beats-He...

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#58
post #8

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.

[flagged]

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#60
post #8

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.

[flagged]

Eh, even if it just means that someone can offer a 3rd-party smartphone app to control them, it's a pretty big win versus the normal end-of-life support story
Post reply on HN