For a brief hopeful moment, I thought this was the .io kind of sandstorm

> my deepest fantasy is that one day I'll be in the hospital for some random thing, they'll take blood for some test, and then when they read the results, their eyes will go wide and they'll call for a consult. The other doctor will read the results and say "you don't have the nutrient?! How do you live? You're so brave". They give me a shot, and just like that, I'm able to conduct myself in society, understand social cues, hold my attention on anything i want for any length of time, etc

... so perhaps the Nutrient is a product of a gut bacterium.

> Radicle supports private repositories that are only shared among a trusted set of peers, not the entire network. These are not encrypted at rest but rely on selective replication and are thus completely invisible to the rest of the network.

There's no structural separation of public / private repositories; this is one bug or fat-finger away from a leak.

I was looking into how to get a radicle node running, but connected to only my own devices.

You can't seem to start the radicle node without it automatically connecting to the (generously provided) global shared seed nodes, and you can't examine/change the config without starting the node (at least with rad subcommands).

If you do `rad auth` and then delete the four seed addresses from ~/.radicle/config.json before starting the rad node, it helpfully re-adds them on startup:

  [...]
  INFO  node     Opening node database..                                                                                                                                                                           
  INFO  node     Address book is empty. Adding bootstrap nodes..                                                                                                                                                   
  INFO  node     4 nodes added to address book
  [...]

Not exactly a subscription since it's a stored-balance system, but still.

Is this because of the Palantir / techbro culture that the author is immersed in, or for some systemic or economic reason?

How could they not? When I penciled this out ~18 years ago, I included the amortized cost of all the interviews it took to hire a given engineer as well. It's not rocket surgery, as they say.

Money can be exchanged for goods and services.

[0] https://books.google.com/books?id=VO4OAAAAYAAJ&pg=PA464#v=on...

https://en.wiktionary.org/wiki/ablative_case

  $ asdf
  $                  # now kill ring is ["asdf"]
  $ qwerty
  $                  # now kill ring is ["qwerty", "asdf"]
  $             # "yank", pastes the thing at the top of the kill ring
  $ qwerty      # "yank-pop", replaces the thing just yanked with the next
                     # thing on the ring, and rotates the ring until the next yank
  $ asdf

You can load modules and then fork child processes. Children will share memory with each other (if they need to modify any shared memory, they get copy-on-write pages allocated by the kernel) and you'll save quite a lot on memory.

One tricky thing about nginx though, from the "If is evil" nginx wiki [0]:

> The if directive is part of the rewrite module which evaluates instructions imperatively. On the other hand, NGINX configuration in general is declarative. At some point due to user demand, an attempt was made to enable some non-rewrite directives inside if, and this led to the situation we have now.

I use nginx for homelab things because my use-cases are simple, but I've run into issues at work with nginx in the past because of the above.

[0] https://nginx-wiki.getpagespeed.com/config/if-is-evil