twtxt VS wildebeest

GitHub repo

> there really oughta be a text-only implementation of mastodon or one of the other fediverse ecosystems

Something like this that I know of, in a very simplified form.

> twtxt is a decentralised, minimalist microblogging service for hackers.

> So you want to get some thoughts out on the internet in a convenient and slick way while also following the gibberish of others? Instead of signing up at a closed and/or regulated microblogging platform, getting your status updates out with twtxt is as easy as putting them in a publicly accessible text file. The URL pointing to this file is your identity, your account. twtxt then tracks these text files, like a feedreader, and builds your unique timeline out of them, depending on which files you track. The format is simple, human readable, and integrates well with UNIX command line utilities.

https://github.com/buckket/twtxt

I will note that indieweb folks sometimes get a little dogmatic about POSSE being better than PESOS (Publish Elsewhere, Syndicate to your Own Site). Because POSSE necessarily entails write-permissions, it's titchier to set up than PESOS-ing your public content elsewhere back to your own site. I had a lot of stuff PESOSed from Lemmy (https://lemmy.ml/post/47757) to my own site (https://maya.land/responses/2021/01/14/recyclable-plastic-is...) because I could just scrape the content out of the Lemmy RSS feed and reformat. Similarly I pull over Hypothes.is annotations (https://via.hypothes.is/https://theprepared.org/features-fee...) to a personal wiki where I clean them up into posts for my site (https://maya.land/responses/2021/07/29/geofoam-giant-styrofo...). Sure, if I wanted to update in two places it'd get titchy, but because I'm mainly using these other sites as front-ends to get a canonical personal copy I then mess with, it works pretty well. Hell, I even take Mastodon (https://occult.institute/@maya) and shove it into a twtxt (https://github.com/buckket/twtxt) file on my site (https://maya.land/assets/twtxt.txt). Once you start thinking about stuff with these approaches you can always find a convenient way to duct tape things together.

As a PWA it probably will not be possible. I don't know of any fedi software that is designed to run entirely without a back-end of some kind. Maybe Wildebeest will fit the bill for you, but it uses Cloudflare's Supercloud as its back end.

Does anyone have a simple example of a Qwik app running on Cloudflare Pages that uses a binding to KV Store or D1? I know that Cloudflare recently released Wildebeest https://github.com/cloudflare/wildebeest but I'm looking for something much smaller for learning purposes. Thanks!

Maybe this https://github.com/cloudflare/wildebeest ?

https://github.com/cloudflare/wildebeest

Official install guide is underlying 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?