[ ARCHIVED ] Wikipedia snapshots on IPFS (2017-2021). The ZIM-unpacking approach is a dead end, read the README for what to build instead. - ipfs/distributed-wikipedia-mirror
IPFS — Content addressing for data with confidence
IPFS gives developers content addressing building blocks for verifiable, portable, and resilient applications across open networks
Decentralized Technology in Practice: An analysis of socio-technical resilience in IPFS
The “Interplanetary File System” (IPFS) refers to a peer-to-peer content addressing protocol that is designed to be “upgradeable, resilient, and more open”. [1]
GitHub - ipld/go-car: A content addressible archive utility
A content addressible archive utility. Contribute to ipld/go-car development by creating an account on GitHub.
IPFS at Eurosky Live Berlin: Highlights From A Bright Future
The Authenticated Transfer Protocol (ATProto or AT), which sits under Bluesky and many other emerging projects, has tremendous potential. At the IPFS Foundation, we're big fans, and not just because AT builds on the IPFS stack through IPLD and DASL (though admittedly building on DASL is one of the coolest
Optimistic Provide: How We Made IPFS Content Publishing 10x Faster
How a statistical approach cut IPFS content publishing times by over one order of magnitude.
Peersky Browser (@peersky@mastodon.social)
Attached: 2 images 📁 In v1.0.0-beta.14 you can now: - Browse your local file:// directories inside PeerSky and publish them straight to IPFS or Hypercore with one click. The distributed web should feel this easy. 🌍✨ https://github.com/p2plabsxyz/peersky-browser/releases/tag/v1.0.0-beta.14
IPFS is moving beyond the sponsored gateways
How IPFS is shifting from centralized public gateways to distributed infrastructure and client-side retrieval.
Introducing Filebase Sites: Simplified IPFS Websites with IPNS
Hosting a real website on IPFS has always come with friction: changing CIDs, manual IPNS management, and fragile workflows. Filebase Sites removes the last-mile complexity, giving developers a simple way to publish, update, and maintain decentralized websites without breaking links.
How we built Git storage for millions of Netlify projects
A technical look at how Netlify built Netlify Source: durable Git storage on S3, scalable caching, push consistency, and support for millions of projects.
i couldn't get this out of my head so i wrote a whole-ass post about it jyn.dev/distributed-identity/
distributed identity
jyn.dev
Justice Of Toren One Var
i’ve been thinking about how let people update/revoke identities in VCS you could keep only an opaque id in the merkle tree, and have a separate central service that maps it to an identity. if you want to keep the “distributed“ part, you could let people “attest” the mapping on bsky/keybase /GPG
Scratching my own itch, I’ve built atfs.dev — an atproto native (self-hosted, for now) IPFS server! xRPC admin & upload, an HTTP gateway (for stored files only) and the ability to follow/mirror another instance. It even has RasPi-ready .img files! atfs.dev/manage/storage.atfs.dev
atfs
atfs.devMirror another platform, now in early access for Pros 📡 Connect a Substack, Ghost or any RSS feed 📝 Land new posts published or as drafts ✨ Originals stay canonical, only new posts sync Settings → Mirror content. Experimental, tell us if it breaks! 👀 Check it out → offprint.link/mirror
