751
this post was submitted on 08 Jan 2026
751 points (94.5% liked)
Technology
78627 readers
2924 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"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.
Yes, the correct term for this would be “open api”
"documented api", nothing open about it
Idk, it probably has an open backdoor somewhere
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.
I appreciate the distinction, but open source is always a spectrum, so I think the description is a reasonable application here.
The source code is private, how can you call that open source?
Bose innovates again by creating "open source" without source, and while keeping everything closed!
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.
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”
And being under a permissive license. Just making the source available is called source-available.
Permissive license means MIT or Apache2. The GPL or AGPL are also open source but copyleft licenses.
It most definitely is not.
It is a spectrum (MIT vs GPL vs APL for example) but this is outside that spectrum.
You're shitting out of your mouth, son.
One could make that argument, but not in this case. Documenting an API has nothing to do with the open source status of the product.