First: This is documented and we also warn users when they publish a page. But, that’s not good enough!
Second: We don’t like this and are looking at ways to fix this either by removing the PII from the public endpoints or by replacing it with an email proxy similar to GitHub’s equivalent functionality for public commits.
P.S: Some folks here have speculated that this should be a 1 minute fix. Unfortunately that is not the case. :(
Good question! We just shipped GitHub Discussions to millions of developers and we can learn whether people use and like the product by looking at whether people are creating discussions, customizing categories, and answering questions.
The argument that you need to follow users around every step of the way to build great products is simply untrue.
Creator of CloudApp here (no longer involved). This is really neat, thanks for sharing! You could potentially monitor ~/Desktop on OS X and identify screenshots with:
mdls 'Screen Shot 2016-10-24 at 4.14.54 PM.png' | grep IsScreenCapture
That would match the original behavior even closer.
Hacker News' design has a lot of personality and I would never recommend redesigning it (for the same reason I enjoy Craigslist's "design") but making it resolution independent and maybe even responsive sounds like a great idea.
Personally I prefer a slightly larger serif font when reading comments on here which is why I wrote a quick dotjs [1] script that now also replaces the upvote arrow GIF:
https://cleanshot.com/share/8yFpGVDQ