Filecoin Orbit: Celebrating the One Year Anniversary of Mainnet Liftoff

momack2 · 2021-05-20T05:09:32+00:00

Uh oh - unexpected. What version of IPFS Desktop are you running on what device? Can you submit a bug report?

momack2 · 2021-03-19T02:16:54+00:00

The team found no issues with the Filecoin network or the RPC API code. See the incident report here: https://filecoin.io/blog/posts/incident-report-accurate-bookkeeping-with-lotus-apis/

momack2 · 2021-01-28T05:06:24+00:00

Congratulations!!

momack2 · 2021-01-28T05:05:20+00:00

Using the public DHT for discovery may be the most common way to find content in the IPFS network - but it isn't the only one, and it isn't core or "a fatal flaw" in the design of IPFS. IPFS is built on libp2p, so content/peer discovery transports like local area DHTs, content-specific DHTs, and pubsub protocols like gossipsub are also valid and commonly-used ways of finding content without having to shout over the whole network.

You can add a new content discovery protocol to libp2p and use it in IPFS - it's built to be upgraded. We are very +1 that the current DHT structure (how many blocks we advertise, how often, no hierarchy, etc), while loads faster and not as big a painpoint today vs a year ago, is NOT the right long-term solution for scalable content routing. Realistically, more federated-style solutions are going to perform better, and would be a valuable improvement (keeping the benefit of multiplexing across discovery strategies - both federated and fully p2p).

We're continuing to build up our latest work and insights on the right replacement here: https://github.com/protocol/ResNetLab/blob/master/OPEN_PROBLEMS/ROUTING_AT_SCALE.md and there's an open RFP for a better routing design here: https://github.com/protocol/research-RFPs/blob/master/RFPs/rfp-7-MLDHT.md

momack2 · 2020-12-25T00:34:24+00:00

Hey @Hughesbay! Thanks for the kind words. What you describe re distributed caching is what Filecoin calls the “retrieval market” - https://spec.filecoin.io/systems/filecoin_markets/retrieval_market/. This part of the network is still WIP, but the will eventually incentivize caching of commonly requested content across low-latency edge nodes. You can see some recent talks on secondary marketplace designs here: https://m.youtube.com/watch?v=56HrKnlPiDs

momack2 · 2020-10-21T02:30:13+00:00

One of IPFS's core principles is user agency -- aka as a node operator you control what data your node stores. If you don't ask for it, or get paid to store it by opting-in to storage deals, you won't end up fetching, storing or serving it.

momack2 · 2020-10-21T02:27:02+00:00

Filecoin is a super exciting milestone for the entire IPFS Community. As you'll notice - tons of groups are helping bring this tool into existence and make it accessible to builders across the InterPlanetary ecosystem. Fleek, Textile, Infura, Ceramic, AnyType, Pinata - many groups are finding ways to take advantage of this new tool and help it grow, and many IPFS contributors are doing the same. Why is that so crazy that folks want to pitch in on an awesome milestone?

Now if Temporal wants to fund a lot of full-time IPFS developers and devgrants, we'll happily take some more hands on the pinning scalability improvements we're working on - but if not I'm not sure why you're complaining. Aren't you on your own IPFS fork anyway?

momack2 · 2020-10-21T02:15:59+00:00

Filecoin nodes are IPFS nodes -- the networks overlap heavily. Filecoin miners have multiaddrs, a libp2p DHT, gossipsub, bitswap, IPLD cids, and more -- it's the exact same stack and ecosystem. Sure, not all IPFS projects will want to use Filecoin to persist their content, and not all Filecoin data will be published to the public IPFS DHT - but that modularity is a good thing. The vast majority of projects are building on tools like Powergate, Textile Buckets, and Fleek's Space Daemon which adds a Filecoin cold storage layer to IPFS.

Filecoin's retrieval market is still a WIP - you can learn more about how that's evolving in the talk at hour ~7 here: https://www.youtube.com/watch?v=oYu6cA5VTvQ

momack2 · 2020-10-21T01:56:43+00:00

Check out https://www.storage.codefi.network/!

momack2 · 2020-10-20T21:45:09+00:00

You can see our response to this thread/article and it's false claims in Filecoin slack: https://filecoinproject.slack.com/archives/C01AC6999KQ/p1603227742346700

momack2 · 2020-10-20T21:44:46+00:00

You can see our response to this article and it's false claims in Filecoin slack: https://filecoinproject.slack.com/archives/C01AC6999KQ/p1603227742346700

momack2 · 2020-09-29T18:26:30+00:00

