cross-posted from: https://lemmy.blahaj.zone/post/3045

Now this is interesting. A Fediverse platform developed by Cloudflare that inherently runs on Cloudflare without needing dedicated infrastructure.

The code is open source yet the platform itself is inherently proprietary. It’s going to be very interesting how this unfolds given how unpopular Cloudflare is with many Fediverse admins

  • I’m not a fediverse admin, but I like to think that if I was I would find a way to automatically defederate with these cloudflare instances. Open source code doesn’t mean anything if it can only run on proprietary infrastructure.

    More abstractly, I don’t feel like there’s inherently anything wrong with the sort of thing, but the fact that Cloudflare Corporation in particular is doing this rubs me the wrong way

    • @anova Why would you ban yourself from interacting with someone who voluntarily chooses provider X or Y or Z for anything? That’s their choice, not yours.

      Half the fediverse already runs on servers provided by only 3 companies. If anything, adding more to the mix, both implementations and hosting providers, is healthy for a decentralized ecosystem.

      • Why would you ban yourself from interacting with someone who voluntarily chooses provider X or Y or Z for anything?

        Because I’m petty

        Half the fediverse already runs on servers provided by only 3 companies

        I also don’t know those three companies off the top of my head, and while I definitely believe you, I can’t imagine they are anywhere near as big as Cloudflare. If you’re talking about cloud service providers, I’d also consider running an instance that ignores say, AWS instances, but I think that’s a bit different since they don’t specifically provide “activitypub” services afaik. With Cloudflare, it’s much more explicit

        • @anova Same. If Amazon created their own ActivityPub implementation, that would be yet another one that has to interop with all the other implementations, thus creating a healthier, more diverse ecosystem. Now people are mostly just running Mastodon on AWS.

          The Cloudflare move is important not because of their infra, but because it’s a new server implementation, which can only run on Cloudflare, thus always having to interop with other implementations (except for insular, corporate use cases).