profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/momack2/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
MollyM momack2 @protocol @ipfs @libp2p @filecoin momack.eth.link @ipfs @filecoin @libp2p Product & Engineering Lead at @protocol. Building #web3 to be #p2p & #LocalFirst.

filecoin-project/community 207

Filecoin community and ecosystem channels, discussion forums, and more

filecoin-project/FIPs 112

The Filecoin Improvement Proposal repository

filecoin-project/filecoin-docs 106

Filecoin Docs

ipfs/devgrants 77

The IPFS Grant platform connects funding organizations with builders and researchers in the IPFS community.

jbenet/data 56

package manager for datasets

ipfs/local-offline-collab 45

Local Offline Collaboration Special Interest Group

libp2p/website 22

Webpage of the libp2p project. A multi protocol approach for a interoperable network stack that follows the 'self description' in favor of assumptions

jbenet/datadex 21

a dataset index

filecoin-project/sentinel 18

A Filecoin Network Monitoring and Analysis System

Digital-MOB-Filecoin/QABot 14

Quality Bot: Periodically makes storage and retrieval deals with each of the top 100 miners, tracking state & success/fail.

issue commentipfs/ipfs-docs

Include community-managed bootstrap nodes to the Configure a Node page.

I think it can be fairly permissive - but some good standing in the ecosystem required (a malicious node could ex be annoying by bootstrapping new nodes into an isolated network and refuse to resolve content / peer them with other nodes).

momack2

comment created time in 17 hours

push eventfilecoin-project/FIPs

Kaitlin Beegle

commit sha beb517e7030cafdaf4c36451019f21473005ba7f

Update and rename fip-xxxx-snap-deals.md to fip-0019.md FIP number assigned

view details

MollyM

commit sha f21a653d062bccfb741f4dbc4f24949e8105f9d8

Merge pull request #175 from filecoin-project/kaitlin-beegle-patch-3 Update and rename fip-xxxx-snap-deals.md to fip-0019.md

view details

push time in 2 days

delete branch filecoin-project/FIPs

delete branch : kaitlin-beegle-patch-3

delete time in 2 days

PullRequestReviewEvent

pull request commentfilecoin-project/FIPs

Commit with expired deals

@nicola - correct me if I'm wrong, but I believe if a miner never packs a deal into a sector, even after calling declare publish storage deals, they never lose a sector collateral (because all sectors they pack, not including that deal, are valid). Therefore I think we are already in the first case and should apply this change because it will have the beneficial impact of causing FEWER deals to need retries / fail to complete without actually changing the mental model. @arajasek @ZenGround0 - is that right?

ZenGround0

comment created time in 3 days

PullRequestReviewEvent

issue commentfilecoin-project/FIPs

Revert FIP repo architecture to fix broken links, and prioritize humans again

PR in question was https://github.com/filecoin-project/FIPs/pull/125/files -- @bmann - can you help revert the rename of the "FIPS" folder to "_fips"?

image

jbenet

comment created time in 8 days

issue commentfilecoin-project/FIPs

FIP proposal: Allow storage providers to set *negative* prices for verified storage deals

