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!

  • Raphael@communick.newsEnglish
    2·
    2 days ago

    But when you’re talking about sending a lot more data to clients, you really need to consider what that means for the internet bill of instance owners.

    I would argue the opposite, actually. A lot of this data could be distributed in a p2p manner and the client nodes would have to rely even less on the servers. The key part would be that this data would have to be self-authenticating, but we do have the mechanisms to do that (Linked Data Signatures)