65
What principles you wish to see social networks (or the fediverse) adopt in their design? (lemy.lol)
submitted 10 months ago by to c/fediverse@lemmy.world
53 comments fedilink hide all child comments
 

For example, for me, here are some things I wish to see (or would implement in my design) :

  • 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
[–] [S] 4 points 10 months ago (4 children)

An easy middle ground is the ability to sync your block list with someone else. This gives the same capability you desire, but allows users freedom to do it on their own. Everyone's happy! What do you think?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 10 months ago (3 children)

    It's a good idea, but still not an alternative to instance level blocking.

    The downside is that if you're new to the fediverse, you have no way of knowing whose lists you should follow. So there needs to be some sort of instance/client level opt in recommendation to make it visible/useful to new users.

    Beyond that though, on an instance like blahaj, it would be largely irrelevant, because there is no scenario where I let transphobes federate to the instance, whether or not individuals have the ability to block them from a subscription list.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 2 points 10 months ago (2 children)

    The downside is that if you're new to the fediverse, you have no way of knowing whose lists you should follow.

    Isn't the whole idea that you choose a trans-friendly instance and you naturally adopt the instance wide blocklist? Same thing here, except you choose the block list similar to choosing an instance in the old flow.

    And if you disagree, this could still easily be mediated. For example, the instance could have a default block list. As long as one can opt out, that would respect user choice.

    Or choosing the blocklists can be part of the account creation flow.

    There's others ways to go about it.

    Beyond that though, on an instance like blahaj, it would be largely irrelevant, because there is no scenario where I let transphobes federate to the instance

    What I suggest isn't meant to take away the instance owner ability to defederate or moderate. But this makes it such that you don't have to modify your moderation strategy when your users can adopt different moderation in addition to what you have. (example: maybe a large group of your users want to block US-centric content, or political content, etc.) and people not on your instance could possibly adopt your moderation as well!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •