Hacker News: momack2

New comment by momack2 in "IPFS Maintainers Winding Down"

momack2 — Mon, 24 Aug 2026 20:04:28 +0000

Love DASL (funded by IPFS too)! Iroh also meets the DASL spec (https://dasl.ing/bdasl.html). A great bridging opportunity for agents to build interop between many different content addressed systems!

New comment by momack2 in "IPFS Maintainers Winding Down"

momack2 — Mon, 24 Aug 2026 20:02:51 +0000

Iroh is great! As is ATProto! Both build on DASL (https://dasl.ing/bdasl.html) - which specifies the core content addressing layer of IPFS.

However - important clarification about the Shipyard post that I think a lot of folks are confused by:

While its sad to see the Shipyard team sunset, the IPFS project is decentralized & robust to a single party moving on. IPFS the project/network is not sunsetting or shutting down!

Current focus is lighter-weight stewardship from the IPFS Foundation via grants to individual maintainers, & development of decentralized public infra tools like the Service Worker Gateway.

New comment by momack2 in "IPFS Maintainers Winding Down"

momack2 — Mon, 24 Aug 2026 19:54:54 +0000

A few interesting places to get involved:

- ATProto ecosystem (built on IPFS content addressing, used by Bluesky): https://atproto.com/guides/tutorials

- IPFS contribution guide: https://docs.ipfs.tech/community/contribute/contribution-tut...

- libp2p maintainers call (networking layer of IPFS & other p2p networks): https://libp2p.io/get-involved/

New comment by momack2 in "IPFS Maintainers Winding Down"

momack2 — Mon, 24 Aug 2026 19:46:04 +0000

The post here is pretty confusing (so no blame to anyone who reads this as "IPFS the project" shutting down instead of just a single maintainer team, it's totally misleading) - but this is actually just a sunset announcement for _Shipyard_ - one of many IPFS implementation maintainers.

*The IPFS Project is not sunsetting or shutting down* - just switching to individual maintainer grants instead of centralized implementation support within Shipyard.

New comment by momack2 in "Filecoin Virtual Machine – Polyglot, WASM-based execution environment"

momack2 — Wed, 13 Jul 2022 20:11:52 +0000

Yep! The SNARKiest network out there I believe! https://research.protocol.ai/sites/snarks/

New comment by momack2 in "Filecoin Virtual Machine – Polyglot, WASM-based execution environment"

momack2 — Wed, 13 Jul 2022 20:10:12 +0000

Hm, I've taken a look at some of the Storage Provider ROI dashboards and AFAIK numbers aren't anything like that -- so not sure what timeframe or cost of goods you're extrapolating from. (ex https://fgas.io/)

I'm also confused how your model accounts for all the ecosystem development and enablement work that is being done across the Filecoin ecosystem. Filecoin isn't just another ETH clone - there is a ton of engineering and product work happening across many teams, with a ton of resources and dev work being poured into them (ex https://www.youtube.com/watch?v=ApVVg78ZBog)

Fine to complain about crypto economic token distributions or something specific - but please don't imply that the dev teams working on Filecoin / IPFS are freeloading or disingenuous. There's a massive amount of work going into building new content-addressed web primitives by some very mission-driven folks that you're unintentionally maligning. (full disclosure - I'm one of them)

New comment by momack2 in "Filecoin Virtual Machine – Polyglot, WASM-based execution environment"

momack2 — Wed, 13 Jul 2022 19:36:26 +0000

You have 2 main pathways for building on FVM: 1. (available sooner) Building an EVM smart contract that then interfaces with Filecoin's built-in actors. This will use existing EVM smart contract dev tools like HardHat, Truffle, Remix, Metamask, etc - and most contracts will likely be written in solidity (or any other EVM compatible language) 2. Native Rust smart contracts (or any language that compiles to run directly in the wasm FVM runtime). There is less tooling available for this today (though there are a few WIP SDKs being built in the Early Builders program), but maybe more accessible if you don't know solidity.

You can look for some of the FVM Foundry demo videos to see what folks are building so far! https://www.youtube.com/watch?v=jTtZh1zqUr8

New comment by momack2 in "Subdomains for IPFS"

momack2 — Tue, 29 Jun 2021 01:35:42 +0000

Example: most NFT marketplaces (OpenSea, Foundation, Palm, etc) use IPFS and Filecoin - https://blog.ipfs.io/2021-06-17-opensea-ipfs-filecoin/

New comment by momack2 in "Subdomains for IPFS"

momack2 — Mon, 28 Jun 2021 23:31:41 +0000

Hmm, I wouldn't assume the goal here is censorship resistance (esp given IPFS+ENS already fits that niche better). Looks to me like someone in the ecosystem is seeing the recent massive speed up to IPNS publishing (launched last week) and testing the waters on whether an "IPNS+DNS as a service" site would be useful to the folks that host dweb sites on IPFS.

New comment by momack2 in "Subdomains for IPFS"

momack2 — Mon, 28 Jun 2021 23:21:32 +0000

Not sure when you last paged into IPFS - the team has made some pretty awesome performance improvements in the past year and seen strong adoption to match (ex, nearly all NFTs are stored on IPFS today).

Definitely check out the IPFS 0.9 release from last week if you haven't seen it! Has some MASSIVE speed ups to IPNS propagation - we're talking less than a second resolution now! There's also a new experimental DHT client that can provide 30M records in about 2.5 hours (which the folks at nft.storage are using reliably at scale). -- https://github.com/ipfs/go-ipfs/releases/tag/v0.9.0

New comment by momack2 in "IPFS via OnionCat and Anonymous Proxy"

momack2 — Wed, 26 May 2021 18:40:51 +0000

This is cool! Curious if you'd be interested in doing a more formal anonymity audit of OnionCat+IPFS? AFAIK, the main hesitancy in making more of these capabilities broadly available is a potential mismatch between _expectations_ of privacy from a TOR+IPFS solution vs real-world constraints on reader/writer privacy for a distributed p2p system.

New comment by momack2 in "IPFS Support in Brave"

momack2 — Wed, 20 Jan 2021 02:07:40 +0000

On this page in Brave (chrome-extension://nibjojkomfdiaoajekhjakgkdhaomnch/dist/options/options.html) you can choose any IPFS gateway you prefer (or even run your own gateway if you want!).

List of public IPFS gateways available here: https://ipfs.github.io/public-gateway-checker/

New comment by momack2 in "IPFS 0.7.0, the SECIO retirement edition"

momack2 — Fri, 25 Sep 2020 09:04:18 +0000

That's a great idea! I know there's a project in the works to have redundant copies of the Archive stored on Filecoin, so expanding that to also make the data available for Collaborative Clusters should be totally doable. We'd have to slice the archive down into bites that small machines like yours and mine can help with though. Thanks for the suggestion!

New comment by momack2 in "IPFS 0.7.0, the SECIO retirement edition"

momack2 — Thu, 24 Sep 2020 19:53:34 +0000

You can become an IPFS Cluster Follower (https://collab.ipfscluster.io/#instructions) and help back up various datasets of IPFS content (like Project Gutenberg, Package Managers, Websites, etc)

New comment by momack2 in "IPFS 0.7.0, the SECIO retirement edition"

momack2 — Thu, 24 Sep 2020 19:44:22 +0000

We're actually implementing a standard Pinning API right now! You can check out the spec here (https://github.com/ipfs/pinning-services-api-spec) - currently being integrated by Pinata and soon others.

By the way, here's a PR to add other pinning options to the docs: https://github.com/ipfs/ipfs-docs/pull/471

New comment by momack2 in "IPFS 0.7.0, the SECIO retirement edition"

momack2 — Thu, 24 Sep 2020 18:36:18 +0000

When was the last time you tried? 0.5.0 from May had a lot of improvements - but go is still a hungry hungry beast. maybe try using Desktop which sets a lower peer count?

New comment by momack2 in "IPFS 0.7.0, the SECIO retirement edition"

momack2 — Thu, 24 Sep 2020 18:27:35 +0000

Thanks! We've been making a lot of updates to the documentation to make it easier to use - so glad it feels easy to follow!

I'll follow up on the Pinata docs example. There are a lot of options for how to persist content in the IPFS network, and we should describe all of them (even if Pinata is one of the smoother/easier to use ones for those new to IPFS who don't want to run their own persistent node). Feel free to file an issue or PR on that docs page if you get a second and we'll help get that fixed ASAP.

Given interest in decentralized persistence, you may be interested in collaborative clusters which allow a group of peers to all persist each other's content: https://collab.ipfscluster.io/ & https://cluster.ipfs.io/documentation/collaborative/

New comment by momack2 in "Filecoin: Proof of Storage Systems"

momack2 — Wed, 19 Aug 2020 20:41:36 +0000

You may enjoy this HackFS Workshop from Juan Benet (creator of Filecoin) that starts pretty high level but gets much more into the details of how the Filecoin network works: https://www.youtube.com/watch?v=P28aNAdZDi4

New comment by momack2 in "I built an IPFS crawler with libp2p"

momack2 — Mon, 15 Jun 2020 23:35:12 +0000

Correct, IPFS is not a blockchain - while both are merkle-dags ('directed acyclic graphs' of hash-linked data), blockchains have all nodes sync the state collectively, while IPFS instead shards state across the entire network (such that each node maintains its own filestore).

New comment by momack2 in "I built an IPFS crawler with libp2p"

momack2 — Mon, 15 Jun 2020 23:28:35 +0000

Nope - but used by lots of blockchains for things like off-chain storage (since having a content-addressable handle for a file that can never change is super critical for things like smart contracts)