rysiek

It used to be deployed on the same IP address as lemmy.ml. I don't have the receipts. Take it or leave it.

Edit: another person corroborating the claim that Lemmygrad used to be deployed on the same IP address as lemmy.ml.

I did not say "lemmy = tankie", I said Lemmy has certain tankie baggage, and that is in fact true. The developers are pretty clearly tankies, they also run a strictly tankie instance (Lemmygrad; many Lemmy instances do not federate with it).

Pretending this is not the case is not going to help in the long run. It might slow down the "unreddit" movement now, but I'd wager a bet it will make it more long-term viable and resilient, if people understand that choice of instance is important (there are quite a few great Lemmy instances that I would recommend wholeheartidly, like BeeHaw), and that there are alternative, independent implementations on Threadiverse (like Kbin).

Yes. Check out the biggest currently active instance of Kbin, https://fedia.io/ — plenty of stuff from Lemmy instances.

This is a very good point! I don't think microblogging is "all" about specific people one follows, but I agree with the observation that component is definitely more important there than on the threadiverse.

If you had the same username on GMail and Hotmail, would it be the same account, or two?..

Yup. But I do see it as potentially enabling people to migrate towards fedi, off of Meta instances, more smoothly than now. Some fedi instances will probably federate with Meta's instances, so one could have an account on a non-Meta instance (thus having access also to fedi instances that block Meta), but stay in touch with contacts on Meta instances.

That just might be enough to pull people towards greener pastures over here. 🙂
I am pretty sure that people who already migrated to fedi will mostly not want to migrate back to Meta-owned instances. So it seems to me like it might be a one-way street. Which would be good!

What I really worry about is two things:

• Meta slurping data from fedi — but they can do that already even without running any instances, as far as public content is concerned;
• additional, potentially insanely huge, load on the moderators of fedi instances that choose to federate with Meta instances.

is the fediverse and the threadiverse the same thing different names?

Yeah, Threadiverse is a part of Fediverse. I can interact with Lemmy/KBin discussions from my Mastodon account, for example.

In other words, "Threadiverse" is just a convenient way of referring to Reddit-shaped Fediverse instances, if that makes sense.

kbin.social is kinda sorta not dealing well with the sudden traffic.

Try: https://fedia.io/

Completely different codebase, written in PHP instead of Rust.

Maybe I should clarify with “each user successfully spun up…” I’m mostly curious if the 5000 microservers trying to federate is a more sustainable access pattern than 5000 users hitting the website.

Sustainable in what sense?

It's way more sustainable in the sense of "one website is not controlling the entirety of the experience of a given type of service for 5000 users", for example. I think it's important to talk about specific kinds of sustainability, and specific threats to it.

Things to consider (apart from bandwidth-related considerations):

• technical knowledge necessary to safely and securely run and maintain a service
• space, time, and resources (including financial) to do so
• ability, willingness, and energy to moderate a service (this is where Big Tech platforms are falling flat on their faces, for example, and where smaller fedi communities work pretty damn well)

These are just two different software projects that a Threadiverse instance can use. They federate with one another, so it doesn't matter all that much if you have an account on a Kbin instance, or a Lemmy instance. The differences are in the interface, some functionality, and the tech stack used (Lemmy is written in Rust; Kbin in PHP).

There are 100+ instances of Lemmy, and ~10 instances of Kbin. Kbin is a much younger project (hence it might get missed), and it's main instance, kbin.social seems to be experiencing more issues with the wave of new registrations. If you want to try Kbin, https://fedia.io/ might be a good instance to check out.

A lot of fedi instances will block any Meta-owned instances on sight. Some will not. How it plays out long-term depends a lot on how well Meta instances get moderated.