design around ease of self-hosting. A non technical user must be able to self host easily and at a very low cost.
Embrace content sorting and filtering algorithms, but on the client side, with optional control by the user.
Standardize tags on all content. So many of the different ways different platforms classify or organize content can be implemented as tags, which increases interoperability between them.
Abandon obsession with real-time-first implementations for use cases that don't explicitly need it.
Transferable user identity (between instances)
User identity and authentication as separate service from social network instance

Would love to hear yours!

you are viewing a single comment's thread
view the rest of the comments

[–] RobotToaster@mander.xyz 1 points 3 days ago (2 children)

I'm not saying that instances shouldn't have default blocklists, but that users should have the right to disable them granularly.

[–] ada@piefed.blahaj.zone 3 points 3 days ago

No way. Transphobia is not welcome on any instance I run for example. And that isn't something that a user should be able to change for themselves. That's a scenario where you would pick a difference instance

[–] matcha_addict@lemy.lol 1 points 3 days ago

I think instance owners should retain the ability to make some blocks non-negotiable. They are responsible for the instance and legal implications after all.