feat: 🔗 add links to articles on common digital infrastructure and ma…

…gnesium

- Added [Common Digital Infrastructure](https://andrewconner.com/common-digital-infrastructure/) link to multiple documents, highlighting its relevance to decentralization, future tech, and governance.
- Introduced a recommended magnesium supplement dosage and forms in the Nutrition guide for improved clarity.
- Emphasized temporal value in the Open Data guide and improved dataset linkage recommendations for better integration and discoverability.

Decentralized Protocols.md

@@ -26,3 +26,5 @@
 - If a system requires a centralized part, a great alternative is give the user the ability to point to other centralized things taking care of that part.
 - If you have a protocol, try enforcing the desired behavior using the protocol. Your ideas of how to solve it might not be the best and adding a protocol restriction (incentives/penalties) will make people figure out.
 - When building a technology, consider: [does this centralize or decentralize power?](https://geohot.github.io/blog/jekyll/update/2021/01/18/technology-without-industry.html)
+- Many decentralized protocols are trying to build next generation common digital infrastructure.
+  - Unfortunately,[nearly every crypto project realized that they could capture value (make a lot of money) with innovative tokenomics that looked a lot like Ponzis, or at least borderline securities fraud](https://andrewconner.com/common-digital-infrastructure/).

Future.md

@@ -32,6 +32,8 @@ History teaches us that in 100 years from now [[Openness|some of the assumptions
 
 ### Exciting Software Engineering Ideas
 
+- [Common Digital Infrastructure](https://andrewconner.com/common-digital-infrastructure/)
+  - If you work in tech, this is a fun thought experiment. Imagine you don’t need any money and can devote your time to benefiting everyone by building common digital infrastructure. What would exist in a better future?
 - Content Addressed Data + Immutability
 - CRDTs
 - Homomorphic Encryption

Governance.md

@@ -13,3 +13,4 @@ Governance is a tool an [[Organizations|organization]] uses to decide where powe
 - [CommunityRule](https://communityrule.info/). A governance toolkit for great communities.
 - [Verses](https://verses.xyz/).
 - [[Decentralized Autonomous Organizations]]
+- [Common Digital Infrastructure](https://andrewconner.com/common-digital-infrastructure/)

Nutrition.md

@@ -18,6 +18,7 @@
 - [Caffeine](https://examine.com/supplements/caffeine/).
 - [L-Theanine](https://lorienpsych.com/2021/01/31/l-theanine/).
 - [Vitamin B12](https://examine.com/supplements/vitamin-b12/). Around 1 mg per day.
+- [Magnesium](https://examine.com/supplements/magnesium/). Around 410–420 mg/day for men and 320–360 mg/day for women. Magnesium citrate is a good form. Magnesium chloride, magnesium gluconate, and magnesium glycinate also appear to have good bioavailability.
 
 ## Resources
 

Open Data.md

@@ -38,7 +38,7 @@ During the last few years, a large number of new data and open source tools have
 
 These trends are already making its way towards movements like [DeSci](https://ethereum.org/en/desci/) or smaller projects like [Py-Code Datasets](https://py-code.org/datasets). But, we still need more tooling around data to improve interoperability as much as possible. Lots of companies have figured out how to make the most of their datasets. **We should use similar tooling and approaches companies are using to manage the open datasets that surrounds us**. A sort of [Data Operating system](https://data-operating-system.com/).
 
-One of the biggest problem in open data today is the fact that organizations treat data portals as graveyards where data goes to die. Keeping these datasets up to date is core concern, alongside using the data for operational purposes and showcasing it to the public.
+One of the biggest problem in open data today is the fact that organizations treat data portals as graveyards where data goes to die. Keeping these datasets up to date is core concern (data has marginal temporal value), alongside using the data for operational purposes and showcasing it to the public.
 
 Open data is hard to work with because of the overwhelming variety of formats and the engineering cost of integrating them. Data wrangling is a perpetual maintenance commitment, taking a lot of ongoing attention and resources. [Better and modern data tooling can reduce these costs](https://github.com/catalyst-cooperative/pudl).
 
@@ -94,11 +94,12 @@ Package managers have been hailed among the most important innovations Linux bro
   - [Bootstrap a package registry](https://antonz.org/writing-package-manager/). E.g: a GitHub repository with lots of known `datapackages` that acts as fallback and quick way to get started with the tool (`data list` returns a bunch of known open datasets and integrates with platforms like Huggingface).
 - **Indexing**. Should be easy to list datasets matching a certain pattern or reading from a certain source.
   - Datasets are linked to their metadata.
-  - One Git repository should match one portal/catalog/hub. Could also be a dataset. The main thing is for code and data to live together. Each Data Portal should be comparable to a website, and may have a specific topical focus (unify on a central theme).
+  - One Git repository should match one portal/catalog/hub where related datasets are linked (not islands). Could also be a dataset. The main thing is for code and data to live together. Each Data Portal should be comparable to a website, and may have a specific topical focus (unify on a central theme).
   - To avoid yet another open dataset portal, build adapters to integrate with other indexes.
     - For example, integrate all [Hugging Face datasets](https://huggingface.co/docs/datasets/index) by making an scheduled job that builds a Frictionless Catalog (bunch of `datapackage.yml`s pointing to their parquet files).
     - [Expose a JSON-LD so Google Dataset Search can index it](https://developers.google.com/search/docs/appearance/structured-data/dataset).
   - [FAIR](https://www.go-fair.org/fair-principles/).
+  - Finding the right dataset to answer a question is difficult. Good metadata search is essential.
 - **Formatting**. Datasets are saved and exposed in multiple formats (CSV, Parquet, ...). Could be done in the backend, or in the client when pulling data (WASM). The package manager should be **format and storage agnostic**. Give me the dataset with id `xyz` as a CSV in this folder.
 - **Social**. Allow users, organizations, stars, citations, attaching default visualizations (d3, [Vega](https://vega.github.io/), [Vegafusion](https://github.com/vegafusion/vegafusion/), and others), ...
   - Importing datasets. Making possible to `data fork user/data`, improve something and publish the resulting dataset back (via something like a PR).