I have enjoyed this discussion but some of my UK peers have added that the fediverse in general (like most social media to be fair) when it is new seems to "american" for them. Bluesky suffers from this criticism as well. This puts a lot of UK users off. Heck even threads is described by many as too us focused right now (see the I'm in the UK is anybody else posts on threads)
Feddit.UK is kinda nice as there's the little british bubble in Local
https://feddit.uk/ has 400 monthly active users and is as British as you can get
Aye it is.... but 400 users seems really small compared to others
I definitely get burnt out on it faster when half my front page is meta posts. I don't have time to curate, I just want to see content that isn't about itself.
Block the meta communities
Or use Piefed where you can create different feeds (a la multireddit): https://join.piefed.social/
I don't have time to curate
They do not want to fix the problem, they want it to fix itself.
Bluesky blew itself up cos they failed to be sufficiently decentralised and became an echo chamber. Activpub systems are less echo chambery but still have a very strong left lean that is significantly effecting out ability to grow especially among the centre who represents the majority. We need more right wing opinions and allow said right wing opinions if we want the majority of people to adopt it.
The fundamental failure of the fediverse that is limiting us is that accounts are not transportable. We need some decentralised ledger of accounts that can be cryptographically verified with a zero trust system. U just set up a oidc server to do that auth and that plugs into every single fediverse application everywhere.
OIDC gives you federated login, but no portable identity...
Oidc is the protocol by which auth can happen its the evolution of oauth. U need to build some kind of decentralised ledger then u set up a server that checks that ledger against the user provided auth then u simply make this server have an oidc endpoint allowing it to be plug and play with existing fediverse services.
I say oidc cos almost all fediverse software is already compatible with it.
My point is: if you have a ledger that the user controls and can use to redirect to different auth endpoints, then you don't need oauth. You just use the record in the ledger as the authentication mechanism directly.
Yeah exactly. But instead of having to implement that auth process in every different fediverse service in however many different languages u simply write it once with an oidc endpoint and all fediverse services can run it as a container in their stack. It makes implementing such auth system a simple config change and updating a docker compose to add a new service.
Fediverse
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, 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)