Lemmy.World Announcements

29079 readers

218 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

DM https://lemmy.world/u/lwreport
Email report@lemmy.world (PGP Supported)

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Join the team

founded 2 years ago

MODERATORS

ruud@lemmy.world

lwadmin@lemmy.world

lwCET@lemmy.world

jelloeater85@lemmy.world

Serinus@lemmy.world

lw_mod_notification@lemmy.world

MrKaplan@lemmy.world

297

Beehaw defederating effective immediately from lemmy.world and sh.itjust.works (beehaw.org)

submitted 1 year ago by gary@lemmy.world to c/lemmyworld@lemmy.world

288 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] fubo@lemmy.world 19 points 1 year ago

From a purely operational standpoint, rapid growth stresses a network service not only in its technical capacity, but also in the ability of the service's operators to keep up with fighting fires. Engineering capacity to work on a service is itself a limiting factor on healthy growth.

If the tools aren't yet there to mitigate a rapid growth in abuse problems, then it just makes sense for them to limit their exposure to the rapid-growth part of the network. It takes time to write those tools.