Remix.run Logo
thesh4d0w 2 days ago

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

freedomben 2 days ago | parent | next [-]

Yeah that's quite fair, the article is not very accurate.

It sounds like there are two main pieces to me:

1. Removal of cloud dependency

2. Making usable the API (and providing documentation)

With a minor 3rd piece:

3. The official app will be updated to support the "offline" mode without losing as many features as possible now that the cloud service is going away.

All very laudable things IMHO. I'm actually going to buy one of these

snackdex 2 days ago | parent [-]

yes. especially when you consider that point 2 requires some amount of investment (writing the api docs, ensuring no ip leaks, etc.)

pbasista a day ago | parent [-]

Those APIs have already existed. So it is probable that they already had a documentation.

Sanitizing an existing documentation for public release might take notable time and effort if there are 100s of endpoints. But I would assume that is not the case with an API for a speaker.

crazygringo 2 days ago | parent | prev | next [-]

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.

jan_Sate a day ago | parent | next [-]

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

dominick-cc a day ago | parent | prev | next [-]

The soundtouch web api which is what was "open sourced" was already an existing thing for a long time. You just had to access it from the bose developer portal I think. I don't think anything actually happened here. I'm so surprised that HN is excited about this story because nothing seems to have been released.

IshKebab a day ago | parent | prev [-]

There are several things they could open source: the firmware, the server, the app.

I assumed they meant the firmware, and was quite surprised they would do that...

adrianN 2 days ago | parent | prev | next [-]

Maybe Bose doesn’t have all the rights necessary to open source their code, eg because they rely on libraries.

Almondsetat 2 days ago | parent | prev | next [-]

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

GuB-42 a day ago | parent | prev | next [-]

I admit that I expected more. They really did the minimum, as in, anything less should have been illegal. It is praiseworthy, but it is unfortunate that it is.

Seeing that, I expected the ability to build and run a custom firmware, like with an Android device with its bootloader unlocked. But it is not that, and they didn't open source their app either.

What they did is that they removed dependence on their servers, and opened their device to be controlled by third party apps. That is, they let users use their device past its end of life, including when the first party app will stop being maintained, but not to the point of letting user add features.

In understand why they would do that, they don't want users to backport features only available on their latest models that are sold at a premium, therefore competing against themselves. After all, the value in smart speakers is not the sound producing device, which I think is a problem that has been solved more than a decade ago at the consumer level, it is all about software features.

seemaze a day ago | parent | prev | next [-]

Agree that the 'Open Source' is misapplied in this instance. I do applaud Bose for providing a graceful EoL to their product and consumers.

dTal 2 days ago | parent | prev [-]

Yeah, it's kinda sad how much applause this is garnering when publishing API specs should be bare minimum for any smart device, never mind EoL concerns.

freedomben a day ago | parent | next [-]

Don't let perfect be the the enemy of good. I fully agree with you on what the bare minimum should be, but the reality is that our definition of bare minimum is currently a fantasy. Any steps taken toward our vision is good and should be applauded IMHO. Especially when it's a major player like Bose that hopefully sets a positive precedent and gets other manufacturers to realize this is not only possible but leads to applause and hopefully more sales.

Evolution v. Revolution. I'd prefer the latter, but realistically the former is the more likely to succeed short of people like us getting control of regulatory bodies and forcing it.

dahcryn a day ago | parent | prev [-]

what more do you actually need?

Unless you want to actually develop ON the device (and build binaries etc...), this completely allows you to use the device and connect it to whatever, so I don't know what more we should expect.

No one else is doing this, so yeay applause

nemomarx a day ago | parent [-]

Open sourcing the server code would make getting your own instance of it way easier, and maybe opening the app code so people should change the controls?