momack2
Joined 13 years ago
Karma
327
Submissions
73
Member since
Apr 26
Recent submissions
Comment · 2 months ago
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!
Comment · 2 months ago
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.
Comment · 2 months ago
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/
Comment · 2 months ago
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.
Comment · 4 years ago
Yep! The SNARKiest network out there I believe! https://research.protocol.ai/sites/snarks/
Comment · 4 years ago
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)
Comment · 4 years ago
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
Comment · 5 years ago
Example: most NFT marketplaces (OpenSea, Foundation, Palm, etc) use IPFS and Filecoin - https://blog.ipfs.io/2021-06-17-opensea-ipfs-filecoin/
Comment · 5 years ago
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.
Comment · 5 years ago
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
Comment · 5 years ago
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.
Comment · 5 years ago
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/
Comment · 6 years ago
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!
Comment · 6 years ago
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)
Comment · 6 years ago
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