I maintain the gitignore.io repo with about 900 stars and thankfully the contributors aren't as snarky. I will say that the users of gitignore.io are probably

I maintain the gitignore.io repo with about 900 stars and thankfully the contributors aren't as snarky. I will say that the users of gitignore.io are probably more on the technical side, but it just seems like Jake is not familiar with the culture of FOSS. That being said, He's a 'customer' of your 'product' and even though his delivery isn't the best, there may be something you can take away from suggestion. When I'm evaluating a FOSS project, the first thing I try and do if I find something wrong is see if there is a way I can fix it and submit a PR. Then if it looks like it's out of my scope, I'll file a bug or look for another project. For gitignore.io, I often take product decisions from the community, but I like to have a discussion about what the best course of action is. I still have open issues in my backlog that I just haven't found an elegant solution to yet. Thankfully gitignore.io has a small enough feature scope that you can't do much with it, otherwise i'm sure the project would become overbearing very quickly.