← Back to context

Comment by jan_Sate

2 days ago

They're just publishing API documentation. No source code of the device got published.

At least people can create their own implementation of the API tho.

6 comments

jan_Sate

Reply
stavros  2 days ago

If the publish the API for the server, as well as allow the device to specify the API hostname to connect to, that's all I need. We can write our own server implementation fairly easily, and this saves us the hassle of having to reverse-engineer the API, plus makes setup much easier if we can just tell the device where to connect.

I wish more manufacturers would unlock their devices for local use when they don't want to support them any more. Or maybe even, hear me out, before support ends! Maybe we could even vote with our wallets and buy open stuff instead of walled gardens.

  • ryandrake  2 days ago

    Exactly. Open source is great and all, but all 99% of these devices need is simply a way to configure them to connect to a different server, when the manufacturer inevitably turns their own server down (usually) bricking devices.

    The open source community will happily reverse-engineer the protocol and clean-room develop their own server code.

    • thewebguyd  2 days ago

      > 99% of these devices need is simply a way to configure them to connect to a different server, when the manufacturer inevitably turns their own server down (usually) bricking devices.

      The same can be said about a lot of games, and should be the case with them as well. Big MMOs for example. See the plethora of WoW private servers as an example of how it can be done.

      I think the stop killing games initiative in the EU was pushing for it but not sure how far they've gotten, but like with hardware, once a game studio no longer wants to run the servers for their game, they should be forced to turn it over to the community so the players can continue playing long after the studio is gone.

      1 reply →