Gotta respect boycotting Cloudflare on principle… but also, why?

In short, it’s a backend/frontend combination that can be shaped using standards compliant web technology, i.e HTMX and JSON, to make it easier in prototyping federated platforms.

Prototyping frontend and backends in tandem is an undertaking to say the least. By creating a framework specifically designed to bridge that gap it will allow developers to more effectively develop, test and publish social media platforms.

…also, they coupled the decoupling… because of course they did. But yeah, if this makes it easier to create federated platforms, I’m all for it.

My biggest problem is how people refuse to integrate monetization into federated platforms. Some standard transactional system of sorts that could allow small platforms to create revenue streams for creators.

Not having that means Threads will be the only platform that makes such functions available, and you know they’ll have a quota based incentive system much like YouTube to get all the creators their side of things.

This is bad for musicians, film makers, animators, etc. And if you’re idea is that “you can just link to someone’s Patreon account or their PayPal wallet”, then we’re right back to the same problem again.

Believing that in 2024 you can just ignore monetization within platforms means you’re just leaving a hole in the fence for which nefarious actors can sneak in. It’s better if we standardise and normalise ethical payment models and have them readily available across platforms.

We need a federated, decentralised SWIFT for the fediverse - believe it or not.