microfeed VS Misskey

Microfeed (https://www.microfeed.org/) is what I want from a UI/UX perspective, but it's not really self hosted (it's completely dependent on Cloudflare services for hosting).

If you like Cloudflare and want to host a few GB media files (e.g., audio, video...) for free, then you can try microfeed: https://github.com/microfeed/microfeed

Closest I find is https://www.microfeed.org/ but it's more for sharing media files rather than a microblog.

i’ve been using django/postgres for over a decade. if it were 5 years ago, i’d use django/postgres.

but recently i would use cloudflare pages, r2, d1, zero trust… in many cases, we don’t want to put eggs in the same basket. but in some cases (eg, building mvp, toy projects…), it’s convenient to be on an all-in-one platform .

for example, i recently launched a cms entirely on cloudflare: https://www.microfeed.org/

I feel like microfeed: https://github.com/microfeed/microfeed and Argun Ganesan’s Edge Blog, both enabled by the open alpha of D1, represent a point of change where users of Cloudflare’s developer platform are moving from deploying their own apps to deploying apps created by others.

on Misskey: https://github.com/misskey-dev/misskey/issues/9504

There is a lot of resistance to the idea. The browser UX for registering protocols is not particularly intuitive. The protocol should not be named after Mastodon because they are defensive of their trademark, and it wouldn't be accurate since the user identifier could be followed from any ActivityPub compatible software.

If you look at the newer comments on the Mastodon github thread I posted you can see web+ap:// recommended, or apub://

I think there just needs to be enough collective will to make this happen. Likely another project will need to take the lead because Mastodon team has decided the browser UX is too much of a barrier. Maybe glitch-soc can do a proof of concept.