Top
Best
New

Posted by HumanCCF 23 hours ago

.self: A new top-level domain designed to support self-hosting(hccf.onmy.cloud)
644 points | 357 commentspage 2
nilslindemann 17 hours ago|
States could grant such domains when individuals register their identity, for example, "klaus-mueller-<close eyes say first word that comes to your mind>.self". It runs on a VPS, and it is well documented how to create and run a website on that. School kids are introduced to it. Would be an excellent entry point into digital sovereignty for citizens.
HumanCCF 16 hours ago||
Enabling digital sovereignty for individuals is our foundational motivating principle!
severak_cz 10 hours ago|||
Except that Klaus Mueller is definitely not unique name. Human names are not that unique.
DocTomoe 14 hours ago||
Please leave states out of this. The State™ is not your friend, and we don't need a future, even more criminal government to have access to the shutdown button of even more of our identity.

Note that I did not single out an individual coutnry. All governments always stride towards autocracy.

hananova 21 hours ago||
It simply cannot be both free and free choice of domain.

If it has both, it will be squatted to uselessness, and blocked everywhere because of phishing scams everywhere.

You can either make the domains cost money, which seems counter to the entire point, or disallow choosing the domain, instead handing out free what3words style names.

HumanCCF 21 hours ago||
We have considered this, all of these things will be examined during the evaluation process of the application with ICANN before any approval to operate the TLD is granted. We could also police our domain and revoke users who use it for abuse but that may be too costly. But you are right that fundamentally we must protect the reputation of the TLD at all costs and that will require imposing certain limits on its use.
applfanboysbgon 21 hours ago||
You should read their proposal. Specifically, the first "core feature": one person, one domain. If you want to squat on a domain, go for it -- it's yours, and that's the only domain you're getting.

I suppose this will be done by ID verification, which is a complete and total non-starter for me, but they do have a vision of some kind.

hananova 21 hours ago||
I've read it, I don't believe it will be effective, even with actual physical ID verification. Scammers can get more IDs, for example by way of scamming.
socalgal2 1 hour ago||
reading the comments on the site itself makes me think this is one of those "oh, I think found a way to get free money from governments". It doesn't feel like it's being done by someone with genuine knowledge of domains, nor an actual mission. I sounds more like a "deal maker" figuring out a way to get rich by creating an NPO
stanfordkid 22 hours ago||
I don't fully understand how this works... who regulates and defines what is "self-hosted" or "ethical technology"... I feel you can't really solve the distributed consensus and governance problem by just introducing a new domain suffix.
onel 10 hours ago||
I actually think this is a really good concept. There is no perfect solution for what they're trying to do, but I think they have most of the things covered.

Offering one free per person is nice, it can be tricky to enforce but I think doable. Regarding privacy, even right now ICANN rules require a real name and address for the domain.

This project comes at the right time when because I see a lot of interest growing towards self-hosting.

I am biased though, I've been working on on OS for self-hosting , fully open source, Debian based, no restrictions https://github.com/malmoos/malmo

hk__2 8 hours ago|
> it can be tricky to enforce but I think doable

It’s not doable at all. There are millions of people that don’t need a domain but would be happy to be paid $5-10 by some random scammer to hand over their domain.

onel 8 hours ago||
That's true. But I think it's the same case as a bad actor owning a domain for himself. They still need to do some policing so it doesn't pull down the whole TLD
prepend 20 hours ago||
I tried to leave a comment and it errored out and said “please leave a valid email.” I tried 6 different addresses at prepend.com.

It’s weird when sites have invalid email checks.

tepitoperrito 10 hours ago||
This sounds great in theory, and if you're capable of managing your own DNS servers already possible for US citizens (via locality domains). Who's gonna front the cost of resolving queries for these domains WAS my question... answered by user HumanCCF above: their sponsors and individual donars will (since they plan on operating the service as a "public good" I imagine with a strong technical team they could actually do it! I wish them the best.)

I definitely can appreciate the principles they're espousing even if I'm not gonna be giving them my dollars. More people should care about making sure technology serves humans, not vice versa :)

Locality domain (RFC 1480) rant: Who the heck is Multi-Paradigm Corporation and how come emailing us-dom2@i-theta.com with all of my "T"s crossed and "I"s dotted to register a domain results in silence. No response, not even a "go away".

I know there's some localities where you have to have notarized authorization on city letterhead but they're mostly administered by the people behind https://www.about.us/locality-structure

https://locality-domains.pages.dev/ is a good reference if you don't have WHOIS installed btw. I can't vouch for how up to date it is though since I just query the database myself.

samgranieri 21 hours ago||
I’m just using .home.arpa for my self hosted stuff. Free, just have to deal with TLS root cert trust, but once that’s down; you’re golden.
ahoka 20 hours ago||
.internal works fine now.
DocTomoe 14 hours ago||
Both of these are meant for operating a home/private network.

.self seems to be geared towards a 'accessible from the everyday net' kind of approach.

ahoka 2 hours ago||
Right.
kaelwd 14 hours ago||
I just use .home, yeah I know it's not reserved but idgaf I'm not writing .arpa.
rcarmo 12 hours ago||
We could fix a lot of this by just making sure .local (which is used in Bonjour/mDNS) could coexist sanely in mixed resolver environments _and_ could support subdomains. I built https://rcarmo.github.io/projects/mdnsbridge to “fix” it for my particular use case, and if it wasn’t for TLS shenanigans and the lack of subdomains, my issues largely went away.
myshapeprotocol 3 hours ago|
I'm currently documenting my research on this at myshape.com/genesis-100.html—would be keen to hear if others are tackling the continuity verification problem from a similar angle.”
More comments...