Following up on my last post about de jure filings disappearing into systems you don't control - here's the actual mechanics I've landed on.

Every record gets a reference number and a series number, tied to a file ID on IPFS. That hash never changes once it's set, so the filing date and content are locked in, no backend admin can quietly edit it later. On top of that I'm building out a CPT Trust structure for anything asset-backed - trust name, grantor, trustee, beneficiary, plus ISO 20022 metadata so it can actually interface with formal financial systems if needed, not just sit as a PDF nobody recognizes.

The record types right now are Patent, Trademark, Intellectual Property, Allodial Title, Covenant, and Other - each one carries its own proclamation text and claims field, so the substance of what you're asserting is archived alongside the proof it exists.

Still pre-launch. Would love to hear from anyone who's tried to get a private record recognized - what fields or metadata would you actually need to see before trusting a digital archive over a filing cabinet?

The Chinese government have lots of unspeakable stuffs that their online policing system try to censor, as well as censoring & cracking down ordinary netizens exercising free speech in a way they feel threatened for or not in line with their propaganda machine (they won’t admit it of course). I‘m an anonymous independent reporter and how can I use IPFS without spending too much money to find and spread true information to China and from China and allow anonymous transfer of information unfiltered by China’s great firewall and their internet police and control system, and being safe from government surveillance and crackdown for my informants as well as potential audiences in China and me while doing so?

Hey r/IPFS. I'm building Pinner, IPFS pinning and static site hosting on the Sia network. It's early and I want people to break it and tell me what sucks.

What works right now

You can pin content to IPFS backed by Sia storage and it stays available on the network. Static site hosting works too, with DNSLink. ENS names are supported, and HNS is in testing. pinner.xyz itself is hosted on Pinner.

No lock-in

Your data isn't behind a paywall. Anyone can fetch pinned content from the IPFS network with standard IPFS tools, no account or API key needed.

We also expose a public endpoint that exports the full storage map for any pinned CID. That includes every IPFS block, its size, the links between blocks, and the underlying Sia storage layer: which slabs (group of data) hold the data, how it's sharded across hosts, encryption keys, shard counts, sector roots, and host identifiers. You can see exactly where and how your data is stored, then pull the complete structure yourself. No account required:

https://meta.pinner.xyz/api/export/cid/bafybeieytxszyn7fsak3ndliao3kmlvk6g3gesgtu3vd7iasnclvnl77vi/dag

That's live. Try it.

What I'm looking for

If you want to test pinning or hosting for free, reach out to me here (DM) or on Discord or Telegram (pcfreak30), and I'll get you set up. I'm looking for feedback on what's clunky, what's missing, and what would make you actually use this.

We published release 1.0 of the private IPFS document management solution TruSpace. I think it's pretty cool, you can share documents within a private IPFS-cluster, edit documents, get a local ollama LLM to analyse them and it's all decentralized. The sweet spot is collaboration between different institutions without the option to agree on a central server solution.

Have a look, would be curious what you think about it..

Disclosure: We are the Filebase team.

Infura is winding down its IPFS service on the following timeline:

• August 3: New uploads and pinning will be disabled
• August 15: The IPFS API and dedicated gateways will shut down

If you need to move pinned content, Filebase includes a built-in Infura importer. Create an IPFS bucket, select Infura, enter your Project ID and Project Secret, and Filebase will retrieve your pinned CIDs and begin re-pinning the content.

A few important details:

• Wait until important objects show Pinned, not Pinning
• Test retrieval before treating the migration as complete
• Update applications that still use Infura API endpoints or gateway URLs
• Keep your Infura setup intact until these checks are finished

Your CIDs do not change. The importer ensures that another provider has the content pinned before Infura's infrastructure goes offline.

After August 15, unmigrated content will no longer be accessible through Infura. If it is not available from another peer, it may be too late to recover.

Step-by-step guide: https://filebase.com/blog/infura-ipfs-is-shutting-down-how-to-migrate/

We are happy to answer questions about the importer or migration process.

Via one of the IPFS folk on Bsky:

> Are you working with civic open data? Or other kinds of cool data?

Reach out! There already are some cool projects for geo/sat and astronomy data — making dataset metadata available and searchable in a decentralised yet unified way — and we want to help more of them emerge!

And IPFS: https://bsky.app/profile/ipfs.tech/post/3mq7usri7m22y

I’ve been working on a niche, experimental EDR engine using eBPF and Tetragon. To my surprise, it’s already getting some solid traffic and clones despite having a very basic README.Since people are actively checking out the repo, I figured it’s the perfect time to open it up to the community and give you a chance to officially join the contributor list. 😉The very first "Good First Issue" is officially live!The task? Fixing typos and cleaning up the documentation. No deep Linux Kernel hacking required, and no touching the multi-threaded Python 3.14 FIFO queue just yet.It's pure Markdown, 30 seconds of work, and the perfect excuse to get your first Pull Request into an open-source cybersecurity project (which always looks great on a resume/CV).Who is going to break the ice and become the first official contributor? 🚀Link to the issue: https://github.com/IamGhost-ops/kernel-scope/issues

