Thread by @IDisposable

I wanted to control my own mastodon identity so I can easily move if a server dies. So my identity is now @[e-mail]

To have that mapped to my current identity, we have to implement the webfinger protocol at github365.com which is a domain I put up for fun a long time ago. That site is actually a fully static HTML file hosted on my bluehost.com account.

I could put up a static file named webfinger in the /.well-known/ directory, but that would mean every request would point to the same json response (and thus the same identity. See @maartenballiauw 's blog post blog.maartenballiauw.be/post/2022/11/0…

So, since ALL my BlueHost stuff is fronted by @Cloudflare (because who doesn't want awesome performance?) I thought why not use a CloudFlare Worker to handle the webfinger protocol at the edge?

That means that I can setup a worker and deploy it at a route that I control on the CloudFlare dashboard. Obviously I don't want to manage all the mappings in the source of the worker, so why not use the CloudFlare KV stuff?

After WAY too much noodling around, I've got it working using the typescript API provided by @CloudflareDev at developers.cloudflare.com/api to construct a worker using Wrangler.

I'm happy to say that github365.com/.well-known/we… now works exactly the way I want, and as a learning experience for myself and others, I've fully released the worker sources and documentation at github.com/IDisposable/cl…

@maartenballiauw @threadreaderapp unroll