I would say the Web isn't dead yet.
Even if #browsers undergo #enshittification , make blocking #ads harder we can still build and consume great web services like the #fediverse , #wikipedia etc.
I feel the responsibility to build ethically and to consume mindfully has increased.
We can create soft forks like #librewolf or #cromite to remove the annoying parts. Really glad that chromium and firefox are still open source.
LPS likes this.
reshared this
LPS
in reply to Bhavani Shankar • •FourOh-LLC
in reply to LPS • • •Wikipedia is a very bad example of things we should be calling Great.
Wikipedia is controlled by ideological puritans, and its an academic exercise on how to conflate data, knowledge and information.
Wikipedia is the diametrical opposite of a read-only immutable storage such as the IPFS. A read-only public archive is accurate and authentic, while a wiki lacks any and all credibility. You cannot rationally expect reading the same on the wiki page.
What's worse is, this is debated all the time. Just what a waste that is, debating the obvious.
WORM archives are needed badly, more than ever. Authenticating raw, tabulated data is urgently needed to correct the increasing effort to subvert data as information. "You cannot step into the same river twice" is Wikipedia, trusting it is a fatal error.
Anything that is trustworthy about Wikipedia should be moved to immutable archives. Facts do not need editing. Mixing indisputable facts with controversial topics and perspectives is used to lend credibility. Wikipedia does not deserve that credibility, because the purpose of the Wiki is subverted.
FourOh-LLC
in reply to FourOh-LLC • • •FourOh-LLC
in reply to FourOh-LLC • • •Bhavani Shankar
in reply to FourOh-LLC • • •FourOh-LLC
in reply to Bhavani Shankar • • •Yes, I agree with that, but I also explained why reliable and factual information should NOT be stored on a wiki.
Its not that Wikipedia is not perfect, its that Wikipedia is used for the WRONG purpose. The original design and concept was sound for its time, as we had no IPFS, cjdns, not even the Internet Archives.
Today we have better tools and better solutions.
FourOh-LLC
in reply to FourOh-LLC • • •This fedi node, pkteerium is operated by the creator of cjdns, and a lead developer (or the lead developer) of PKT. I think I understand his design and vision, and I think I have at least one use-case for his software.
If that makes me a technological evangelist I an actually honored, because cjdns and PKT are on the cutting edge of the relevant technological sector(s).
FourOh-LLC
in reply to FourOh-LLC • • •Let’s imagine the combination of the immutable and the mutable, where IPFS serves as the immutable storage layer and a Wiki or other Semantic Web technology acts as a dynamic, human-readable organizational layer.
By core design, IPFS is a highly efficient but terse storage mechanism—it does not provide human-readable references beyond content-based cryptographic addresses (hashes). This makes IPFS powerful for verifiable, tamper-proof storage, but it lacks built-in ways to search, structure, annotate, or correct its content. A Wiki-like layer or other structured knowledge system could complement IPFS by organizing immutable content without modifying it, providing metadata, discussions, errata, and searchability while preserving the underlying integrity of the stored data.
I am not a coder, so I will not attempt to explain this in terms of software and protocols. However, as an end-user, I can clearly articulate the need for a system that enables structured, accessible, and user-friendly interaction with immutable data. There may already be projects working
... show moreLetâs imagine the combination of the immutable and the mutable, where IPFS serves as the immutable storage layer and a Wiki or other Semantic Web technology acts as a dynamic, human-readable organizational layer.
By core design, IPFS is a highly efficient but terse storage mechanismâit does not provide human-readable references beyond content-based cryptographic addresses (hashes). This makes IPFS powerful for verifiable, tamper-proof storage, but it lacks built-in ways to search, structure, annotate, or correct its content. A Wiki-like layer or other structured knowledge system could complement IPFS by organizing immutable content without modifying it, providing metadata, discussions, errata, and searchability while preserving the underlying integrity of the stored data.
I am not a coder, so I will not attempt to explain this in terms of software and protocols. However, as an end-user, I can clearly articulate the need for a system that enables structured, accessible, and user-friendly interaction with immutable data. There may already be projects working toward this, but I have not yet encountered one that fully meets this vision. The challenge is not simply technicalâit is about aligning immutable trust with flexible usability in a way that serves real-world needs.
FourOh-LLC
in reply to FourOh-LLC • • •Take, for example, the Wikipedia page for George Floyd.
As of today, the page contains 144 references—a staggering amount of effort and documentation for a single individual. The sheer volume of citations and the relentless attempts to justify and shape the narrative demonstrate the nature of Wikipedia as a never-ending editorial battleground rather than a stable reference.
I have followed this page for a while, and the continuous edits, justifications, and revisions show that the effort to maintain and control the narrative is bottomless. The page will never stop changing, because Wikipedia, by design, is not meant to provide immutable historical records—it is a forum for ongoing interpretation, re-evaluation, and editorial consensus, which shifts over time.
This is not about dismissing events, disregarding the impact on those affected, or making a political statement. Rather, it highlights the immense resources and effort spent in the pursuit of an unattainable goal—trying to create a stable record on a platform that is inherently unstable. Th
... show moreTake, for example, the Wikipedia page for George Floyd.
As of today, the page contains 144 referencesâa staggering amount of effort and documentation for a single individual. The sheer volume of citations and the relentless attempts to justify and shape the narrative demonstrate the nature of Wikipedia as a never-ending editorial battleground rather than a stable reference.
I have followed this page for a while, and the continuous edits, justifications, and revisions show that the effort to maintain and control the narrative is bottomless. The page will never stop changing, because Wikipedia, by design, is not meant to provide immutable historical recordsâit is a forum for ongoing interpretation, re-evaluation, and editorial consensus, which shifts over time.
This is not about dismissing events, disregarding the impact on those affected, or making a political statement. Rather, it highlights the immense resources and effort spent in the pursuit of an unattainable goalâtrying to create a stable record on a platform that is inherently unstable. This is exactly why certain facts, once verified, must be moved to immutable storage, where they cannot be rewritten, reframed, or selectively edited to fit shifting narratives.
FourOh-LLC
in reply to FourOh-LLC • • •Here lies the truly tragic and uncomfortable question—does George Floyd even warrant an immutable record? In life, he did not accomplish anything of historical, scientific, or cultural significance that would traditionally justify national or international recognition. This is an objective fact.
However, the circumstances of his death and the global events that followed undeniably warrant extensive documentation. Not just one, but multiple immutable records should exist—not for the sake of glorification, but for unbiased preservation of historical reality. Yet, if such immutable records were created, many of them would not be flattering—they would be revealing.
This highlights the precise crisis we face today—not just in politics, but in academia, journalism, and every major institution where narratives are constantly reshaped, controlled, and framed to serve agendas. Take climate change data, for example—are there truly immutable records documenting the sun’s cycles, cosmic radiation, geomagnetic fields, deep oceanic currents, and a
... show moreHere lies the truly tragic and uncomfortable questionâdoes George Floyd even warrant an immutable record? In life, he did not accomplish anything of historical, scientific, or cultural significance that would traditionally justify national or international recognition. This is an objective fact.
However, the circumstances of his death and the global events that followed undeniably warrant extensive documentation. Not just one, but multiple immutable records should existânot for the sake of glorification, but for unbiased preservation of historical reality. Yet, if such immutable records were created, many of them would not be flatteringâthey would be revealing.
This highlights the precise crisis we face todayânot just in politics, but in academia, journalism, and every major institution where narratives are constantly reshaped, controlled, and framed to serve agendas. Take climate change data, for exampleâare there truly immutable records documenting the sunâs cycles, cosmic radiation, geomagnetic fields, deep oceanic currents, and all the complex variables that form the foundations of climate science? Or are we only left with curated datasets that reinforce a particular statistical model?
At its core, the issue is deeper than bias or misinformationâit is about whether we, as a society, are even capable of having objective discussions anymore, without first shaping them to fit a predetermined political agenda. If facts can no longer exist outside of narrative control, then truth itself becomes an illusion.
FourOh-LLC
in reply to LPS • • •The great things are cjdns and PKT, a brilliant convergence of cryptographic addressing, decentralized routing, and the unrealized potential of scalable networkingâsuch as the IPv6 address pool, which is far too vast for conventional routing methods. cjdns solved fundamental problems: removing the need for traditional name services (NS), eliminating the bottlenecks of centralized routing, and outperforming software-based anonymity networks like I2P in speed and efficiency. PKT takes this further, realizing the dream of individuals becoming their own ISPs and Data Centersâfully independent, untraceable, and unstoppable. This is federation at its highest form: self-sovereign, trustless, and beyond centralized control.
What we need next is the immutable archives.
FourOh-LLC
in reply to FourOh-LLC • • •The Internet Archive and the Wayback Machine cannot serve as true immutable archives like IPFS because they lack permanence, cryptographic verification, and decentralization. Just as Wikipedia should not be “fixed” to become a factual authority, the Internet Archive should not be patched into an incomplete solution for true immutability. It was not designed for cryptographic integrity, censorship resistance, or decentralized storage, and forcing it into that role would only create a fragile workaround, not a real solution.
The true path forward is leveraging technologies purpose-built for immutability—and IPFS is designed for exactly this purpose. Its content-addressable, peer-to-peer storage model ensures that data remains verifiable, untampered, and accessible regardless of centralized control. However, IPFS must scale, and this is where cjdns and PKT provide the missing link: a self-sovereign networking layer and an infrastructure that enables individuals to become independent ISPs and data providers. By integrating cjdns and PKT into the IPFS ecosystem,
... show moreThe Internet Archive and the Wayback Machine cannot serve as true immutable archives like IPFS because they lack permanence, cryptographic verification, and decentralization. Just as Wikipedia should not be âfixedâ to become a factual authority, the Internet Archive should not be patched into an incomplete solution for true immutability. It was not designed for cryptographic integrity, censorship resistance, or decentralized storage, and forcing it into that role would only create a fragile workaround, not a real solution.
The true path forward is leveraging technologies purpose-built for immutabilityâand IPFS is designed for exactly this purpose. Its content-addressable, peer-to-peer storage model ensures that data remains verifiable, untampered, and accessible regardless of centralized control. However, IPFS must scale, and this is where cjdns and PKT provide the missing link: a self-sovereign networking layer and an infrastructure that enables individuals to become independent ISPs and data providers. By integrating cjdns and PKT into the IPFS ecosystem, we move toward a decentralized, unstoppable, and censorship-resistant data network, solving the fundamental challenges of scalability, distribution, and resilience in a way that no centralized archive ever could.