Login
You're viewing the functional.cafe public feed.
  • Nov 18, 2026, 10:14 AM

    RE: social.anoxinon.de/@Codeberg/1

    This #codeberg issue is horrible and shows how your registrar can disrupt your service and - in the case of @forgejo case - prevent distribution of critical security fixes.

    This issue demonstrates that however much you want to try and keep away from #BigTech you can still end up in trouble if one part can take you out. Will be interesting to find out the cause.

    If you're affected, it seems "217.197.84.140 codeberg.org" in your /etc/hosts is a workaround (unverified. Use at own risk)

    #security

    💬 2🔄 9⭐ 1

Replies

  • Nov 18, 2026, 10:19 AM

    Given that it's gone to the registrar's (namesilo) abuse depertment it does sound like someone requested that it got taken offline completely. Hopefully they will respond quickly and get it sorted but will we even find out what triggered it? It does show what the impact of takedown requests can be.

    Maybe someone was hosting illegal material on it, but in that case would it really be valid to go directly to the registrar to get a side taken offline? Did they contact #codeberg first? Who knows.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 1
  • Nov 18, 2026, 11:13 AM

    @data0 Yeah I was running out of characters in the original post so didn't include the (likely less commonly used) IPv6 address :-)

    💬 0🔄 0⭐ 0
  • Nov 18, 2026, 11:23 AM

    @sxa I wouldn't be surprised if they had more traffic over IPv6 than IPv4 actually

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 18, 2026, 8:00 PM

    @altf4 If I had to guess: NameSilo is a US company. To react with such obedience, they must have received a rather threatening-sounding complaint. Probably from a lawyer representing some other US entity that wanted some content removed. Could've also been some kids fighting over nothing and being good at social engineering, who knows. When NameSilo then found out about the whole thing and what a potential PR disaster it could turn into, they quickly reversed it.

    💬 0🔄 0⭐ 0
  • Nov 18, 2026, 8:13 PM

    @altf4 If I were them, I'd probably consider moving to a non-ICANN tld, hosted on non-US infra. They have pointed out that they already had the same issue with a German cloud provider in the past (the country they're based in), but this would at least provide some protection against politically motivated abuse complaints.

    💬 0🔄 0⭐ 0
  • Nov 18, 2026, 8:19 PM

    @data0 but at this point, it’s just a guess. We have nothing to back up that it has anything to do with it. We don’t even know if the complaint was coming from the US if there even was one. I do agree that we prefer sovereignty. But Europeans also have terms of service and react to abuse complaints. From the info we currently have, US or EU make no difference here in this case

    💬 0🔄 0⭐ 0
  • Nov 18, 2026, 11:22 AM

    @sxa @forgejo to verify that information, just look at the rdap.

    rdap codeberg.org -w

    In there, you see the nameservers and you can then querry them.

    2a0a:4580:103f:c0de::1

    Here is the modern IP for /etc/hosts

    There you go ;-)

    💬 0🔄 0⭐ 0