Mitja Podreka
tanteThis should be a legal requirement for being allowed to sell networked devices.
(Original title: Bose open-sources its SoundTouch home theater smart speakers ahead of end-of-life)
Aleksandr Koltsoff@tante There was no actual conversion to open-source. ars-technica was a bit sloppy here.
What happened is that Bose sent a link to the HTTP API document so that people could write replacement software for the stuff that connects to the device.
Device internal software remains proprietary and non-fixable.
@tante (I read through the spec doc yesterday and it contains license conditions that make using the API in open source not even possible, unless going through white-room).
Mohit SindhwaniI came here to say that - I would imagine that a system built with licensed components, codecs, etc. would likely not be allowed to be open sourced... I remember that there was a big push to make OS/2 Open Source after IBM abandoned it and that was one of the big problems with that proposal.
Guido Gallenkamp@tante Also for software / games that require a server to connect to
Lenni
haui â˜
🇵🇸@tante
As the unhappy owner of legacy sonos devices, i felt this in my bones. Fuck sonos.
As the unhappy owner of legacy sonos devices, i felt this in my bones. Fuck sonos.
BitHive 
@tante it is btw: https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Cyber_Resilience_Act/cyber_resilience_act_node.html
Cyber Resilience Act
Der Cyber Resilience Act ist die erste europäische Verordnung, die ein Mindestmaß an Cybersicherheit für alle vernetzten Produkte festlegt, die auf dem EU-Markt erhältlich sind - etwas, das es bisher nicht gab. Ziel ist es, die Cybersicherheit innerhalb der Europäischen Union zu erhöhen. Die neuen Vorschriften gelten in allen EU-Mitgliedstaaten und werden schrittweise umgesetzt.
tastyraspberryOk - right, thats more like a recommendation; with a bit whisfull thinking on my part:
(61) When products with digital elements reach the end of their support periods, in order to ensure that vulnerabilities can be handled after the end of the support period, manufacturers should consider releasing the source code of such products with digital elements either to other undertakings which commit to extending the provision of vulnerability handling services or to the public. Where manufacturers release the source code to other undertakings, they should be able to protect the ownership of the product with digital elements and prevent the dissemination of the source code to the public, for example through contractual arrangements.
LionelB
Hubert Figuière@tante from reading it’s not open source. They just document the REST api which should have been done on release day.
@hub Making it Open Source would be better. But the API at least allows people to build something to keep the systems operational. It's not "the best thing" but it should be the minimum.
@tante but the terminology is incorrect (and confusing) — it first it make the reader think that the software is.
Yes it's still better than any other, but the bar is set so low..
Ars is doing us a disfavour here and they should know better.
@hub I agree with that criticism. @arstechnica has fucked up with the terminology here.
Jack-Frostodon@tante The beautiful irony here consists of all the following good, and more:
1. This is #recycleMode in all the ways Sonos's so-called recycle mode wasn't. And that's a good thing.
2. Anyone with the chops can build a permanently accessible native app around this api.
Which would give users who can obtain this speaker set used in the not-too-distant future a viable, opensource and accessible wireless audio setup. Up yours, Sonos!
1. This is #recycleMode in all the ways Sonos's so-called recycle mode wasn't. And that's a good thing.
2. Anyone with the chops can build a permanently accessible native app around this api.
Which would give users who can obtain this speaker set used in the not-too-distant future a viable, opensource and accessible wireless audio setup. Up yours, Sonos!