Welcome to Wildebeest: The Fediverse on Cloudflare
blog.cloudflare.com
blog.cloudflare.com
Official install guide is underlining that all the Cloudflare's offerings are still a disjointed bunch. You need to enable billing in 3 separate products in 3 different UIs (while only Images requires an actual paid plan, Access requires a credit card to onboard and Workers Unbound is probably a good idea to enable right away).
Why so much management/onboarding complexity if you really want to compete with AWS as a general-purpose cloud?
(edit: spelling)
Was wondering what HN thinks about this solution, and if you run your own instance of an activity pub / fediverse server that isn't mastodon which are you using? I've been trying to find something that is easy and clean for a single user instance that could run on a raspberry pi or other tiny low powered setup.
I've got my main instance as Akkoma[1] (was Pleroma, both in Elixir), a secondary as GotoSocial[2] (Go), and a couple of Honks[3] (Go) for various other things.
You might want to look at https://github.com/guysoft/PleromaPi which is a specific Pi image for a Pleroma instance.
[1] https://docs.akkoma.dev/stable/
The Fediverse is like email. There's Gmail and other completely hosted providers. I'm sure there are services that are out of the box but deployed to cloud infra. And you can self-host if you really want.
I hope a lot of the big players enter the space. That would help prevent embrace-and-extinguish.
https://news.ycombinator.com/item?id=34350897
my take: this is kind of a rube goldberg device but it's a lovely move in the right direction when suitable services are lacking.
I think a company like Twitter could have had a real competitive advantage if they were to have repackaged its core experience as a "bring your own domain name" hosted implementation of ActivityPub in the likes of G Suite or M365. I thought for a minute that's what Bluesky was, but I am losing all hopes they'll have sense to do that.
(Disclosure: I am the tech lead for Cloudflare Workers.)
Btw, is there any plans to do same thing to Matrix and Peertube, by any chance?
I don't think anyone has tried it yet. There are probably some missing pieces that need to be filled in. In principle, it should be possible to fill in those pieces without changing any of the Wildebeest code itself.
As a simple example, Workers KV provides a simple key/value storage API, basically just the methods get(key) and put(key, value). In workerd, you can use this API, but you have to configure it to point at your own back-end that does the actual storage. It translates into a basic HTTP API (mostly just GET/PUT). You could pretty easily write a Worker (running as another nanoservice on top of the same workerd instance) that uses local disk storage to back this API, or sends the data to some other back-end of your choice.
Eventually we should have ready-made shims like this to handle a lot of situations, but it's still somewhat early days of workerd and at present some of this is still missing.