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 10 points 1 month ago (12 children)

User sovereignty first design, where users individually control what instances they wish to block.

[–] matcha_addict@lemy.lol 6 points 1 month ago (11 children)

I agree with this. I think instance owners retaining ability to block other instances is still unfortunately necessary, if at least for administrative and legal reasons. But putting the onus on granular blocking controls on the user is a big achievement, as I prefer the user to retain that control.

[–] WamGams@lemmy.ca 1 points 1 month ago (1 children)

you should look at the domain names of some of these blocked instances.

going live without a block list implemented upon start up is going to put you in a very serious legal quagmire where you are now responsible for your ISP having transmitted CASM.

[–] matcha_addict@lemy.lol 1 points 1 month ago

That's precisely why I call it necessary, you're right!

load more comments (9 replies)