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

@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.

@cy@mstdn.io @Hyolobrika@mstdn.io @roboneko IIRC the REST subsystem is used by the re:claimID browser plugins.

Having a JSON interface for node services is nice. E.g. you can have your own DoH provider in no time.

@Hyolobrika@mstdn.io Where did you get that? Their solution to Zooko's is asymmetric crypto, petnames, pinning & delegation. Certainly not some central authority, that would be bonkers.

> For the case of the exomoon candidate Kepler-1625b-I (Teachey & Kipping 2018) we showed in Fig. 2 that the largest stable submoon is Vesta- to Ceres-sized. The largest possible submoon would thus be roughly 5–10 km in radius. For much less massive, Solar system-like moons the largest stable submoon was ∼10 km such that the largest possible subsubmoon would be sub-km-sized.

Amazing! Add some trojan neighbors here and there and it would be a fun place to navigate around. Something like Interplanetary Transport Network, but crunched into a cisplanetary space.

@luci curses-based

https://academic.oup.com/mnrasl/article/483/1/L80/5195537

> For more massive stars, the habitable zone is more distant and habitable zone planets have wider Hill spheres. Large moons can therefore survive on more distant orbits and have larger Hill spheres such that submoons can exist on wider orbits where submoon–moon–planet tidal evolution is far slower, as compared with lower mass stars.

(Yes, the Moon could have had a submoon.)

@meejah Rust and Elixir are certainly going to teach you a thing about ownership and message-passing concurrency.
Haskell gives more clarity in more fields overall.

So, yeah, a tour of Rust and Elixir, then a dive into Haskell.

@mia :vkcube: