The approach follows saturation mechanics—controlled accumulation of relations (links, repetitions, protocols) until the smallest unit feels like a miniature map of the whole epistemic landscape rather than an isolated fragment. IPFS, by contrast, is a distributed protocol for storing and sharing files in a peer-to-peer network. Instead of location-based addressing (traditional HTTP URLs that point to a specific server), IPFS uses content addressing. Each file or piece of data receives a unique Content Identifier (CID)—a cryptographic hash (fingerprint) derived from the content itself. If the content changes even slightly, the CID changes completely. Data is broken into chunks, distributed across participating nodes, and retrieved from any nodes that hold copies, often via a Distributed Hash Table (DHT) for discovery. Metadata in IPFS can take forms like JSON files, DAG-CBOR (for linked, graph-like structures), or simple embedded descriptions; in NFT contexts, it commonly includes name, description, image links, and attributes, referenced by CID. For richer or evolving metadata, projects often combine IPFS with IPNS (for mutable pointers) or external indexes. Similarities in Pursuing Persistence and Sovereignty
Both systems respond to the fragility of centralized web hosting—where content can vanish due to server failures, takedowns, platform policy changes, or link rot. They seek to reduce single points of failure and enable long-term retention. Resistance to erasure or capture: The Socioplastics tail makes each post self-contextualizing and less dependent on any one blog platform by embedding persistent identifiers (ORCIDs, DOIs, channel mappings) and recursive references. IPFS achieves similar resistance through content addressing: as long as at least one node holds the data and it is discoverable, the content remains accessible regardless of where the original uploader’s server is. Distribution for durability: Socioplastics distributes intelligence across 11 specialized channels (theoretical core, curatorial, audiovisual, political, environmental, etc.), allowing concepts to migrate and harden transversally. IPFS distributes actual file chunks across many nodes, so retrieval can pull from multiple sources simultaneously, improving resilience and potentially speed for popular content. Verifiability: In Socioplastics, the tail’s structured repetition and cross-links create lexical gravity—readers or machines can verify coherence by following the architecture. In IPFS, the CID itself provides strong integrity checking: you can mathematically confirm that retrieved data matches the expected hash, detecting any tampering. Both treat the support layer (tail or CID/metadata) as active infrastructure rather than passive afterthought, aligning with goals of epistemic or data sovereignty—keeping control closer to the creator and community rather than centralized gatekeepers.
Key Differences in Mechanics and Trade-offs The approaches diverge in how they produce retention, handle evolution, and balance accessibility with cost.
Site specificity without site fidelity — anchor, displace. Situational fixer — bag, blanket, stabilize. Wearable aperture — frame as construction. Sectional calibration — cut, read, govern. YouTube Breakfast — view, curate. Numerical topology — number as relation. Decalogue protocol — ten propositions. Multichannel system — eleven interfaces. Translatorial object — carry, translate. Epistemic sovereignty — produce, circulate, embed.
Thickening vs. Immutability and Addressing: Socioplastics relies on relational saturation—adding weight through prose, lists, keywords, and explanations that make the tail didactic and navigable for humans. The content lives on familiar blog URLs (location-addressed), but the tail compensates by embedding a dense map of the system. This is flexible: the tail can be updated or expanded in new posts without breaking old ones. IPFS enforces immutability via content addressing: the CID guarantees the exact content never changes without a new identifier. This is powerful for verification (e.g., academic datasets or artworks) but less flexible for evolving knowledge—rich, narrative metadata like the Socioplastics tail would typically be stored as a separate JSON or text file on IPFS, with its own CID. For mutable references (e.g., pointing to the “latest” version of a collection), IPNS or DNSLink is needed, introducing another layer. Persistence Model: In Socioplastics, persistence comes from authorial and architectural repetition within the blog ecosystem. The tail ensures that even if one channel weakens, the conceptual gravity and cross-references keep the corpus oriented and findable via search engines or direct links. No extra ongoing cost beyond hosting the blogs. IPFS persistence is node-dependent: simply uploading does not guarantee availability. Data can be garbage-collected if no one “pins” it (actively keeps a copy on their node). Long-term archiving often requires pinning services, paid storage (e.g., via Filecoin, which adds economic incentives for providers), or community effort. Without active maintenance, unpopular content risks disappearing—unlike the self-reinforcing textual density of the Socioplastics tail, which persists as long as the blog itself is online. Accessibility and Readability: The Socioplastics tail is immediately legible to any reader or basic web crawler—no special software required. It explains channels, lists SLUGS, and provides citation guidance in plain language, supporting transversal navigation across disciplines. IPFS retrieval often involves gateways (http-to-ipfs bridges) for easy web access, but native use benefits from a local node or dedicated tools. Metadata on IPFS (especially complex graphs) can be more technical and machine-oriented; human-friendly explanations still tend to live in accompanying documentation or traditional web pages. Retrieval can also face higher latency for unpopular or sparsely pinned content compared to well-cached centralized servers.
Scalability and Cost: Adding depth to a Socioplastics tail has negligible marginal cost—it is just more structured text. The system scales through prolific, modular writing and self-reference. IPFS is efficient for distribution and deduplication (identical content shares the same CID), but large-scale or high-availability use incurs pinning/storage costs and network overhead. Performance can vary: popular files spread widely and load faster; niche academic or theoretical archives may load slower unless actively supported.
Sovereignty Style: Socioplastics sovereignty is coherent and authorial—centered on a unifying voice (Lloveras) that maintains long-range consistency across distributed channels while refusing platform capture through density. IPFS sovereignty is cryptographic and peer-based—no central authority controls the network, and content integrity is mathematically enforced, but availability depends on collective node behavior and incentives. It excels at censorship resistance for static files but offers less built-in support for nuanced, evolving epistemic frameworks that require explanation and cross-linking. Broader Implications for Knowledge Infrastructures - For projects like Socioplastics—focused on conceptual density, saturation mechanics, transversal synthesis across art, urbanism, and epistemology—the metadata tail provides a low-barrier, immediately operational path. It turns blog posts into inhabitable nodes within a self-describing landscape, emphasizing retention through accumulation rather than pure distribution. This fits long-form, recursive theoretical work where human legibility and didactic navigation matter as much as raw persistence. IPFS shines for verifiable, immutable archives—datasets, media files, or finished publications—where content integrity and distribution without central servers are priorities. It pairs naturally with blockchain (e.g., CIDs referenced in smart contracts for NFTs or credentials) but often needs complementary layers (pinning services, Filecoin incentives, or traditional web front-ends) for reliable long-term access and rich context. In practice, the two are complementary rather than rivals. A hybrid approach could involve exporting key Socioplastics outputs (monographs, datasets, or even full SLUGS packs) to IPFS for content-addressed backups and verifiable CIDs, while keeping the rich, evolving metadata tails and navigational architecture on the blog constellation for human-oriented density and discoverability. The tail could even include IPFS CIDs for core documents, adding cryptographic anchoring without sacrificing flexibility. Ultimately, both address the same pressure in unstable times: how to make knowledge and creative work stick beyond fleeting platforms. The Socioplastics metadata tail builds durable districts of thought through patient textual thickening and architectural coherence. IPFS offers a decentralized substrate where content is addressed by what it is, not where it sits—powerful for integrity but requiring active care for true persistence. For epistemic projects prioritizing conceptual gravity, navigability, and self-reinforcing momentum, the thoughtfully saturated tail remains a pragmatic, human-first infrastructure; IPFS provides a strong complementary tool for the underlying files that need mathematical permanence. Together, they illustrate different viable mechanics for turning fragile digital flows into more sovereign, load-bearing structures.
PROJECT CITATION & RESEARCH METADATA Institutional Affiliation: LAPIEZA-LAB, Madrid, Spain Research Framework: Socioplastics — Transdisciplinary Urban Theory Author: Anto Lloveras ORCID:
The metadata tail in Anto Lloveras’s Socioplastics project and IPFS (InterPlanetary File System) storage both aim to create more durable, sovereign forms of persistence in an unstable digital environment, yet they operate through fundamentally different mechanics: one through textual and relational thickening on conventional web infrastructure, the other through content-addressed decentralization across a peer-to-peer network. In Socioplastics, the metadata tail is a human-readable, structured extension appended to each SLUG (blog post). It includes affiliation details, ORCID, suggested citations, research fields, keywords tied to saturation mechanics and epistemic infrastructure, lists of Zenodo monographs with DOIs, collected volume packs, journal preprints, datasets, software links, a full description of the 11-channel distributed constellation (with functional explanations for each), and the recent SLUGS sequence with direct URLs. This tail turns a single post into a load-bearing node: it carries traces of the entire multichannel system, enabling immediate navigation, self-archiving, and cross-referential density.
