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

[–] 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.

[–] ada@piefed.blahaj.zone 3 points 1 month ago (8 children)

That's not a universal want. Trans people and other vulnerable, targeted minorities face a real cost in having to play whack a mole with bigots. Sure, you can block them as they appear, but by that point, you've already seen their hate. And it means every trans person has to see and block that content. After which, the bigot just comes back with a new account, and does another round.

The blahaj instances offer aggressive, pre-emptive blocking of bigots and transphobes, at the instance level, with the goal of giving our users an experience of social media that isn't shaped by hate.

Of course, not all trans folk want that, and some absolutely do want the power to choose for themselves who gets blocked and are willing to face the hate in order to retain that ability. But that's the other power of the fediverse, because there are instances that cater to that approach as well.

tl;dr - Granular user control of blocking/federation is good, but it's not "better" than instance level blocking and defederation.

[–] RobotToaster@mander.xyz 1 points 1 month 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.

[–] matcha_addict@lemy.lol 1 points 1 month 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.

load more comments (1 replies)

load more comments (6 replies)

load more comments (8 replies)