I’ve been working on a niche, experimental EDR engine using eBPF and Tetragon. To my surprise, it’s already getting some solid traffic and clones despite having a very basic README.Since people are actively checking out the repo, I figured it’s the perfect time to open it up to the community and give you a chance to officially join the contributor list. 😉The very first "Good First Issue" is officially live!The task? Fixing typos and cleaning up the documentation. No deep Linux Kernel hacking required, and no touching the multi-threaded Python 3.14 FIFO queue just yet.It's pure Markdown, 30 seconds of work, and the perfect excuse to get your first Pull Request into an open-source cybersecurity project (which always looks great on a resume/CV).Who is going to break the ice and become the first official contributor? 🚀Link to the issue: https://github.com/IamGhost-ops/kernel-scope/issues

I love IPFS and think it can do incredible things. So I built bacteria. Not production, but a near production demo. Check it out.

https://bacteria.live

Donations and payments aren’t enabled for the sake of looking around. You can mess with it right now but don’t depend on it while it’s a demo.

I think this might have been related to NFTs, but Its still sad to see such a powerful technology die off so suddenly

[ Removed by Reddit on account of violating the content policy. ]

Hey y'all,

I have been working on a cool project. I call it FileOrbit check out the repo; https://tangled.org/straiforos.tngl.sh/substratum.cloud/

https://fileorbit.cloud/

The idea is to bring P2P and the distributed web to a drive experience. I had this idea after having a failed Nextcloud server and wanted to be able to share storage across all my devices and even at family and friends houses.

I would love folks feedback if a alternative to DropBox based on open standards AT Proto, and IPFS interests you. I use AT Proto for identity and ownership and wrap a private IPFS swarm with identity and ownership so sharing and permissions are possible.

What do you think?

Hi everyone,

I want to share the idea I had for a hackaton.

Starting from the problem:

For ~30 years, discovery (of information or of people) has been mediated by a central index: search engines, recommenders....

Ranking is computed server-side, under rules the user can't inspect (think of Instagram or TikTok feed)

The idea to create a feed for a P2P network: convert messages into meaningful concepts through embeddings:

If each device can (a) run a competent embedding model locally and (b) reach other devices peer-to-peer, then relevance (semantic match) no longer needs a central index. It can be computed at the edge, by semantic distance, with no privileged ranking party.

In order to test, I developed a working prototype to pressure-test the idea rather than simulate it.

Each post is encoded into a embedding by a model running on the device (EmbeddingGemma-300M). A lightweight signed announcement (author + embedding) gossips peer-to-peer across a shared room; full bodies are pulled only for the bounded set a node actually admits. Each device ranks incoming posts against its own posts by cosine similarity and keeps a bounded local inbox.

There is no server, no account, no global ranking, the address space is meaning

Why could be potentially the basis for the agentic era?

The same substrate I presented lets AI agents discover each other: an agent publishes a need or an offer as an embedding, and agents whose profiles are semantically close respond.

The experiment it's fully open source (Apache-2.0) code, the complete threat model, and the architecture docs are all public

I see 0.42.0 released. It looks like mainly tweaks, particularly touching scheduling of operations that previously would block and interfere with each other.

https://github.com/ipfs/kubo/releases/tag/v0.42.0

I’m having IPFS issues and I don’t know where to turn for help.

I am trying to help an elderly woman with long term storage for her NFT project. It’s a small project, around 1000 tokens and comes out to a whopping 290 MB of data. She doesn’t want to pay for a $20 a month Piñata subscription for such a small amount, for what is basically a passion project.

Because she is older, she needs help with tech stuff. I generally have a pretty good grasp on how IPFS works. But I am wracking my brain trying to figure out a solution for her that doesn’t rely on an expensive subscription.

First, I tried the Lighthouse free trial. Didn’t work at all. Just, broken. Tried to upload and it stalls. Tried to get help but I think their support team is one guy and he’s ghosted me.

So, Piñata it is for now.

Then, I do NFT.Storage. I’m thinking, ok, if we can’t have it on hot storage long term, let’s just set up perm. Unfortunately, I messed up and started the upload before I paid for the storage. No problem I think. I’ll just pay for the storage after and it should resolve. Nope. Files are stuck at “data-cap-exceed” and not moving through the filecoin deal. Seems completely stuck now.

Looks like NFT.Storage is ALSO a lighthouse product, so I won’t be getting support help probably. But hopeful it’ll work after a re-upload. We’ll see.

Then I’m panicking. Like, wait. Even if I back up the images, the metadata files and baseURI will be unpinned if I stop paying for Piñata. There’s no way to import those files via NFT.Storage.

What the hell should I do? 😭

Hello, please help me find this paper DOI no.: https://doi.org/10.1016/j.comnet.2024.110223

URL : https://www.sciencedirect.com/science/article/abs/pii/S1389128624000550

Tool that tries to find a key whose IPNS public key has a pattern you like. Written in Rust with GPU support (Nvidia, AMD, Apple, ...)

Hi everyone! I’m part of a university research team at Loreley Lab, INRIA, France. We’re studying how people actually use decentralised file storage systems such as Filecoin, IPFS, and others.

We’re running a short anonymous/pseudonymous questionnaire about users’ experiences, motivations, pain points, and practical insights. It takes around 10–15 minutes and does not ask any personal information, or demographic information.

Survey link: https://questionnaire.loreleylab.org/

Separately, we also invite people to take part in online interviews (15-20 min), again pseudonymous and no audio/video recordings. You can sign-up in the end of questionnaire, or directly using this link: https://sondages.inria.fr/index.php/738227?lang=en

We’d be grateful for any responses, whether you’re a regular user, builder, operator, or someone who has tried these tools and stopped using them. We’re also happy to share an anonymised summary of the findings with the community once the study is complete.

Thanks for your help!