1
Why have we started blocking lemmy.world? (NO LONGER BLOCKED) (files.catbox.moe)
submitted 3 years ago* (last edited 3 years ago) by to c/sdfpubnix@lemmy.sdf.org
3 comments fedilink hide all child comments
 

UPDATE: @SDF@lemmy.sdf.org has responded

It is temporary as lemmy.world was cascading duplicates at us and the only way to keep the site up reliably was to temporarily drop them. We’re in the process of adding more hardware to increase RAM, CPU cores and disk space. Once that new hardware is in place we can try turning on the firehose. Until then, please patient.

ORIGINAL POST:

Starting sometime yesterday afternoon it looks like our instance started blocking lemmy.world: https://lemmy.sdf.org/instances

A screenshot of the page at https://lemmy.sdf.org/instances showing the lemmy.world instance on the blocklist

This is kind of a big deal, because 1/3rd of all active users originate there! A pie chart depicting the top instances by usershare. The lemmy.world instance is in the top spot with 1/3 of the total usershare

Was this decision intentional? If so, could we get some clarification about it? @SDF@lemmy.sdf.org

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 3 years ago*

Killer stuff! Sorry for my contributing undue pressure on top of what was probably already a taxing procedure happening in the server room.

Out of curiousity: how do you feel about Lemmy performance so far? I'm actually a little bit surprised that we already managed to outstrip the prior configuration. I suppose that inter-instance ActivityPub traffic just punches really hard regardless of intra-instance activity?

  • permalink
  • fedilink
  • source
  • parent