Apparently more and more registrars are "randomly" requiring clients to send copies of their passports and face selfies and other nonsense. I've heard namecheap is doing this and I emailed them and their answer was:
> [snip] "It is correct that we do not require every customer to proceed with identity and payment verification. Unfortunately, we cannot specify the criteria; this information is internal."
So randomly when they feel like it. Me and a number of customers are moving away from them immediately.
Centralization of DNS is becoming a problem. Privacy rights are being trampled. Nobody should be collecting such images unless in emergencies, and they need to be liable when they misuse it.
It seems that someone convinced the .org registrar that #codeberg is bad and so the domain name codeberg.org is currently on clientHold and thus removed from DNS.
> #codeberg's .org domain status is on "clientHold", I tried calling everyone that I could over there but no response from someone that can do something yet. ¯\_(ツ)_/¯
>
> The domain didn't expire, so I'd expect the cause is different. I'd be curious to read the writeup afterwards.
>
> https://chaos.social/@n0toose/117636269217275094
> Attention: A #Forgejo security release is scheduled for today. The patches were temporarily publicly accessible as part of the release process. Due to urgent issues with #Codeberg, we are unable to proceed with the release. We are in contact with Codeberg and are working to find a solution.
>
> We therefore currently recommend that, if you are using the internal SSH server (Docker with `ssh.START_SSH_SERVER = true`), you disable it for the time being or prevent access to it.
>
> https://floss.social/@forgejo/117636334439245475
Apparently more and more registrars are "randomly" requiring clients to send copies of their passports and face selfies and other nonsense. I've heard namecheap is doing this and I emailed them and their answer was:
> [snip] "It is correct that we do not require every customer to proceed with identity and payment verification. Unfortunately, we cannot specify the criteria; this information is internal."
So randomly when they feel like it. Me and a number of customers are moving away from them immediately.
Centralization of DNS is becoming a problem. Privacy rights are being trampled. Nobody should be collecting such images unless in emergencies, and they need to be liable when they misuse it.
It's bad that the DNS system is centralized; I wish that one of the blockchain-based decentralizing naming systems had caught on.
https://social.wildeboer.net/@jwildeboer/117636595702972996
It seems that someone convinced the .org registrar that #codeberg is bad and so the domain name codeberg.org is currently on clientHold and thus removed from DNS.
Its apparently namesilo who did it: https://status.codeberg.eu/status/codeberg
https://social.anoxinon.de/@codebergstatus/11763643784068884...
IPv4 URL: http://217.197.84.140:443
IPv6: 2a0a:4580:103f:c0de::1
Also worth try the /etc/hosts hotfix: https://sauna.social/@sm/117636439190990385
Codeberg uses secdns as dns server so i rewired my resolver to use them directly for the codeberg.org domain:
The ipv6 address is reused on both ns entries.Stressful day for the Codeberg & Forgejo crew.
> #codeberg's .org domain status is on "clientHold", I tried calling everyone that I could over there but no response from someone that can do something yet. ¯\_(ツ)_/¯ > > The domain didn't expire, so I'd expect the cause is different. I'd be curious to read the writeup afterwards. > > https://chaos.social/@n0toose/117636269217275094
> Attention: A #Forgejo security release is scheduled for today. The patches were temporarily publicly accessible as part of the release process. Due to urgent issues with #Codeberg, we are unable to proceed with the release. We are in contact with Codeberg and are working to find a solution. > > We therefore currently recommend that, if you are using the internal SSH server (Docker with `ssh.START_SSH_SERVER = true`), you disable it for the time being or prevent access to it. > > https://floss.social/@forgejo/117636334439245475
It's back since 11:15 UTC!
I guess we can rule out that ai caused it, unless namesilo is behind it.
Namesilo is the registrar
same
Yup I am seeing the same issue too.
Same here. I don't think there will be any node issues.
See the same on my side