There are some open implementation questions in actors that need more consideration (and are currently lower priority for the actors team to review than other FIPs currently in PR). Ex - for a negatively priced deal - is the negative price delivered to the storage client up-front (as a one-time bounty for the deal), or "vested" out of the payment channel over time (as it currently is when the storage client pays the provider)? If the latter, what happens on deal termination (it wouldn't make sense for the client to stop getting their bounty if the storage provider terminates!)? Are there any incentive misalignments or attack vectors for a storage provider to self-deal and cheat the Network in this new construction?

If others are excited about this idea, would love a slightly deeper dive proposal on how to handle some of these edge cases within the deal making spec in an incentive-aligned way!

momack2

comment created time in 8 days

issue commentipfs/ipfs-docs

Include community-managed bootstrap nodes to the Configure a Node page.

Maybe we can just start with this list here? https://docs.ipfs.io/how-to/peering-with-content-providers/#content-provider-list

momack2

comment created time in 8 days

IssuesEvent

issue commentipfs/ipfs-docs

Include community-managed bootstrap nodes to the Configure a Node page.

I don't think that was quite the intended approach, @johnnymatthews. This issue came from sourcing/identifying additional mechanisms to heal from hypothetical DOS attacks against the pre-configured IPFS bootstrap node list that ships in go-ipfs. With a community list here in the docs, nodes could re-configure to new bootstrap nodes if those default nodes are ever DOSed in an attack (unable to bootstrap new nodes into the network). The todo items to make this possible are:

  • [ ] Request "bootstrap" node addresses from IPFS Operators (ex @andrewxhill, @obo20, @MichaelMure, @bmann, etc)
  • [ ] Make a table with those addresses that others can PR to
momack2

comment created time in 8 days

push eventfilecoin-project/FIPs

Marten Seemann

commit sha c81fadecb6897b42f862895130ca512484ff8337

fix broken link to FIPs in README

view details

MollyM

commit sha 3bb2c1e955d033a6d27198916e5b95c905bad4fa

Merge pull request #150 from marten-seemann/patch-1 fix broken link to FIPs in README

view details

push time in 24 days

PR merged filecoin-project/FIPs

Reviewers
fix broken link to FIPs in README
+1 -1

1 comment

1 changed file

marten-seemann

pr closed time in 24 days

PullRequestReviewEvent

issue commentfilecoin-project/notary-governance

Modification: Large Dataset Notary Process - Reducing time to DataCap for LDN

Tagging @whyrusleeping since he also had some ideas to improve the process

galen-mcandrew

comment created time in a month

issue commentfilecoin-project/FIPs

FIP Discussion: CC Sector Repair Tool

After reading the grant proposal - my understanding is this aims to build a tool/library that can re-create a sector (and replace it from the Filecoin protocol's perspective) if an error is encountered. It allows a storage provider to seal a new sector with the same ticket/cid/etc and use it to slot in place of a broken sector. So if you have a deals sector, you set up the exact same sector info/data/contents as before, and do the same sealing process to generate a new sector, which the Filecoin blockchain should then accept instead of the old sector when it comes to wPoSt, collateral, deal rewards, etc.

I think this does likely have core protocol implications (ex, the sector was sealed with different randomness, it may have a different lifetime and collateral than a new sector sealed later, your contract with the deal-maker may or may not be upheld, etc). I'd like @nicola and @zixuanzh to comment on this from the security/cryptoecon perspectives early so you know what constraints/roadblocks to navigate!

FWIW - I know there have been some conversations about making CCSectors more "fungible" between folks like @anorth @Kubuxu etc - so maybe they also have thoughts or ideas to contribute to your approach.

realChainLife

comment created time in a month

push eventipfs/ipfs-blog

Stan Yee

commit sha 2741788434f85bd7baa62fc7561aaacdd2cf77c2

Update from Forestry.io Stan Yee created src/assets/jupiter-hackathon-ipfs-alibaba-cloud-hdr.jpeg Stan Yee created src/_blog/announcing-the-jupiter-hackathon.md

view details

Stan Yee

commit sha 5de105fcace3395a3cba473d39cc232379a0adfe

Update from Forestry.io Stan Yee created src/assets/asia-hackathon-season-ipfs.jpeg Stan Yee created src/_blog/about-500-000-in-prizes-and-grants-for-asia-hackathon-season-2021.md

view details

emily.vaughan@protocol.ai

commit sha 7b054f22723ebe2eed62b6561cb93827d95dc6d6

Update from Forestry.io emily.vaughan@protocol.ai updated src/_blog/about-500-000-in-prizes-and-grants-for-asia-hackathon-season-2021.md

view details

emily.vaughan@protocol.ai

commit sha 53d629513e3af19ea7dbeaff1f4827c821dcadb5

Update from Forestry.io emily.vaughan@protocol.ai created src/assets/ipfs-blog-gateway.jpg emily.vaughan@protocol.ai created src/_blog/aug-20-ipfs.io-gateway-outage-resolution-next-steps.md

view details

emily.vaughan@protocol.ai

commit sha 3593720a15950d3a7d4dc4a18f9023ea377d961a

Update from Forestry.io emily.vaughan@protocol.ai created src/assets/ipfs-blog-gateway-2.jpg emily.vaughan@protocol.ai updated src/_blog/aug-20-ipfs.io-gateway-outage-resolution-next-steps.md

view details

emily.vaughan@protocol.ai

commit sha e4659fd811709e85a8457202a9a7f26350542d04

Update from Forestry.io emily.vaughan@protocol.ai updated src/_blog/aug-20-ipfs.io-gateway-outage-resolution-next-steps.md emily.vaughan@protocol.ai created src/assets/ipfs-blog-gateway-5.jpg

view details

github-actions[bot]

commit sha 0c27585ee14cac99f7f4da37b7691e904568d452

Optimised images with calibre/image-actions

view details

emilymvaughan

commit sha b8a69c3d1206aa32dbc5e0912e93659b6f48acc6

Update src/_blog/aug-20-ipfs.io-gateway-outage-resolution-next-steps.md Co-authored-by: MollyM <momack2@users.noreply.github.com>

view details

MollyM

commit sha d6874f6a9269e1c5d25d02c5233d01872eb530b2

Apply suggestions from code review

view details

MollyM

commit sha 749fa75f458bb2047d0eb1845c3130e0140ab127

Merge pull request #309 from ipfs/staging Add blog: August 20 Incident Report + Asia Hackathon Season

view details

push time in a month

push eventipfs/ipfs-blog

MollyM

commit sha d6874f6a9269e1c5d25d02c5233d01872eb530b2

Apply suggestions from code review

view details

push time in a month

Pull request review commentipfs/ipfs-blog

Add blog: August 20 Incident Report + Asia Hackathon Season

+---+title: August 20 IPFS.io Gateway Outage Resolution & Next Steps+description: The ipfs.io gateway & website experienced an outage on 2021-08-20; here+  are more details & corrective actions.+author: IPFS Team+date: 2021-08-27+permalink: 2021-08-27-IPFS.io-gateway-outage-resolution+translationKey: ''+header_image: "/ipfs-blog-gateway-5.jpg"+tags:+- gateways++---+# Customer Impact++On 2021-08-20 at 15:54 UTC, visitors started to get 404s across all HTTPS content served from the[ ipfs.io](http://ipfs.io/) domain. 404s were returned for both:++1. Web properties under the[ ipfs.io](http://ipfs.io/) domain: the[ ](http://ipfs.io/)ipfs website ([https://ipfs.io](https://ipfs.io "https://ipfs.io")), ipfs docs ([https://docs.ipfs.io](https://docs.ipfs.io "https://docs.ipfs.io")), ipfs dist ([https://dist.ipfs.io](https://dist.ipfs.io "https://dist.ipfs.io")), ipfs blog ([https://blog.ipfs.io](https://blog.ipfs.io "https://blog.ipfs.io")), etc. AND+2. Content served over the IPFS over HTTP gateway at[ ](https://ipfs.io/ipfs)[https://ipfs.io/ipfs](https://ipfs.io/ipfs "https://ipfs.io/ipfs")++Users across the internet fetch content from the IPFS network using the ipfs.io gateway over 300 **million** times per week, and were thus impacted until our mitigation was applied at 19:35 UTC. You can see the full incident report and history [on the status page](https://ipfsgateway.statuspage.io/).++However, you can instead fetch content directly from the IPFS network without hitting any of these gateways by using your own IPFS node with [IPFS Desktop](https://docs.ipfs.io/install/ipfs-desktop/), [IPFS CLI](https://docs.ipfs.io/how-to/command-line-quick-start), [IPFS Companion](https://docs.ipfs.io/install/ipfs-companion/) in your browser, and/or an [IPFS-enabled browser like Brave](https://brave.com/ipfs-support/). **If you were using IPFS directly, you probably never even noticed this outage! 💪**++# Background++As a reminder, IPFS and Filecoin are peer-to-peer applications to store and provide content in a distributed fashion. In such architecture, every peer (person or company) controls what it contributes to the network, how it does it, and how it interacts with other peers and their content. The architecture of Filecoin and IPFS is designed to embody the principle of **user agency**.++IPFS HTTP gateways (like the one at [https://ipfs.io/ipfs](https://ipfs.io/ipfs "https://ipfs.io/ipfs")) allow browsers and tools that speak HTTP to access content from the IPFS network. They don’t represent all of IPFS, but rather the HTTP resolution; they provide the canonical way to address IPFS content via http scheme URLs. The ipfs.io gateway is a community resource run by Protocol Labs to help developers build on IPFS, but it is just one of many gateways hosted by many groups (see [a list of 100+ gateways and their statuses](https://ipfs.github.io/public-gateway-checker/)).++Gateway operators do not store or host the data that is viewable through the gateway. Rather, the gateway allows users to view content hosted by the thousands of independent node operators across the IPFS Network. While the best practice for reporting apparently illegal or otherwise objectionable content is to directly contact the node operator hosting the data, gateway operators can also block the ability of users to view a particular piece of content via their gateway in appropriate circumstances. Protocol Labs operates the ipfs.io gateway and regularly receives and complies with reports of this nature through the [abuse@protocol.ai](abuse@protocol.ai) and [abuse@ipfs.io](abuse@ipfs.io) addresses.++# What Happened++On Friday, ipfs.io’s domain registrar received complaints about objectionable content being served through the ipfs.io gateway. In response, the domain registrar took down the _entire_ ipfs.io domain by setting the records for the domain to point to a “black hole” address. Our automated monitoring detected the issue within minutes, and internal & external users started posting observations of 404s within 30 minutes as the DNS record update propogated, which triggered a full incident response. Per above, the blast radius of this domain takedown affected both the ipfs-related websites and the ipfs gateways because they were housed together.++# How we resolved it++Our first priority thread was to remove the objectionable content and get the domain registrar to restore the ipfs.io DNS records. After a few escalation hops, our legal team was able to speak with the domain registrar, which eventually reinstated our domain.++While our legal team engaged with the domain registrar, we also:++1. Initiated the domain migration to Cloudflare (big thanks to the Cloudflare team on getting our transfer expedited!), where we have existing relationships and a support contract. Not to mention, they’re [already pretty familiar with IPFS](https://developers.cloudflare.com/distributed-web/ipfs-gateway).+2. Because all of the IPFS web content is static and stored in IPFS, we created/updated [ipfs.eth.link](http://ipfs.eth.link/) records to reference the latest content of our sites and various subdomains like [docs.ipfs.ens.link](http://docs.ipfs.ens.link/) and [dist.ipfs.eth.link](http://dist.ipfs.eth.link/). We publicized the availability of that content on social media and status pages. This brought all the main IPFS site content back online immediately using the distributed web! 🎉+3. We also reminded gateway users of the [100+ other gateways](https://ipfs.github.io/public-gateway-checker/) that could be used besides ipfs.io, including dweb.link.
3. We also reminded gateway users of the [100+ other gateways](https://ipfs.github.io/public-gateway-checker/) that could be used besides ipfs.io, including [dweb.link](https://dweb.link).
emilymvaughan

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentipfs/ipfs-blog

Add blog: August 20 Incident Report + Asia Hackathon Season

+---+title: August 20 IPFS.io Gateway Outage Resolution & Next Steps+description: The ipfs.io gateway & website experienced an outage on 2021-08-20; here+  are more details & corrective actions.+author: IPFS Team+date: 2021-08-27+permalink: 2021-08-27-IPFS.io-gateway-outage-resolution+translationKey: ''+header_image: "/ipfs-blog-gateway-5.jpg"+tags:+- gateways++---+# Customer Impact++On 2021-08-20 at 15:54 UTC, visitors started to get 404s across all HTTPS content served from the[ ipfs.io](http://ipfs.io/) domain. 404s were returned for both:++1. Web properties under the[ ipfs.io](http://ipfs.io/) domain: the[ ](http://ipfs.io/)ipfs website ([https://ipfs.io](https://ipfs.io "https://ipfs.io")), ipfs docs ([https://docs.ipfs.io](https://docs.ipfs.io "https://docs.ipfs.io")), ipfs dist ([https://dist.ipfs.io](https://dist.ipfs.io "https://dist.ipfs.io")), ipfs blog ([https://blog.ipfs.io](https://blog.ipfs.io "https://blog.ipfs.io")), etc. AND+2. Content served over the IPFS over HTTP gateway at[ ](https://ipfs.io/ipfs)[https://ipfs.io/ipfs](https://ipfs.io/ipfs "https://ipfs.io/ipfs")
2. Content served over the IPFS over HTTP gateway at `https://ipfs.io/ipfs/<cid>`
emilymvaughan

comment created time in a month

Pull request review commentipfs/ipfs-blog

Add blog: August 20 Incident Report + Asia Hackathon Season

+---+title: August 20 IPFS.io Gateway Outage Resolution & Next Steps+description: The ipfs.io gateway & website experienced an outage on 2021-08-20; here+  are more details & corrective actions.+author: IPFS Team+date: 2021-08-27+permalink: 2021-08-27-IPFS.io-gateway-outage-resolution+translationKey: ''+header_image: "/ipfs-blog-gateway-5.jpg"+tags:+- gateways++---+# Customer Impact++On 2021-08-20 at 15:54 UTC, visitors started to get 404s across all HTTPS content served from the[ ipfs.io](http://ipfs.io/) domain. 404s were returned for both:++1. Web properties under the[ ipfs.io](http://ipfs.io/) domain: the[ ](http://ipfs.io/)ipfs website ([https://ipfs.io](https://ipfs.io "https://ipfs.io")), ipfs docs ([https://docs.ipfs.io](https://docs.ipfs.io "https://docs.ipfs.io")), ipfs dist ([https://dist.ipfs.io](https://dist.ipfs.io "https://dist.ipfs.io")), ipfs blog ([https://blog.ipfs.io](https://blog.ipfs.io "https://blog.ipfs.io")), etc. AND
1. Web properties under the [ipfs.io](http://ipfs.io/) domain, including: the ipfs website ([ipfs.io](https://ipfs.io "https://ipfs.io")), ipfs docs ([docs.ipfs.io](https://docs.ipfs.io "https://docs.ipfs.io")), ipfs dist ([dist.ipfs.io](https://dist.ipfs.io "https://dist.ipfs.io")), ipfs blog ([blog.ipfs.io](https://blog.ipfs.io "https://blog.ipfs.io")), etc. AND
emilymvaughan

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentipfs/ipfs-blog

Add blog: August 20 Incident Report + Asia Hackathon Season

+---+title: August 20 IPFS.io Gateway Outage Resolution & Next Steps+description: The ipfs.io gateway & website experienced an outage on 2021-08-20; here+  are more details & corrective actions.+author: IPFS Team+date: 2021-08-27+permalink: 2021-08-27-IPFS.io-gateway-outage-resolution+translationKey: ''+header_image: "/ipfs-blog-gateway-5.jpg"+tags:+- gateways++---+# Customer Impact++On 2021-08-20 at 15:54 UTC, visitors started to get 404s across all HTTPS content served from the[ ipfs.io](http://ipfs.io/) domain. 404s were returned for both:++1. Web properties under the[ ipfs.io](http://ipfs.io/) domain: the[ ](http://ipfs.io/)ipfs website ([https://ipfs.io](https://ipfs.io "https://ipfs.io")), ipfs docs ([https://docs.ipfs.io](https://docs.ipfs.io "https://docs.ipfs.io")), ipfs dist ([https://dist.ipfs.io](https://dist.ipfs.io "https://dist.ipfs.io")), ipfs blog ([https://blog.ipfs.io](https://blog.ipfs.io "https://blog.ipfs.io")), etc. AND+2. Content served over the IPFS over HTTP gateway at[ ](https://ipfs.io/ipfs)[https://ipfs.io/ipfs](https://ipfs.io/ipfs "https://ipfs.io/ipfs")++Users across the internet fetch content from the IPFS network using the ipfs.io gateway over 300 **million** times per week, and were thus impacted until our mitigation was applied at 19:35 UTC. You can see the full incident report and history [on the status page](https://ipfsgateway.statuspage.io/).++However, you can instead fetch content directly from the IPFS network without hitting any of these gateways by using your own IPFS node with [IPFS Desktop](https://docs.ipfs.io/install/ipfs-desktop/), [IPFS CLI](https://docs.ipfs.io/how-to/command-line-quick-start), [IPFS Companion](https://docs.ipfs.io/install/ipfs-companion/) in your browser, and/or an [IPFS-enabled browser like Brave](https://brave.com/ipfs-support/). **If you were using IPFS directly, you probably never even noticed this outage! 💪**++# Background++As a reminder, IPFS and Filecoin are peer-to-peer applications to store and provide content in a distributed fashion. In such architecture, every peer (person or company) controls what it contributes to the network, how it does it, and how it interacts with other peers and their content. The architecture of Filecoin and IPFS is designed to embody the principle of **user agency**.++IPFS HTTP gateways (like the one at [https://ipfs.io/ipfs](https://ipfs.io/ipfs "https://ipfs.io/ipfs")) allow browsers and tools that speak HTTP to access content from the IPFS network. They don’t represent all of IPFS, but rather the HTTP resolution; they provide the canonical way to address IPFS content via http scheme URLs. The ipfs.io gateway is a community resource run by Protocol Labs to help developers build on IPFS, but it is just one of many gateways hosted by many groups (see [a list of 100+ gateways and their statuses](https://ipfs.github.io/public-gateway-checker/)).++Gateway operators do not store or host the data that is viewable through the gateway. Rather, the gateway allows users to view content hosted by the thousands of independent node operators across the IPFS Network. While the best practice for reporting apparently illegal or otherwise objectionable content is to directly contact the node operator hosting the data, gateway operators can also block the ability of users to view a particular piece of content via their gateway in appropriate circumstances. Protocol Labs operates the ipfs.io gateway and regularly receives and complies with reports of this nature through the [abuse@protocol.ai](abuse@protocol.ai) and [abuse@ipfs.io](abuse@ipfs.io) addresses.++# What Happened++On Friday, ipfs.io’s domain registrar received complaints about objectionable content being served through the ipfs.io gateway. In response, the domain registrar took down the _entire_ ipfs.io domain by setting the records for the domain to point to a “black hole” address. Our automated monitoring detected the issue within minutes, and internal & external users started posting observations of 404s within 30 minutes as the DNS record update propogated, which triggered a full incident response. Per above, the blast radius of this domain takedown affected both the ipfs-related websites and the ipfs gateways because they were housed together.++# How we resolved it++Our first priority thread was to remove the objectionable content and get the domain registrar to restore the ipfs.io DNS records. After a few escalation hops, our legal team was able to speak with the domain registrar, which eventually reinstated our domain.++While our legal team engaged with the domain registrar, we also:++1. Initiated the domain migration to Cloudflare (big thanks to the Cloudflare team on getting our transfer expedited!), where we have existing relationships and a support contract. Not to mention, they’re [already pretty familiar with IPFS](https://developers.cloudflare.com/distributed-web/ipfs-gateway).+2. Because all of the IPFS web content is static and stored in IPFS, we created/updated [ipfs.eth.link](http://ipfs.eth.link/) records to reference the latest content of our sites and various subdomains like [docs.ipfs.ens.link](http://docs.ipfs.ens.link/) and [dist.ipfs.eth.link](http://dist.ipfs.eth.link/). We publicized the availability of that content on social media and status pages. This brought all the main IPFS site content back online immediately using the distributed web! 🎉
2. Because all of the IPFS web content is static and stored in IPFS, we created/updated [ipfs.eth.link](http://ipfs.eth.link/) records to reference the latest content of our sites and various subdomains like [docs.ipfs.ens.link](http://docs.ipfs.ens.link/), [blog.ipfs.ens.link](http://blog.ipfs.ens.link/), and [dist.ipfs.eth.link](http://dist.ipfs.eth.link/). We publicized the availability of that content on social media and status pages. This brought all the main IPFS site content back online immediately using the distributed web! 🎉
emilymvaughan

comment created time in a month

issue commentfilecoin-project/community

A well-known open source project is missing FIL

This isn’t complete yet. 2 FIL bounty stands!

forjdk

comment created time in a month

push eventfilecoin-project/FIPs

Boris Mann

commit sha 4ecce355b8066ac65c971a7b731040ca30093618

Change master branch to auto-publish Missed this in the big PR. Secrets _should_ have copied across I think.

view details

MollyM

commit sha 1550a45becabff71512230d29f771f13a02ef8b5

Merge pull request #147 from application-research/bmann-fission-publish-master Change master branch to auto-publish

view details

push time in a month