As you probably noticed, our domain codeberg.org is entirely unreachable. It was registered with namesilo and entirely disappeared from our account. We’re waiting for their customer support to investigate the situation. No, we didn’t forget to renew. There are no suspicious logins in the login history. There is no entry about the situation in the account’s domain history. We’ll try setting up a workaround on our codeberg.eu domain ASAP.

Update: We have received the confirmation that our domain was suspended and our case got forwarded to the abuse team. We’re still waiting for a final decision.

We decided not to enable codeberg.eu as a quick workaround: There are several technical difficulties (e.g. multi-domain support, SEO, Two-Factor-Authentication). The benefit of a temporary workaround compared to the effort is quite low (updating all the Git remotes and other references). We hear you about domain resiliency and independence from a single point of failure. However, activating a second domain is a long-term project and nothing we can pull of within a few hours.

https://social.anoxinon.de/@codebergstatus/117636437840688845

  • redjard@reddthat.com
    link
    fedilink
    arrow-up
    2
    ·
    14 hours ago

    Not immediately, no. The timeline scales with the coarseness of the tools of the respective level. Platforms themselves have to act within a few hours of being notified (regulations vary place to place and depend on hosting location not tld location, the worst I recall seeing is 4 hours), but registrars even for the highest priority stuff in the worst jurisdictions get at least a week.
    Because while the platform would be able to block content directly, the registrar can only take down entire pages.
    Generally registrars do (voluntarily) act quickly in serious cases, but the better ones only with manual review, for situations like phishing, csam, …

    If it weren’t structured like that, you could go to any website that lets you upload stuff, upload illegal content, and then go to the registrar to report it and get the page taken down.
    This was done to lemmy instances in the past iirc, but out of the registrars own volition. Changing registrars or registrars improving their policies has to my knowledge largely eliminated that.

    Even the week-scale timeframe leaves the option open to delay this until a court order. Ultimately only courts have the authority to force domain takedowns, so if you are prepared to sue and the registrar doesn’t sabotage you, you can keep everything up until at least a preliminary court order tells you or the registrar otherwise.

    • Glitchvid@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      Companies are reasonably litigation averse, plus at least in the US you get protections as a service provider by acting first on a lot of legal requests (notably DMCA).

      That’s a big reason your registrar matters quite a bit, a lot just don’t have the legal resources to handle this kind of thing and go to bat for you. Price is a big competitive factor for the sector, so it’s not a surprise to see sparse support around legal stuff like this.

      Not to excuse the systems at play and the companies that handle it particularly poorly, but just to explain why these things happen.

      It’s also why I keep my services as separate as possible, my registrar is not also my authoritative name server provider, which is separate from my colo provider, etc.