trash
Sorry to disappoint but there was no serious attention. Shen identified the potential pitfall while working on something else decided to look at existing ring signature implementations he could find to see if any of them had the bug. Both OZcoin and Shadow seemed to have it. It's possible he missed something too, and Shadow is protected in some manner, although it doesn't really look that way (the code posted here doesn't seem to fix it). I guess we'll see after further attention is given to it.
Another assumption by Smooth and Co. So he happened to be working on something else and just decided to create a blog (who's only post is dedicated to this FUD)
No, he discovered the issue and wanted to write it up somewhere. That's what you do when you are a cryptographer, you write up math stuff. It wasn't really enough substance for a real paper so he put it on a blog.
and reddit post
The reddit post didn't come from him, and as for the rest of the "PR blast", I'll just say you are naive if you think this sort of thing isn't going to be talked about. That's just the nature of crypto. There are plenty of people commenting about bugs in Monero when we've had them.
Agreed that the math doesn't justify a full paper. Glad to see that some people are attempting serious mathematical and cryptographic discussions on potential implementations (granted, it could be an oversight in thinking what the code does versus what it actually does). In the civilized world, cryptographic researchers don't call other people trolls for making honest mistakes about an implementation when the scenario is that they are trying to have an honest discussion about the potential overall problems of systems that may have a faulty implementation.
* complexring goes and gets his popcorn stand