this post was submitted on 05 Feb 2025
111 points (95.1% liked)
Open Source
32570 readers
262 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Their guide still implies that you need to pay a fee to unlock an API key before you can flash a new firmware.
How they plan to enforce that fee to unlock an API key when the firmware is supposedly open source I don't know. When I looked over the source code it looked like it was being written to a log.
The esp32 supports efuses that can be used to require a signed binary to boot. So they could lock their hardware to only work with their binary. Source code wouldn't matter.
Of course if the source is open you can buy and put together your own hardware and then put their code on it.
I'm not advocating what they're doing. Rent seeking is rent seeking even if they need to recoup development costs. I'd rather pay for open hardware and software with no monthly fee.
Honestly, between this and not all the modules being open source I would personally avoid it, seen too many projects openbait and then go "open core".
I agree that the guide is VERY unclear. The documentation here is a bit better, but still bad and mentions a monthly cost for DIY devices instead of a one-time dev-level API key cost.
The gist is that if you want to use their servers and you bought their device, they have an API key built in to the device for their non-dev-level API access, and it's not supported (maybe also against API TOS, but I'm not sure) to extract the API key and use it when you flash custom firmware. Getting the dev-level API key doesn't have this issue, though, because they give that to you when you pay for it.
When modifying the firmware to use on your own server, you don't have to pay them anything because you won't be using their API.
Ah. Can't really complain too much about them wanting people who are putting load on their servers to pay for it. Ideally, that should mean that the end user is not the actual product. Good to see more options joining Inkplate.
Is it possible to self-host a server? Is the server code open source?
Yes to both. The server code is open source under and MIT license as of last night.
IIRC based on the snazzy labs video about it, the answer to both those questions is yes