Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To me, it’s about the easy of connecting a comments relevance to the post, assuming CTO was on the founding team, so makes sense that them posting they had never seen the post adds value to the thread; anyone else posting comment like that would have likely been down voted.

To me, fair to assume everyone does not know everyone else, though they might be familiar with a subset of the information, for example, knowing who Cloudflare is. If a user appending affiliation to a comment adds context, to me it makes sense to add it - and not assume or expect users to click your profile, other users point out who you are, etc.



But even if you didn't know the user was a cloudflare exec, the comment just becomes a boring throwaway comment from some luser on the internet telling you their thoughts, like posting 'Me too!' like some braindead AOLer.


Are you recommending we do the world a favour and cap him like old yeller?


Sorry, but do not understand references or generally what you were expressing; highly suggest reading all my comments in thread to avoid forcing me to unnecessarily repeat myself.


My point is that adding a disclaimer about your employer only matters if the post has a possibility of being seen as astroturfing if the reader doesn't know about the relationship between the poster and the company.

For example, if jgrahamc said "I never knew that. Cloudflare is such an amazing company, everyone should apply for a job there!", then okay, request a disclaimer. But if someone just says "I didn't know that", then the comment goes from mildly interesting (if you know who they are) to boring (if you don't know who they are). The failure mode here for lack of disclaimer is the post just becomes a boring, low-effort comment.

I think jgrahamc adding "I'm the CTO of cloudflare, and I didn't know that!" might have been reasonable context, but no disclaimer is required, because the reader didn't need to be protected from the post. There was no conflict of interest in the post.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: