all 63 comments

sorted by: hot top controversial new old
[–] 294 points 10 months ago* (20 children)

"Open source" really isn't the right term here, if they're just releasing API specifications. "Open sourcing" the speakers would be releasing the source code to the software that runs on the speakers.

Like, all of Microsoft's libraries on Windows have a publicly-documented interface. That hardly makes them open source. Just means that people can write software that make use of them.

  • source
  • hideshow 20 child comments
  • [–] 30 points 10 months ago (1 child)

    Indeed it's misleading wording but credit where credit is due, this is far better than turning them all into e-waste. It's not like anyone bought these with the assumption they would have any sort of official API someday, especially after seeing how Sonos handled their similar situation...

  • source
  • parent
  • hideshow 1 child comment
  • [–] 19 points 10 months ago

    It’s misleading wording by arse-technica, not Bose. The quoted wording from Nosebis correct and it looks like they’re doing the right thing. After originally announcing they would be dumb speakers, now they’ll continue to be useful and third party apps can continue to use them. Applaud Bose for doing the right thing

    Direct your Boos to arse-technica

  • source
  • parent
  • [–] 71 points 10 months ago (3 children)

    Yes, the correct term for this would be “open api”

  • source
  • parent
  • hideshow 3 child comments
  • [–] 11 points 10 months ago

    There is a Soundtouch extension to Music Assistant, which which is part of Home Assistant. Last I checked the developer is unsure how functional the wireless speakers will be after the app shutdown.

  • source
  • parent
  • [+] -75 points 10 months ago (13 children)

    I appreciate the distinction, but open source is always a spectrum, so I think the description is a reasonable application here.

  • source
  • parent
  • hideshow 13 child comments
  • [–] 52 points 10 months ago (2 children)

    but open source is always a spectrum

    Is it? I’ve only ever heard “open source” to refer to the source code being released.

    Maybe there’s a different term they meant to say other than “open source”

  • source
  • parent
  • hideshow 2 child comments
  • [–] 45 points 10 months ago

    But the source code isn't available. The source isn't open. It's not open-source, by definition.

    The "spectrum" you refer to us about how free you are to publicly make use of the code, not whether or not you even have the code.

    This situation does not fall inside that spectrum.

  • source
  • parent
  • [–] 18 points 10 months ago* (last edited 10 months ago) (3 children)

    open source is always a spectrum

    It most definitely is not.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 19 points 10 months ago (2 children)

    It is a spectrum (MIT vs GPL vs APL for example) but this is outside that spectrum.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 10 months ago (1 child)

    That is not a spectrum of open source. They are all open source, as in you can access the source code without restriction. These licenses just limit what you can do with the source code.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 10 months ago

    Well, yeah. That’s what the spectrum is.

    Low end: “you can see the source but can’t do anything with it” (questionable whether this counts as open source at all)

    High end “do what you want, it’s literally yours” (public domain).

    One can debate where the low boundary of “open source” is, or what makes one license more or less free than another, but the spectrum is the range of limitations.

  • source
  • parent
  • [–] 77 points 10 months ago (1 child)

    It would be one thing for a corporation to misuse the term open source as they've been doing lately. It's pretty bad for one of the biggest and oldest tech news sites to be doing it.

  • source
  • hideshow 1 child comment
  • [–] 131 points 10 months ago (14 children)

    We need a law that companies provide device owners root access for every end of life device.

  • source
  • hideshow 14 child comments
  • [–] 51 points 10 months ago (4 children)

    That's something the EU would do, but never America.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 30 points 10 months ago* (3 children)

    How about a free gun at the end of life of any device?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 23 points 10 months ago (5 children)

    I think medical device manufacturers should have to support their products for some definite length of time—maybe 10 years?—or not be allowed to make devices at all

  • source
  • parent
  • hideshow 5 child comments
  • [–] 8 points 10 months ago (1 child)

    This type of laws already exist in some cases, but realistically no one knows that the company won't just go bankrupt in 5 years. Open sourcing things is a "reasonable" last resort option, or rather, the only viable one

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 10 months ago (2 children)

    Medical devices are already supported for a very long time. At least the official ones used in hospitals.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 15 points 10 months ago* (last edited 10 months ago)

    For software too, if a company has sold software and then goes out of business, it should have to give all licensed users permanent access to use it. Preferably also the source code. (Ideally we'd have open source options for everything but that's not always practical or possible right now.)

  • source
  • parent
  • [+] 4 points 10 months ago* (last edited 6 months ago) (2 children)
  • [–] 1 point 10 months ago (1 child)

    GrapheneOS is your savior. I should donate, their work is only getting harder.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • load more comments (-1 replies)
    [–] 40 points 10 months ago (2 children)

    Basic documentation does not equal open source.

    Toaster ovens from 40 years ago did better. They came with a technical diagram.

  • source
  • hideshow 2 child comments
  • [–] 32 points 10 months ago (4 children)

    That's a pretty cool thing to do

  • source
  • hideshow 4 child comments
  • [–] 40 points 10 months ago (2 children)

    They didn't open source anything.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 21 points 10 months ago
    [–] 7 points 10 months ago (2 children)

    Is there any quality, real open-source speakers? Or it's way better not bother with it and get dumb speakers and an SBC?

  • source
  • hideshow 2 child comments
  • [–] 6 points 10 months ago*

    I don't use OpenHAB or Home Assistant, but I'd be extremely surprised if they don't have existing functionality for connecting microphones, speakers, and LLMs to set up voice-controlled stuff.

    searches

    https://heywillow.io/

    Willow Is a Practical, Open Source, Privacy-focused Platform for Voice Assistants and Other Applications

    Willow is an ESP IDF based project primarily targeting the ESP32-S3-BOX hardware family from Espressif. Our goal is to provide Amazon Echo/Google Home competitive performance, accuracy, cost and functionality with Home Assistant, openHAB and other platforms.

    100% open source and completely self-hosted by the user with "ready for the kitchen counter" low cost commercially available hardware.

    https://rhasspy.readthedocs.io/en/latest/

    Rhasspy (ɹˈæspi) is an open source, fully offline set of voice assistant services for many human languages that works well with:

    • Hermes protocol compatible services (Snips.AI)
    • Home Assistant and Hass.io
    • Node-RED
    • Jeedom
    • OpenHAB
  • source
  • parent
  • [–] 4 points 10 months ago*

    For passive, and even now some active loudspeakers, very much so.

    Links for passives: https://sites.google.com/site/undefinition/diy https://www.zaphaudio.com/ https://www.madisoundspeakerstore.com/speaker-kits/ (etc)

    Active speakers are usually things like this and use commercially available parts with commercial software. But if you want you can build a DIY DSP and DAC and DIY amplifier. Note that there are tons of other designs for both available.

    The DIY audio community is very vibrant. There are tons and tons of forums collaboratively iterating. You can build DIY headphones and DIY headphone amplifiers. Hell, you can even build DIY speaker drivers.

    Anything I missed was not an intentional omission, lol.

  • source
  • parent
  • [–] 7 points 10 months ago
    [+] 42 points 10 months ago* (last edited 6 months ago) (6 children)
  • [–] 32 points 10 months ago (2 children)

    You sound like an extremist brother. If they lie and dont do it (seems like they already have made it open-source) then get mad. But it sounds like you are upset because you got screwed by Sonos and Bose actually are attempting to do the right thing for their customers.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 33 points 10 months ago (1 child)

    Thing is they didn't actually open-source it, as stated in other comments. They just released the api documentation. While, yes, it is a step in the correct direction, it is definitely not open-source. Open source would be releasing the source code for all the software involved, which they haven't done.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 10 months ago*

    I wasn’t affected by the Sonos App fiasco because I don’t use it. I mostly use the speakers through Spotify, and occasionally through Home Assistant. I only need the app to set my wake schedule but once it was done, I didn’t need to go back.

    Won’t this allow the same? With the API, you should be able to continue using your speakers with local automation, assuming someone wants to implement that.

  • source
  • parent
  • [–] 4 points 10 months ago (2 children)

    That kinda sucks, especially since even the older ones work with Home Assistant etc directly now

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 10 months ago

    They're never getting those integrations back though, e.g. Spotify. Those are usually implemented in each company's servers rather than something that can be brokered locally through an API. That needs to change

  • source
  • [–] 1 point 10 months ago

    That’s fantastic. Can Apple Pay attention to this?

  • source
  • [–] 2 points 10 months ago
    6 comments in c/technology@beehaw.org view that post
    [–] 39 points 10 months ago (2 children)

    open-sources

    To repeat my comment over on !technology@lemmy.world, "open-sources" isn't really the right term here, as the source code that runs the speakers isn't being released. This is just releasing API documentation to let software interact with the speakers.

  • source
  • hideshow 2 child comments
  • [–] 14 points 10 months ago

    That’s still a pretty big win. It means the interoperability and control via external means is preserved. It can be localized as well and prevents it from becoming e-waste as quickly.

    I wish more devices would do that EOL. I don’t need to know how it works internally, but as long as I can still use it when it’s cloud based service shuts down is amazing.

  • source
  • parent
  • [–] 13 points 10 months ago (1 child)

    This is great to see, and as long as it's up to companies whether to do this we need to encourage that behavior... but it also shouldn't be up to companies' whims whether to do this or not. It should be legally required for end-of-support devices and software to release whatever source code or changes are necessary to either operate the device/software independent of a server, or run the server ourselves.

  • source
  • hideshow 1 child comment
  • [–] 5 points 10 months ago

    Precisely, which will cut down on e-waste and consumer costs as well. If industry says that reduces profit bc people are still using their current models, then they need to be better and more creative as businesses to deliver what people want, and not shoving them toward a new purchase they don't need/can't afford.

  • source
  • parent
  • [–] 3 points 10 months ago

    I always recall Bose for their high quality almost 'vintage' devices, and they should encourage their newer digital devices to become the old high quality devices that still work, sitting in someone's home.

  • source
  • 3 comments in c/hardware@lemmy.world view that post
    [–] 50 points 10 months ago (1 child)

    Distributing the documentation of your API is not making your device open source, what the fuck kind of tech journalism is that

  • source
  • hideshow 1 child comment
  • [–] 17 points 10 months ago

    Yeah the headline definitely does not match the content of the article.

    This will make it easier for people to build apps that interface with the speaker without signing any agreement with Bose, but it doesn't make it any easier for the community to patch or update/maintain the speaker firmware itself, which is what may eventually result in the speakers being landfilled despite having good hardware.

  • source
  • parent
  • [–] 15 points 10 months ago

    PDF is open-source, LLM black box is open-source, everything is open-source. Those companies must really want to destroy the meaning of open-source.

  • source
  • 2 comments in c/technology@lemmy.zip view that post
    [–] 26 points 10 months ago* (1 child)

    They didn't open-source it. They released an API spec. The author seems not to understand what "open source" means. What they did was a step in the right direction though.

  • source
  • hideshow 1 child comment