Came across some #threadiverse compatibility issues in @toddsundsted's Ktistec project posted by @rahul (← this account is a #Ktistec instance) and it made me think: I would love to have a fediverse compatibility "issueathon" where we make a super list of everything that we expect to work across the fediverse and where all the issue are at.
I'm in agreement with her. While I'd like things would be different, I don't see how people can think that the fediverse / #threadiverse as it stands now is a suitable replacement for Reddit. The entire labour strike on Reddit is centered around inadequate community moderation tooling and their API-reliant alternatives threatening to become unavailable.
Lemmy is fediverse's main answer to Reddit. Moderation tooling in lemmy is severely lacking and admins put themselves and the communities they host at risk by using that software in federated mode. I wrote this github issue over a year ago: https://github.com/LemmyNet/lemmy/issues/2277 very little has changed since.
In it, I give the example of a user account where description avatar are all slurs and hatesymbols. The account is replicated across all Lemmy instances that existed at the time that account was made, and admins can do nothing about it. For fun: try to change the domain name of the account to any lemmy instance that was around at the time.
The way the main devs are handling that issue also does not inspire tremendous confidence. I'd say in a trusted group lemmy is mature enough to use, but definitely don't turn federation on..
A note on the current #Threadiverse expansion: As a few have pointed out, #Lemmy and #Kbin are OK, but as far being Reddit replacements, remember that neither software is really stable or mature, especially in terms of moderation. It'll be a while before we can really consider either one as a good place to build a community.
I wish my main #federation account could easily plug directly into the #kbin and #lemmy clients that I currently use without me having to host my own #threadiverse instance. So the #Mastodon instance I currently host would be a recognized login option in any threadiverse app that I install.
Reddits Community/Subreddit-Architektur ist wie gemacht für eine verteilte Alternative. Passt sogar weitaus besser als beim Microblogging/Twitter. Bin gespannt ob hier noch stärkeres Momentum reinkommt. #reddit#threadiverse
Just want to announce: @cendawanita will be my main posting account for Malaysia and SEA newsy stuff. This is since I'll be posting to m/MagASEAN anyway (you can follow here @magASEAN but just fyi you won't see any posts anyway - kbin doesn't federate that way (yet?). This way I won't clog up my local instance feed imo.
But individual users you can see their activity like normal posts, so I'll be boosting some posts from here (but not all). I'll be posting the usual TootSEA etc stuff on the microblog if it doesn't get fetched as well. But anyone also can if you @ the mag in your first line (I'm oversimplifying)
But I'll probably set up an individual mag/sub for my website as well. I do think the linkage works much much better than the current AP bridge as cross-posting.
Defederation drama hits the #threadiverse, but with the twist of community/group dynamics being a major factor: see discussion with important links here: https://lemmy.ml/post/1281130
Here defederation is concerned with open signups (lemmy.world) and beehaw’s ability to moderate effectively, where they’re finding lemmy’s tools lacking, on which see this thread on an upcoming review: https://hachyderm.io/@thisismissem/110550824230711531 (@thisismissem).
TLDR: lemmy/kbin aren’t ready yet, need 6mnths-2yrs to mature
I often feel like replies are cringe on fedi and I can never tell if someone wants replies. so that's at least one thing I'm optimistic about for kbin or Lemmy. it's nice to have posts that are clearly designed for conversation threads.
Whew. It's not open for registrations and I don't have the qualifications to open it up, but my #kbin instance has been running for over a week, close to 10 days now. The things my little instance has seen in that time has been INTENSE.
My little instance was just one of about 6, or 7 kbin instances when it finally went live, but now #fedidb lists 28 kbin servers with more coming online constantly.
Helping others where I can with information about how I managed to get mine running as well as helping others learn about #kbin has been a wild and intense experience.
I know that with more people coming to kbin that the little part that I played in these last few days will echo for a while across the #fediverse as more people join kbin and other platforms.
@contessa It’s certainly been a few really wild days recently but I think there is no need to wait to try kbin out. The flagship instance actually is in good company now with a couple more instances opening their doors to open registrations and more coming online quickly.
Because kbin presents content the way it does, migrating accounts if you want to change instances doesn’t seem like it’s going to be the same kind of experience. What do I mean? In kbin, following magazines is going to be most likely the bulk of who you care about and not individual accounts. And even with that, given the way content is aggregated and presented, it’s more likely someone will have only a handful of magazines/groups that they subscribe to.
One very interesting question that has always been there but now is more pressing is how to manage the “same magazine/group” that exists on different instances. Since each instance can have their own “humor” magazine/group, humor @ instance1.com is technically a different magazine/group than humor @ newinstance.net. How can a user “group” those two together in their own “personal front page” so they can see and interact with them in an organized way? There are lots of ideas being shared and it will be interesting to see which ones are more popular to try and answer that question.
Kbin is going to be seeing a lot of changes in the next days and weeks, likely really quickly, too. Giving it a try now and experiencing the Fediverse and the #threadiverse as it grows will be a good opportunity to see a very different way of using decentralized platforms and what kinds of ideas generated from this growth can be used to help improve other platforms like Mastodon or Calckey or Pixelfed.
That’s a long-winded way of saying, “Try creating an account now and spend a little time experiencing how the model works. Capacity is growing rapidly and the feeling is that it will continue. Spinning up a new instance is still very challenging but also rapidly getting easier.”
Looks like #Lemmy and #Kbin keep being mentioned together, which to me suggests we might have averted "mastodonization" of the #threadiverse — i.e. a situation where the whole network gets identified with a single piece of software. 🎉
@rysiek I think both options are great but at some point I think we should consider standardizing terminology. I very much prefer lemmy’s communities over kbin’s magazines. #threadiverse
@rysiek so, is Mastodon a part of the #threadiverse, and if not, what is it's segment, the #postiverse, just #microblogs. What should we call it? Guess Calckey is also in that segement.
I'd just like to interject for a moment. What you're refering to as Lemmy, is in fact, a part of the Fediverse, or as I've recently taken to calling it, the Threadiverse. Lemmy is not a protocol unto itself, but rather another free software server of a fully interconnected Fediverse, made useful by the ActivityPub protocol as defined by the World Wide Web Consortium.
Many computer users interact with a version of ActivityPub every day, without realizing it. Through a peculiar turn of events, the version of ActivityPub which is widely used today is often called Mastodon, or Lemmy, and many of its users are not aware that it is basically the ActivityPub system, developed by several independent projects such as Mastodon, Lemmy or Kbin.
There really is a Lemmy, and these people are using it, but it is just a part of the Fediverse they use. Lemmy is the implementation: the program in the server that allocates the messages to the other servers that run in the Fediverse. The implementation is an essential part of the network, but isolated by itself; it can only interact in the context of a complete federated network. Lemmy is normally used in combination with either instances of itself, or of similar projects of the Threadiverse such as Kbin: the whole network is basically ActivityPub with Lemmy as a node. All the so-called Lemmy servers are really nodes of the Fediverse!
I have never been a huge Reddit user but I am obviously fascinated by the potential migration to #Threadiverse alternatives. Tell me friends, what’s better!? #kbin or #lemmy and does it matter because they are interoperable?! 👍 🙌 #Fediverse
Signs of the #RedditMigration in action: Three of the top 6 fastest growing #Fediverse servers are not only not Mastodon.social but they are not even microblogging servers - but rather are #Threadiverse servers.
That is only seriously good for the entire Fedi infrastructure. Diversity is strength.
@technology Is there a Usenet like app/website/whatever of the Fediverse?
So, I've sort of grown up in the Usenet, and this whole Federation thing sort of feels very reminiscent of it. To the point where I'm wondering why there isn't a way to access it in this fashion? Any tips would be very helpful. I love the idea of this thing and would probably even begin running my own server if that becomes viable.
My guess is that this actually regarded as a feature in the wider #fediverse. At least in the Mastodon community it is. Toots not being searchable/indexed and you discover topics and people to follow by looking for hashtags and organically setup and control your own home feed. This, leading to much frustration for many who've moved over from Twitter.
Reasons being that it should not be easy for big tech (and others) to just slurp up and make peoples data open publicly for a wider audience through public search engines. A level of privacy and owning ones own data has been a priority over the inconvenience of not being as discoverable.
Of course the same thinking does not apply or map equally well to the #threadiverse as it does to Mastodon. I'm sure there are workarounds and a way to make this more seamless for users, but this is just getting started. It was never an issue when everything was on a small number of instances which everyone knew about.
#MeaCulpa I just realized that I was joining in the chorus of disapproval about John Mastodon driving new signups to his flagship mastodon.social server, in very strident terms, despite having made excuses for the matrix folks doing exactly the same thing; driving new sign-ups to the matrix.org homesever in Riot/Element. I guess it just reminds me that nobody is immune from bias, however fair and balanced we're trying to be 🫣
@strypey@digitalRightsNinja What feeds a hellthread are bad ideas. So just avoid posting bad ideas that don’t solve the problem. The #threadiverse does not solve the centralization problem. It’s the best initial step we have. A migration from #Reddit to threadiverse would be useful progress. But it’s only the start of a solution not a finished solution.
Join the Kmoon Discord Server! (discord.gg)
Announcements, feedback and feature request. Plus I'll be posting technical jargon for the geeks in the room ;)...
OC There is a lesson to be learned here
TL;DR: We should bring blogs (self-publishing) back instead of putting all our knowledge into other people's websites....