I think the fedi needs to be more about clients/apps than it is currently.
Agreed, and I kinda touched on this earlier about how the #Threadiverse should've simply been a frontend where people just use their main fedi account instead of having to create another account for forums in a link aggregator... :sagume_think:
Tbh all the #fediverse implementations in the first place should've been backends first and foremost. Why should I not be able to have #Misskey's frontend in #Mastodon or #Pleroma? And the other way around too. This does mean that we will have to all agree on a common client API and MastoAPI will dominate, but I'd rather have Mastodon dictate client API than fediverse implementations. :seija_coffee:
Tbh I think the #Threadiverse like #Lemmy and #kbin would make a lot more sense if they were simply frontends and perhaps a backend too but just for the forums themselves. IOW, no accounts live in Lemmy or kbin, all users post from their preferred #fediverse account instead.
Sure you can already technically do that from your #Mastodon or #Misskey or whatever fedi you're in, but that means using whatever app you're on right now, which almost certainly means it's not a #linkaggregator UI. Not ideal at all.
If I had any good programming skills I'd make it so that the link aggregator is merely a client that uses the Mastodon (with #Pleroma extensions too) and Misskey APIs, treat (almost) all #ActivityPub actors as their own forums or subs, and each post would be a boost from said actor. Users authenticate from their preferred fedi account. Voting would be tallied by few special actors, which internally receive votes via direct messages (the app will make this transparent, but this also means you can technically vote without the app if you know the exact command), which will effectively make votes secret to non-admins like in #Reddit. Users can also choose which vote counters they want to rely from.
This would make the fediverse-powered link aggregator very flexible and minimal, imo. It may look janky but that's the general idea I have. :seija_coffee:
So, @eatyourglory and I were discussing Lemmy and he had a good question/idea. Could Lemmy communities technically be subdomains? Like instead of Lemmy.world/c/example, it could be example.lemmy.world?
Would this be something that could be theoretically built into Lemmy or is there some kinda technological limitation, making this not a thing..? I think it's a neat idea.🤷♂️🤔
Excited to see the work that @julian, @angusmcleod, @rimu, @evan and many others are putting into this initiative and will be following with excitement for the future standardization and interoperability in the #fediverse thru #ActivityPub that will hopefully follow.
@ben@ben.werdmuller So it is a Threads setting now? Forgive my ignorance, but I’ve been health challenged for 2 months now, and not keeping up with the #threadiverse, or whatever we’re calling it now or soon.
I think it's interesting in obvious ways and risky in some less obvious ones (that have less to do with "O NO BILLIONAIRES" or "O NO LIBERTARIANS" and more to do with placelessness), but we'll see.
I hope good things emerge from/grow on top of this framework.
[I recognize that mentioning this is widely considered to be an invitation to explain capital like I am a tiny baby. You could also not.]
@ggpsv I’m arguing that #threadiverse platforms like Lemmy, kbin et.al. is where we should go for place, which will include Mastodon once it implements Groups.
I don’t have any sense of place on Mastodon, as it is chiefly oriented around people. I can’t easily visit Erin’s mas.to or your social.coop.
But root identity provisioning needs to be extricated from all of the above, in favor of the #nomadicidentity which Bluesky has gotten 80% figured out already and working in practice.
Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy’s Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps...
@BeAware hey, I think #socialWeb seems to be more accessible than #fediverse. The latter is jargon, which is not necessarily a bad thing, but has no meaning to those outside of the in-group.
If you’re interested in checking out a #fediverse-based alternative to Reddit, come check out infosec.pub! It hosts a number of communities including one I’ve stood up for #cybersecurity / #infosec!
"Care has been taken to construct it in the simplest way possible, enabling contributions from programmers of all skill levels and keeping server costs down. This will greatly speed PieFed's development process and widen its adoption."
Clever move by @rimu Lemmy's development is struggling.
The most popular instance, lemmy.world (>25% monthly active users), is still on a previous release. The current release, 0.19.1, has broken federation for the past couple weeks. Up-to-date instances are hobbling along by being restarted every few hours.
Tried hacking on Lemmy myself... I've got many thoughts but not sure if/how to write them down.
"Meta's fediverses", federating with Meta to allow communications, potentially using services from Meta such as automated moderation or ad targeting, and potentially harvesting data on Meta's behalf.
"free fediverses" that reject Meta – and surveillance capitalism more generally
The free fediverses have a lot of advantages over Meta and Meta's fediverses, some of which will be very hard to counter, and clearly have enough critical mass that they'll be just fine.
Here's a set of strategies for the free fediverses to provide a viable alternative to surveillance capitalism. They build on the strengths of today's fediverse at its best – including natural advantages the free fediverses have that Threads and Meta's fediverses will having a very hard time countering – but also are hopefully candid about weaknesses that need to be addressed. It's a long list, so I'll be spreading out over multiple posts; this post currently goes into detail on the first two.
Opposition to Meta and surveillance capitalism is an appealing position. Highlight it!
Focus on consent (including consent-based federation), privacy, and safety
Emphasize "networked communities"
Support concentric federations of instances and communities
Consider "transitively defederating" Meta's fediverses (as well as defederating Threads)
Consider working with people and instances in Meta's fediverses (and Bluesky, Dreamwidth, and other social networks) whose goals and values align with the free fediverses'
Build a sustainable ecosystem
Prepare for Meta's (and their allies') attempts to paint the free fediverses in a bad light
Reduce the dependency on Mastodon
Prioritize accessibility, which is a huge opportunity
Commit to anti-fascist, anti-racist, anti-colonial, and pro-LGBTQIA2S+ principles, policies, practices, and norms for the free fediverses
Looks like the #threadiverse has been widely used by the #Lemmy and #Kbin communities for years, but now it's slowly being co-opted (including by #Meta staff) to refer to the #federation of #Threads.
I predict a complete takeover of the #hashtag, and term in general, before the end of 2024.
Copie Publique : Code Lutin investit 3333 € pour soutenir le développement du threadiverse
Tous les ans, avec @copiepublique, nous versons 1% de notre chiffre d'affaires pour soutenir le libre et les communs numériques. Parmi d'autres projets, nous allons verser 3000 € au projet Lemmy et 333 € pour /kbin afin de rendre le pouvoir aux internautes.
Nous cherchons des entreprises prêtes à rallier #CopiePublique, faites signe !
OC Lemmy's Image Problem (wedistribute.org)
The popular Reddit alternative's user count has grown a lot over the past year. One problem, though: users and admins can't delete images.
OC Sublinks Aims to Be a Drop-In Replacement for Lemmy (wedistribute.org)
Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy’s Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps...