I vote for forced open sourcing of the server side components and communication protocols. That way people can create custom firmware or build support into generic NVRs
You don’t need every consumer to roll their own. If they’re obligated to provide server code, or an API, or whatever, stuff that sells at scale can be integrated into community projects. If you buy something obscure you might have issues, but you have options if you buy something mainstream and get the rug pulled.
You don’t think it will be mentioned in any of the articles about the hardware being abandoned?
But community projects would very likely also allow third parties to provide services that handled the legwork for customers if they preferred as well.
I vote for forced open sourcing of the server side components and communication protocols. That way people can create custom firmware or build support into generic NVRs
Most customers would not be able to take advantage of this because they lack the skills to do so.
You don’t need every consumer to roll their own. If they’re obligated to provide server code, or an API, or whatever, stuff that sells at scale can be integrated into community projects. If you buy something obscure you might have issues, but you have options if you buy something mainstream and get the rug pulled.
Right, but what I’m saying is how many people do you think will be able to track down the new open-source project and connect it to their hardware?
You don’t think it will be mentioned in any of the articles about the hardware being abandoned?
But community projects would very likely also allow third parties to provide services that handled the legwork for customers if they preferred as well.
Because if the community solutions are good enough then half the articles about the shutdown will mention it