l'empathie mécanique @dpwiz@qoto.org

@cy@mstdn.io No, ffs. DNS is irrelevant in gnunet. The whole bag of web crap can be left behind. That's the point.

@xenmen Too bad computers making decisions will eat competitors for lunch. (And then, the rest of the world.)

@cy@mstdn.io @roboneko @Hyolobrika@mstdn.io DNS is just a common protocol for apps to resolve keys into values, with features like delegation and TTL. Same with GNS. You can have a bunch of TOR addresses pinned by your own private key, accessible from anywhere on the network. Or files. Or app-specific data.

ReclaimID is the inverse of "Login with Facebook". It is "you can ask me if I still want to share stuff with you".

So, those aren't just some configuration pieces exposed to as JSON. But you'll have to read up some nice materials to make sense of the data.

@cy@mstdn.io @roboneko @Hyolobrika@mstdn.io huh, what?..

@cy@mstdn.io @roboneko @Hyolobrika@mstdn.io DoH is DNS-over-HTTP, a tech to stop providers and pretty much everyone else to snoop on you and poison your query results.

re:claimID is like reverese OpenID. You publish the attributes and the servers are requesting them to authenticate you.

@Hyolobrika@mstdn.io The web
links are name-centric, pointing to whatever the content is currently provided by whatever the authority managed to receive your request. Ephemeral and basically worthless. "Good URLs don't break", hear, hear. PKI is FUBAR, servers can 4xx and 5xx at you at any time or go black entirely. It's a little miracle we can serve stuff on localhost, and a divine intervention that the big web works at all, at least sometimes.

@Hyolobrika@mstdn.io And discovery is broken even more. It is unnecessary hard to find shit without sucking some corporate cock.

@Hyolobrika@mstdn.io Anyway, it doesn't matter. It wasn't naming that's broken, it is the linking model that gone wrong. DNS given the promise it couldn't fulfill without forcing everyone to succumb to the network effects.

@Hyolobrika@mstdn.io How would the real solution look like?

@mitchconner @Hyolobrika@mstdn.io @Moon
> .BIT DOMAINS
> Decentralized domains using
Namecoin cryptocurrency.

No.

@Hyolobrika@mstdn.io There are no TLDs in GNS. Not like ICANN runs it. Every PKEY is its own TLD.

Tell me your PKEY, and I put it under whatever the name *I* want. You don't even have a say in that. Think user bookmarks, not global registry of stuff.

If you have to tell me about some stuff you publish, you suffix it with your PKEY. But most of the time, GNS isn't a right level of abstraction to work with.

@cy@mstdn.io @Hyolobrika@mstdn.io @roboneko You don't need a REST API to fetch files. If anything, REST, HTTP even is unsuitable for high-latency P2P fetching.

If you want a browser running on a such a network you can invoke `gnunet-download` to crawl the URLs you encounter.

@Hyolobrika@mstdn.io > With blockchain, AFAIK there is no tradeoff.

IPFS struggles a lot with their blockchain NS. Last time I've checked, they were converging on reinventing the GNS wheel.

@Hyolobrika@mstdn.io The `.pin` zone is not a registry of "all the TLDs out there". Your GNS config is.

So,

> What happens when two top-level zones with different private keys and owners have the same name?

isn't possible.

You can only bind one PKEY to a zone.

@Hyolobrika@mstdn.io I just checked the distro. There is a `.pin` zone where everyone can submit their names and keys, but IDK, that's just a silly "early days" thing.

The old `.gnu` zone was a hack to wrestle old-world browsers from ICANN controls. It is basically what a "localhost" is.