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

[–] wiki_me@lemmy.ml 2 points 3 days ago

Allow people who fund the platform vote on features (that are pre approved ). who contribute more get more in return.

"time well spent". and maximizing the "average quality of content". maybe by allowing custom feeds. or feeds that are based only on the votes of trusted users. with governance models supporting how those feeds are managed like how KDE and GNOME nonprofits are managed. maybe vote on best post/comment of the day/week/year/decade with leaderboards for that.

Linus law of trail and error. allow people to easily extend the software .with plugins and ideally a store with reviews for addons like in firefox and chrome. making experimentation easier and safer (without risking adding a bad feature to all users of the software). vote on features implemented rating for example how satisfied you are on a scale of one to ten.

information over speculations . use A/B testing to see what works in practice. maybe use "counted statement" for example "this is useful" or "this is important" beyond lemmy and reddit upvotes and downvotes.

Right now a life changing post from world class expert and a funny cat picture with someone who spend too much time online are treated the same by the software. this should somehow change.