On #Archival, #Libraries, #Analog #HumanReadable #storage and the importance of libraries as #PublicGoods.
The linked article has some unsavory takes though (particularly around gender studies), but the Fedi conversation around this thread is still interesting.
https://mastodon.archive.org/@brewsterkahle/110814840301552912
"Getting rid of physical books because we now have databases is like getting rid of sunshine because of the existence of vitamin-D pills and cod liver oil." --love that. a plea for keeping physical libraries available. (but it is key to remember that all living library collections include materials that come and also go) https://scottlocklin.wordpress.com/2023/07/28/death-of-the-physical-library/
What should I use for #HumanReadable #Configuration files?
#INI kinda sucks for a number of reasons, #JSON works but it's JSON, its derivatives are much the same but harder to parse...
Would that be a reasonably good match for #RecUtils?
#XML sucks as a user-facing anything.
I thought of s-exps but the reality of intern bombing & arbitrary execution in the Lisp reader make me rather reluctant to keep using that now.
And also that isn't perfectly portable unless I make my own reader.
Human-readable is a nice term. I should use it...
It also works great in the context of fep-2e40. The @context is machine-readable, the accompanying markdown is human-readable. This also means more writing ...
I think we may have a clash of semantics here? With βdomainβ I meant the conceptual space for which you define a formal ontology/vocabulary (i.e. domain driven design ddd:domain, not dns:domain π ). You can only use IRIβs in Linked Data, and preferably (SHOULD) they are dereferencable. In JSON-LD 1.1 chapter 3 it says: Furthermore, developers and machines are able to use this IRI (by using a web browser, for instance) to go to the term and get a definition of what the term mean...
@StarLitJazz
And Cloudflare's emergence has nothing to do with the controlled demolition of comedy and the rise of CentralBankDigitalSlavery.
Our pet peeve is how under the guise of safety they had to make the URLs go from 16 characters to 50 characters.
Gotta futureProof #Tor for the year 34288.
I2P stands for #InvisibleInternetProtocol.
Some benefits of #I2P over Tor:
π its a fully #distributed network, meaning everyone using it is a node (though slow ones are less used).
π it loves traffic including #torrenting and comes with a native #torrentClient,
π get #humanReadable web domains not governed by an authority, eg. yaylife.i2p,
π no "Guard" nodes,
π the more traffic you offer the more anonymous you get!, and
π no #NFT moneyLaundering goes to devteam!!!!π ππ
I2P stands for #InvisibleInternetProtocol.
Benefits of #I2P over Tor:
- its a fully #distributed network, meaning everyone using it is a node (though not all nodes are used equally, slow ones are less used).
- it loves traffic including #torrenting and comes with a native #torrentClient,
- get #humanReadable web domains not governed by an authority, eg. seelife.i2p,
- no #NFT moneyLaundering goes to devteam, and
- the more traffic you offer the more anonymous you are!
#TorProject: Over past months we've been breaking Tor Hidden Services (#HSv2), but we are now only just telling users in the browser that those accessible #onionAddresses are being dropped.
"Oh and here is #DuckDuckGo's website, still (by some miracle, obviously) using the #humanReadable address we know you prefer.
We would honestly compile a version of Tor that had 17 letters of entropy, if 16 doesn't take enough billions of years to crack.
Tor is now officially designed to kill grassroots movements.
We can no longer support it for anything more than maintaining some of the already popular movements.
We need to trust our intuition. As much as we liked #Tor we cannot let this blind us to the notion that it is now another captured and corporatised entity.
#TorProject dropping #humanReadable and memorable addresses by forcing the adoption of #v3Addresses is an aggressive move, to kill any possibility of #grassrootsAction.