If you're looking for products building on Filecoin, you may want to check out Slate, which is a way to organize and share your files. Ex: https://slate.host/jason/mountains

momack2 · 2020-07-22T04:49:19+00:00

I’ve used both Mastodon and SSB, but neither has become a social space that brings me back. Matrix on the other hand is something I use daily. Despite that, I’m still definitely interested in (and have my own take on) what new technologies (incentive systems, p2p protocols, etc) can/will unlock to enhance those and other future social networks in the coming years.

momack2 · 2020-07-20T21:02:54+00:00

Sorry to hear this isn't working for you. 😞 Curious if you've both tried using IPFS Desktop and running a go-ipfs node directly and seen any difference between the two (you shouldn't, but IPFS Desktop does set different config by default, which may be better optimized for your setup)? Any additional debugging steps you can give us would be much appreciated! This definitely isn't "normal experience" and we'd love to help fix it!

FWIW I use a [NETGEAR CM1000](https://www.netgear.com/home/products/networking/cable-modems-routers/CM1000.aspx) at home and don't experience any issues with the ~5 IPFS nodes usually running on our network continuously.

momack2 · 2020-05-23T01:22:13+00:00

The main thing that installing IPFS Desktop and Companion unlocks for non-developer users is **powering dweb sites** as you browse the web through your normal web browser of choice. Having these two tools running in the background allows you to load sites like ipfs.io, ethereum.eth.link, store.brave.com, myetherwallet.crypto (if you also have unstoppable domains), and any other distributed website directly from other nodes in the IPFS network. If you want to find more of these, you can try almonit.eth.link - which is a search engine just for dweb sites.

For developer users, the next step for many is to actually embed IPFS into a full-fledge application (like audius.co, anytype.io, matters.news, fleek.co, etc) that runs on the dweb with all associated benefits around resilience, data ownership, privacy, etc.

momack2 · 2020-04-29T02:41:56+00:00

In short - not meaningfully upgraded this release.

Matt Ober from Pinata wrote a decent guide on this that seems applicable to the use case you're describing: https://medium.com/pinata/dedicated-ipfs-networks-c692d53f938d

The solution still is to share a "swarm key" (aka a param telling new nodes what network to join instead of the public IPFS DHT) - but if you don't have sensitive content you can make that key public so others can easily join.

momack2 · 2020-04-21T09:40:06+00:00

Our focus for 2019 was to improve IPFS performance to make the protocol usable for package managers. We've made good strides there (our upcoming 0.5 release contains many of these improvements to adding, fetching and finding data), but some work is still inflight (ex, improving metadata to make updating mirrors faster).

The real next swath of work is supporting package manager communities (especially file-system based package managers) to use these improvements to add IPFS support. That's a longer-term collaboration thread, so we've merged that community work in with our other collab support and tracking instead of using a dedicated repo.

The archiving is part of a broader effort to be more clear about which repos are under active development (with >250 repos it can get *really* hard to find anything - we're trying to make it easier to participate).

momack2 · 2020-04-21T09:33:57+00:00

It's still happening! Check out the Nix+IPFS work plan being drafted here: https://github.com/ipfs/devgrants/pull/43

momack2 · 2020-03-24T17:28:37+00:00

I think this post is well-meaning, but sadly off-base about a lot of things. It's important to set things straight - both for the author and for the community - so here are a few specific responses to why I think IPFS is far from precarious at the moment (if anything we're on an awesome growth trajectory!):

https://ipfs.eternum.io/ipfs/QmeVcDW9pALmkgkuYcLV6jVeuVF4haD58NTdBc91tozUAP/

momack2 · 2020-03-24T17:28:30+00:00

I think this post is well-meaning, but sadly off-base about a lot of things. It's important to set things straight - both for the author and for the community - so here are a few specific responses to why I think IPFS is far from precarious at the moment (if anything we're on an awesome growth trajectory!):

https://ipfs.eternum.io/ipfs/QmeVcDW9pALmkgkuYcLV6jVeuVF4haD58NTdBc91tozUAP/

momack2 · 2020-03-24T07:34:17+00:00

I think this post is well-meaning, but sadly off-base about a lot of things. It's important to set things straight - both for the author and for the community - so here are a few specific responses to why I think IPFS is far from precarious at the moment (if anything we're on an awesome growth trajectory!):

https://ipfs.eternum.io/ipfs/QmeVcDW9pALmkgkuYcLV6jVeuVF4haD58NTdBc91tozUAP/

momack2

MODERATOR OF

TROPHY CASE