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!

  • General_Effort@lemmy.worldEnglish
    1·
    3 months ago

    In the client, you wouldn’t need to be sorting and running extensive calculations on all data. You could, e.g, build the front-page by indexing/scoring posts and comments that have been created since your last visit with a hard cap on some time window (last 48h) or total data points (e.g, keep only the most recent 10k objects in a local hot database, freeze/archive everyhing else.)

    Absolutely. There’s a lot you can do. The “For You” Feed on Bluesky is quite instructive. https://bsky.app/profile/spacecowboy17.bsky.social/post/3mb2r5qei322a

    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.