Couldn't this be done a lot more simply with a mailing list or RSS feed? Using GitHub issues seems a bit convoluted, although I'm guessing it's probably because it's easier to set up and free to use. It seems like somebody should build a service which makes use cases like this 0 config.
I think this is a much smarter way of building this than using a mailing list or RSS feed, both of which have non-trivial operational expenses associated with them. This implementation instead takes advantage of the enormous ecosystem of tools GitHub already has around their issue notifications.
Pointing out existing technologies that might be more appropriate to use is valid feedback. I don’t think that detracts from how neat the project is.
Some of the big questions I always ask myself before I set about writing code for something are: Can this be done with older and more mature tech? Is this already more or less solved by another project and what value am I adding?
Highly subjective. What some would call ossified, others might call “mature,” “reliable,” or “battle tested.” Sometimes bits don’t rot—they just go out of fashion.
