ActivityPub, as a protocol, is particularly vulnerable to EEE, since a corporation can create their own implementation and still talk to existing instances - allowing them to gradually extend the protocol, without forcing a mass migration to their service from the get go.
With Wikipedia, for example, they would basically have to create a competing site, and users of Wikipedia will not see any content from that site unless they actively go to it.
Edit: BTW, I don’t see this as admitting defeat; if anything, these migrations from service to service over time show that the corporations never win in the long run.
With Wikipedia, for example, they would basically have to create a competing site, and users of Wikipedia will not see any content from that site unless they actively go to it.
Linux is a very unique project in many ways, so I don’t think it’s the best example.
There’s Wikipedia as another example.
We shouldn’t let them make us act like we’ve already lost.
Wikipedia is also a bad example though…
ActivityPub, as a protocol, is particularly vulnerable to EEE, since a corporation can create their own implementation and still talk to existing instances - allowing them to gradually extend the protocol, without forcing a mass migration to their service from the get go.
With Wikipedia, for example, they would basically have to create a competing site, and users of Wikipedia will not see any content from that site unless they actively go to it.
Edit: BTW, I don’t see this as admitting defeat; if anything, these migrations from service to service over time show that the corporations never win in the long run.
So… Wikia, aka Fandom?
Fandom and Wikipedia are both wikis, but they serve a different purpose, they don’t really compete with each other AFAIK.