Content-Addressed Wikis: Permanence Without a Single Host: Difference between revisions
Created page with "Content-addressed wikis store page bytes so that a cryptographic identifier, not a single website hostname, is the durable name of a version. A classic MediaWiki installation keeps articles in a database on one host. If that host goes offline, changes policy, or loses its disks, readers lose the pages even when many people valued them. Content addressing changes the failure mode. An IPFS content identifier (CID) or an Arweave transaction identifier names exact bytes. Any..." |
Use short piped text for internal links |
||
| Line 23: | Line 23: | ||
== Arweave transaction identifiers and permaweb pages == | == Arweave transaction identifiers and permaweb pages == | ||
Arweave is aimed at long-lived public data with payment up front. A wiki snapshot uploaded there receives a transaction identifier. After the write meets the confirmation bar the application requires, the identifier is a stable citation. New edits are new transactions. For most readers, the permaweb still looks like HTTPS through a gateway that maps identifiers and path manifests to bytes. See [[Permaweb_Basics:_How_Arweave_Makes_Content_Permanent]] for the storage model, and [[IPFS_and_Arweave_for_Agent_Memory_and_Knowledge_Bases]] for how the two networks differ when agents and knowledge bases are the workload. | Arweave is aimed at long-lived public data with payment up front. A wiki snapshot uploaded there receives a transaction identifier. After the write meets the confirmation bar the application requires, the identifier is a stable citation. New edits are new transactions. For most readers, the permaweb still looks like HTTPS through a gateway that maps identifiers and path manifests to bytes. See [[Permaweb_Basics:_How_Arweave_Makes_Content_Permanent|Permaweb basics]] for the storage model, and [[IPFS_and_Arweave_for_Agent_Memory_and_Knowledge_Bases|[object Object]]] for how the two networks differ when agents and knowledge bases are the workload. | ||
Arweave fits releases that should stay citable for years, such as approved article versions and static HTML exports. It is a weak fit for every keystroke. Practical teams keep hot revisions in a mutable database and push signed releases on a schedule. Bundlers can group small objects. The team should know who holds signing keys, who pays the fee, and how a failed bundle is retried. | Arweave fits releases that should stay citable for years, such as approved article versions and static HTML exports. It is a weak fit for every keystroke. Practical teams keep hot revisions in a mutable database and push signed releases on a schedule. Bundlers can group small objects. The team should know who holds signing keys, who pays the fee, and how a failed bundle is retried. | ||
| Line 47: | Line 47: | ||
* Recompute CIDs on fetch. Check Arweave transaction data when the client allows it. Log mismatches. | * Recompute CIDs on fetch. Check Arweave transaction data when the client allows it. Log mismatches. | ||
* Maintain a catalog. Permanent bytes are not a search ranking. | * Maintain a catalog. Permanent bytes are not a search ranking. | ||
* Keep non-public personal data off the public network. Encrypt private notes and store keys outside the snapshot. See [[Building_a_Second_Brain_on_the_Permaweb_Without_Losing_Ownership]]. | * Keep non-public personal data off the public network. Encrypt private notes and store keys outside the snapshot. See [[Building_a_Second_Brain_on_the_Permaweb_Without_Losing_Ownership|Second brain on the Permaweb]]. | ||
* Write the steps to rebuild the mutable wiki from the latest snapshot. | * Write the steps to rebuild the mutable wiki from the latest snapshot. | ||
* Keep working notes in a mutable index and cited releases under content identifiers. See [[X402:_HTTP_402_Payments_for_AI_Agents]] and [[Open_Source_Freedom_Tech_Worth_Watching_in_Agent_Infrastructure]]. | * Keep working notes in a mutable index and cited releases under content identifiers. See [[X402:_HTTP_402_Payments_for_AI_Agents|x402 payments]] and [[Open_Source_Freedom_Tech_Worth_Watching_in_Agent_Infrastructure|Freedom tech for agents]]. | ||
== What still fails == | == What still fails == | ||
| Line 61: | Line 61: | ||
== See also == | == See also == | ||
* [[IPFS_and_Arweave_for_Agent_Memory_and_Knowledge_Bases]] | * [[IPFS_and_Arweave_for_Agent_Memory_and_Knowledge_Bases|[object Object]]] | ||
* [[Permaweb_Basics:_How_Arweave_Makes_Content_Permanent]] | * [[Permaweb_Basics:_How_Arweave_Makes_Content_Permanent|Permaweb basics]] | ||
* [[Building_a_Second_Brain_on_the_Permaweb_Without_Losing_Ownership]] | * [[Building_a_Second_Brain_on_the_Permaweb_Without_Losing_Ownership|Second brain on the Permaweb]] | ||
* [[Open_Source_Freedom_Tech_Worth_Watching_in_Agent_Infrastructure]] | * [[Open_Source_Freedom_Tech_Worth_Watching_in_Agent_Infrastructure|Freedom tech for agents]] | ||
* [[X402:_HTTP_402_Payments_for_AI_Agents]] | * [[X402:_HTTP_402_Payments_for_AI_Agents|x402 payments]] | ||
* [[Post-Scarcity_Tooling:_When_Compute_and_Storage_Stop_Being_Scarce]] | * [[Post-Scarcity_Tooling:_When_Compute_and_Storage_Stop_Being_Scarce|Post-scarcity tooling]] | ||
[[Category:Content addressing]] | [[Category:Content addressing]] | ||