@dangillmor I have seen pretty much every not-for-profit make the same shift either explicitly or covertly. ICANN was supposed to be non profit, they worked out how to charge a quarter million dollars to register a domain and they donât even pay to run the DNS root.
I see no reason not to expect Signal to do the same. The involvement with crypto-Ponzi coins showed malicious intent in my view and it is a walled garden. Only Signal can provide the service to Signal users.
@hallam @pete_wright Verisign has a $1 contract IIRC with IANA for A root. ICANN runs L root. Others are run by universities or USG, and have since before ICANN. Thatâs part of the problem. ICANN doesnât regulate the roots or have any control beyond trying to coordinate and talk with them.
ICANN even modified their bylaws to remove reference to being responsible - an acknowledgment of reality.
@thedarktangent @pete_wright Interesting, its a long time since I worked for VRSN.
VRSN still has the A and the J servers which is kinda weird since they are ANYCASTing and so they don't need two slots.
@thedarktangent @pete_wright oh I remember that being screwed up once.
Moot since they started signing the rootâŚ
@thedarktangent ICANN runs the registry but the DNS servers for the root, that is the A, B, C etc are run by separate organizations who have been doing it for years.
So VeriSign runs the A root and a bunch of other organizations run the others. When I was at VeriSign, nobody is paid to actually run the roots. Which is kinda odd when you think of the consequences of an outage.
We used to have two of the roots until we went to ANYCAST at which point we rapidly went to hundreds.
So the $250,000 fee just to look at a TLD registration strikes me as a 'yacht fund surcharge'.
Understanding where the costs actually lie, I have a scheme to provide callsigns for life at $0.10 each. They bind to a fingerprint of a public key and a set of service addresses. These would be for the Mesh Service Provider servicing the account which MAY return contact information if it is public and for a private DNS partition.
So if you register @thedarktangent for $0.10, that maps to your PGP key, your Mesh messaging and also to the DNS zone thedarktangent.m3-- where you can manage all your IoT stuff.
When you connect up your browser to your Mesh account, it can provision a service resolving the private m3-- TLD. So you can put a Web site up and give out URLs which will be permanent without paying any ICANN tax.
The original goal here was limited to allowing users to change their Mesh service providers at any time without cost, so their messages etc. would mover to the new location automatically. Then I realized with only slightly more engineering effort, I could make it self sustaining and solve the personal PKI naming problem.
I do have running code. My current focus is making E2E chat work for Mastodon and the Fediverse.