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

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

- Mom, I want wa ch zod ahaaskes rea.
- We have wa ch zod ahaaskes rea at home.
Wa ch zod ahaaskes rea at home:

@cancel Holy f...

@freeschool The "inside" part is a riff off the original "inside the country".

But you really can treat it as a real thing and move towards it.
The problem is (at least) two-fold:

1) Own what you are. Personal identity management, private keys and metadata, stuff like this. A modern solution here are hardware tokens, esp. with on-device cryptography processing. A bit forward into future and we'll start seeing implantable stuff. Yes, we have implantable NFCs and stuff like that, it's just not particularly capable/interesting.

2) Own what you have. The bulk data storage question. You can't implant a few dozen TBs. But this can be reclaimed with pervasive connectivity when aided by (1). And we also have at least preliminary solutions here with p2p tech.

With a bit of effort you can commit your private keys to your meat memory. Then walk with your stuff through any country border without it getting noticed. The only problem would be Alzheimer's. And a need for external trusted cryptography hardware to actually run the algos.

Arguably the #GNUnet project has some capabilities for both 1 and 2. It "just" needs to gain more traction.

@meejah Haskell, this time for real