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
Laywer up, delete facebook, hit the gym.
So they’re switching registrars, right?
Seems it’s resolved
The domain is slowly recovering. Many users are able to connect to our systems again. Some might need to wait for DNS propagation.
Thank you so much for your patience. We’re sorry for the serious disruption.
We haven’t yet received an official response from Namesilo’s abuse department about the incident.
https://social.anoxinon.de/@codebergstatus/117637187711177698
Getting a report on the abuse you received from the provider is unlikely to be forthcoming. Just look at the Trump Epstein files for more context.
Update: We have received the confirmation that our domain was suspended and our case got forwarded to the abuse team.
Wtf? Why
Because their are no consequences for companies and lawyers that lie about copyright.
If the managers signing on things got perjury charges and lawyers that don’t do any due diligence got disbarred this would happen much less often.
And apparently Namesilo will shoot first ask questions later. Proceedings and deadlines on legal requests are weeks ro months, there is never a reason to silently disable something with no warning.
Competent registrars will also vet legal requests for at minimum basic validity.I’m pretty sure they have to, no? Or they will be held accountable themselves? That’s why youtube tends to ban videos before investigating.
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.
You basically get what you pay for. There’s a reason big companies use MarkMonitor instead of “off the shelf” registrars.
the lovely US motto of inventing a problem to sell you the solution. this shouldn’t be an issue to begin with

Found in the topic on [email protected] - https://sopuli.xyz/post/54751299
c:\windows\system32\drivers\etc\hosts for those still stuck with an legacy OS
Wait, is
C:/windows/system32/drivers/just a silo for stuff microslop copied from Linux?I would assume this is a remnant of Windows’ POSIX compliance decades ago.
That sounds reasonable. I checked some old backups and there’s not much else (at least in this location), but also
services,protocolsandnetworks, which are also shared with linux. (On linux,serviceslets you define the name given to certain ports, so e.g. whenlsof -i :22000would usually show entries with :22000, you could then addsyncthing tcp/22000 \nsyncthing udp/22000and hboth uselsof -i :syncthingor also with any lsof results see that port show up as:syncthing.
Btw. the same is true with ips and names inhosts, so if you have local static ips it can be nice to give devices entries inhostsjust for that, to make connections more readable.
like, “drivers” you know… but they copied it from some BSD I assume…
Not related to the codeberg issue, however I recently learned that this simple file can circumvent DNS ban from my ISP ^^.
I’m always amazed how all our complexe infrastructures are actually based on something so simple and elegant :D
Theres an easier way to achieve this: don’t use your ISP provided DNS resolver. Use something like quad9 instead.
Haha yeah my answer is not a 100% complete :) I do use qaud9 with my pihole, but my country is also going to block quad9 in the futur.
my country is also going to block quad9
Me thinking: I bet it’s France
in the futur.
Yep, that’s a French native speaker alright 😁
xD Oh yeah? What would be the correct syntax if I may ask? I’m doing the best I can you know :((
Future
Your English is great.
PSA: They also delayed a security update because of this incident
https://mstdn.ca/@[email protected]/117636334564654241One of the reasons why I like to host my own infrastructure, and the codeberg guys let you do it with their forgejo software.
It’s just trying to catch up to GitHub’s outages
I speculate that it was microsoft attorneys that pulled this stunt







