kytta
Decide on one runtime and deprecate others
I have been contemplating leaving Astro for a lighter weight solution. Astro is very cool; I love how easy it is to deploy to multiple runtimes. However, it's hard to keep all runtimes in mind, and the lack of an 'auto' adapter (like what Svelte offers) makes it harder.
I don't want to write my own auto adapter, and I don't want to have users install all the dependencies, and I also just don't want to have all of them around.
I need to decide on one runtime that is the "flagship" runtime. The s2f.kytta.dev will use it. I don't know if self-hosted or not. Currently, it's on Vercel, but the usage has been high enough that I begin to fear high prices. Deno (the runtime) is something closer to my heart than Node, but Deno Deploy is not as good. Lastly, I could just self-host it. In any case, there should be one adapter and one dependency.
All other runtimes become "contrib-/community-supported". I will make sure to update their dependencies, and I will keep the canary instances running, but if one of them breaks for no apparent reason, I don't care.
Okay, I've met the decision. I will self-host Share2Fedi on the main domain, and I will use Node.js. All other runtimes will be deprecated, but the config files should still be available under contrib/