This is a general view on the topic. I think open-source isn’t enough, we need also governance for the software we use, and create small pockets of freedom.
All feedback is welcome.
This is a general view on the topic. I think open-source isn’t enough, we need also governance for the software we use, and create small pockets of freedom.
All feedback is welcome.
Almost the point, I don’t want to fragment a system, I want to federate then. Make more people using the system, focus on the protocol and make the system better. For example, Piefed, I’m writing this on a alternative face of the system, but because this is a federated, I don’t need to use the official front. At the same time, I focus on the showing the system for more people around me, and expanding it’s userbase (and money, but I was focus on the human instead of the money).
And hopefully these protocols are backward compatible so I can still use a limited feature set running an older version. I think this would be a big step towards avoiding any fragmentation.
I hate when software supports up to an arbitrary version number and if you just fake the version string in your client or framework it just works fine. Why set up arbitrary hurdles?
Protocol solves this issue. And reason why takes so long for a protocol to establish.