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.

You mean http://github-trends.ryotarai.info/?

It could have been simpler and just as free in Yahoo!Pipes. RIP.

Parse it and publish it

the never satisfied freeloaders

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?

But Github issues are free. And they have a tweeting bot, also free.

An observation of how much these closed systems are a regression from systems we had 10 years ago.

Protocol ossification is also a real thing: we’re stuck in all the protocols developed two decades ago. https://signal.org/blog/the-ecosystem-is-moving/

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.

The maker posted the repo to get constructive criticism. They could have posted it on Producthunt or Facebook if they only wanted some appluase.

How do you know?

> Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread.

https://news.ycombinator.com/showhn.html