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.
I am not sure yet. I'm trying to figure it out. I've been sending a questionnaire to a bunch of registrars with these questions. Namecheap failed spectacularly, others answered okay.
It's a red flag if they don't list a sales or support email on their website, so that's another hint too.
I am not sure yet. I'm trying to figure it out. I've been sending a questionnaire to a bunch of registrars with these questions. Namecheap failed spectacularly, others answered okay.
It's a red flag if they don't list a sales or support email on their website, so that's another hint too.
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
Dude, why am I getting negative karma? There are some real negative peope her. What the heck... It feels just like my very brief stint playing LoL, when I didnt understand how the game worked and all those jerks were giving mehr a hard time. But to be honest, I still send you lots of love.
But Codeberg is back up and running now, anyway. At least I'm happy about that.
> [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.
Where are you moving to? Are there any registrars that have promised not to do this? Can we trust any of them?
I'd rather not move once and then have to move again.
It's a red flag if they don't list a sales or support email on their website, so that's another hint too.
It's a red flag if they don't list a sales or support email on their website, so that's another hint too.
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.
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'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
But Codeberg is back up and running now, anyway. At least I'm happy about that.