this post was submitted on 16 Jan 2025
77 points (100.0% liked)
Fediverse
28996 readers
3154 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's her description of her ideal social network, "found" is probably a bit misleading here where "I came up with the features I'd like to see in my ideal social network".
Kinda. However, from her description what is really needed is a big push to improve the UX/UI of Friendica (probably work on not overwhelming the new user with so many options too) and get it a lot more stable (although in her Friendica piece, she suggests it might be the instance she was on). Better that than reinvent the wheel.
The good thing is that it feels like Friendica's time has come - Meta is enshittifying, Bluesky is popular but people are wary of where it is going and Xitter is a dumpster fire. With more people using it, there will be more focus on improving it and it could be ready to blow up like Pixelfed just has.
I might try Friendica, although coming from lemmy I'd be more inclined towards Mbin, to combine topic-focus and people-focus.
However as a developer I first check the code repos and see that both are based on php, which seems rather old, and i doubt this would scale efficiently if the network really took off. Recall that twitter was once based on ruby (like mastodon is) and shifted to scala for such reasons. So I feel, these are exploring well the potential user-experience, but the code may need a fresh structure (if somebody knows this tech issue better, please say). It's good to discuss these things, to help consolidate potential efforts.