@alasaarela right? That’s the whole point of an open protocol, which even supersedes a codebase license: anyone can implement interop under any license or hosting / deployment stack.
@bmann @alasaarela@equel.social That is not where the considerations end. Cloudflare in particular is a known bad actor. Learning from past cases of EEE is instructive here.
@bmann And that "lots of other [supposedly] open-source things are built on proprietary systems" is a huge problem, actually, but somehow people always defend it through circular reasoning by pointing at the other things that are *equally* bad as a justification
@joepie91 yep I agree! I was trying to see if anyone would actually admit to this or just say that CF has some bad actions in their history as you pointed out.
I still don’t think this is EEE. They literally wanted a hot trend to demo their stack with. AP is an open protocol.
@bmann These kind of "ah, but are you hypocrites?! let's see" mind games are completely unnecessary. "Open-source" things depending on corporate infrastructure is a thing that is *frequently* criticized on here, by much the same people as Wildebeest is now.
As for the second part: Cloudflare's whole business model is EEE. As others have said, "corporations do not get the benefit of the doubt", and that is doubly true for one with such a long track record of EEE.
