@digitalRightsNinja@fedi.at
@digitalRightsNinja@fedi.at avatar

digitalRightsNinja

@digitalRightsNinja@fedi.at

Este perfil es de un servidor federado y podría estar incompleto. Explorar más contenido en la instancia original.

maegul, a fediversenews en
@maegul@hachyderm.io avatar

settles on its big central instance: lemmy.world () run by @ruud

Its numbers are now big enough to be counted amongst the top 5-10 masto instances! (https://fedidb.org/network/instance/lemmy.world) as become the “second platform” by size.

Apart from running it well and keeping up to date (recent update seems to have gone well, with a nice example of instances and admins helping each other!?), some redditers seek the big instances?? Curious how communities will adapt.

@fediversenews

digitalRightsNinja,
@digitalRightsNinja@fedi.at avatar

@md @maegul @ruud @fediversenews

Note as well that Lemmy World is now centralized by Cloudflare. If only they woudn’t hide that fact & inform users about the consequence, perhaps more users would be steered toward a balance.

digitalRightsNinja,
@digitalRightsNinja@fedi.at avatar

@ruud @md @maegul @fediversenews

Insufficient. It needs to be on the registration page. It’s unlikely that non-uses would have received the announcement prior to registration.

digitalRightsNinja,
@digitalRightsNinja@fedi.at avatar

@ruud
Whenever a site starts using as an attack response, they almost never mention it or the consequences. When pressed about it, the “I’m under attack” PR move is just an excuse/cover for action. A reluctant CF user should take the opportunity to fully inform users.. have statements like “we are using CF under protest & are exploring alternatives; plz be aware that your usernames, passwords, DMs will all be visible to Cloudflare Inc. until we recover, and some segments of readers will be unable to read your posts”.. etc.

In any case, I’m grateful that it was at least announced to users & that new registrants may also get the msg. It’s a shame most users don’t really grasp the consequences.

@md @maegul @fediversenews

digitalRightsNinja,
@digitalRightsNinja@fedi.at avatar

@ruud
I had a list of competing commercial alternatives somewhere.. maybe I can dig it up. But I would certainly touch base with jerry@infosec.exchange because I think he dealt with attacks quite cleverly without having to use CF or any MitM of that kind. Part of his solution involves standing up an onion host & redirecting tor traffic there. But before that step, he has a way of tar-pitting suspicious traffic on the clearnet side. There is also a fedi user “tallship” who suggests having a few VPSs geographically spread out and load-balanced with some fancy DNS stuff that’s over my head.

digitalRightsNinja,
@digitalRightsNinja@fedi.at avatar

@ruud There’s also a baby step in the right direction that can be taken to minimize CF exposure until a permanent fix is established: a site can use a Cloudflare NS service but not the reverse proxy service. When the server load hits a set threashold it can turn on the CF proxy on-the-fly until the load drops. So at least during off-peak moments users have a chance at not being exposed to or blocked by CF. This approach is used by forum.fail and kbin.social, last time i checked.

  • Todo
  • Suscrito
  • Moderado
  • Favoritos
  • random
  • noticiascr
  • CostaRica
  • Todos las revistas