Hacker News new | past | comments | ask | show | jobs | submit login

In your case that was true. General explanation here: https://news.ycombinator.com/item?id=42902318.

I didn't see much misuse of vouching in your recent history so I've removed that penalty from your account now. But please make sure that the comments you're vouching for are respecting the site guidelines (https://news.ycombinator.com/newsguidelines.html).






Why don't you make such things transparent and clear on a user's account so they can see what you've done?

You're keen on reviewing a user's recent history, but provide no corresponding transparency to the user on what you've done.


Because I'm scared of how much extra work it would create, and because it's the sort of frog-boiling bureaucratism that it is in the spirit of this site to avoid. I call it frog-boiling because it's easy for me to imagine that one day I would wake up and be horrified by the systems we had inadvertently let spring up around ourselves.

HN works best with informal systems, not formal ones. The informal contract around transparency is: people are welcome to ask questions and we always answer them, but we don't formally publish a moderation log or anything like that (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...).


> I call it frog-boiling because it's easy for me to imagine that one day I would wake up and be horrified by the systems we had inadvertently let spring up around ourselves.

You're already removing the ability of users to vouch. That frog is boiled.

I'm saying tell them on their user page. Include a line that only they can see which says "can no longer vouch" or similar. That way they know what's happened instead of having to guess what's happened.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: