3 ms·
I agree, but is this really something that needs to be a blog post? You could have easily commented it on the HN post or sent the author an email. This brings t
by paulgb 14y ago
I agree, but is this really something that needs to be a blog post? You could have easily commented it on the HN post or sent the author an email. This brings to mind the recent discussions of negativity on HN.
- citricsquid 14y agoThis is a problem that affects a lot of people that post on HN -- as in, their websites blame the user -- so the blog post helps everyone, right?
- paulgb 14y agoYes, but so would a comment, and it would come off as more constructive and less self-promotional.
- beezee 14y agonot that I mind a little traffic to my blog, but as I've mentioned in a few spots now this was more of a strategic choice in the sense of how I might incentivize the repo maintainer to give a crap.
- beezee 14y agoI did comment on the HN post, and also opened an issue on the repo (see my comment on this thread,) and based on the many ignored pull requests and issues on the repo and watching my comment go unnoticed in the original hn thread decided this would be my best chance to get a change implemented.
- beezee 14y agoAdditionally to directly address your reference to "negativity on HN" - as someone who submits their side projects here I'm all about fostering a supportive environment, however I don't think the same rules apply if your website includes a profile for me that I did not create and is effectively misrepresenting me. Wouldn't you say so?