139
lemmy.world and .ml down
(lemmy.name)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Jul 2023
139 points (100.0% liked)
Chat
7499 readers
25 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Even more of a reason to
1 - have an account on multiple instances
2 - support multiple instances. Can't take everyone down at once!
First account: vlemmy.net - went down 2 days later Second account: lemmy.world - has been DDOSed twice and hacked once the week after making the account Third account: this one.
Which instance do you want me to tank next? Apparently I’m pretty good at it!
lemm.ee! The lead admin is top notch, he contributes directly to the lemmy codebase and implements his working mods there before they get accepted. He was also one of the key helpers in the first lemmy.world hack (which incidentally lemm.ee was immune to).
I don’t think it’s in anyone’s best interests to encourage mass users to any single instance. That “everybody get in this same room” behavior is part of the problem.
Lemmy and the fediverse depend upon users distributing themselves across many reliable instances. More users in a single instance equals more demand on that individual server and more vulnerability based on that single server’s status.
While I agree with that, lemm.ee doesn't seem to be dominating much. It isn't even top 3 - the top 4 in my understanding is lemmy.ml, lemmy.world, beehaw.org and sh.itjust.works (in the order they fell out my brain). So I don't feel guilty cheerleading for it, at least not right now.
However in terms of user experience, lemm.ee has been by far the most reliable for me. Afaik it was the first to have a truly stable version of v0.18 (he didn't upgrade right away, but implemented a modified version of a release candidate of v0.18.1).