I second not sharing anything that isn't already public.
But there is this pattern where these discussions get hashed out either (a) when someone misbehaves and dang posts a reply to remind them about the guidelines or (b) like this, we have an impromptu comment thread on HN's mechanisms. In either case, the content gets buried pretty quickly and we're relying essentially on human memories to keep this institutional knowledge alive.
I wonder if it would help to explicitly collate this information somewhere. Think, something parallel to the guidelines. But the guidelines answer the question, "how should I behave on HN?" whereas this would be answering "how is HN run?" (Or perhaps, how is it not run.)
It's a half-baked thought, so don't take it too seriously, but I figured I'd mention it.
There once was a "undocumented features of hacker news" which was on github when "awesome" lists on github were the gimmick a few years back. I do not recall the link or name now.
But there is this pattern where these discussions get hashed out either (a) when someone misbehaves and dang posts a reply to remind them about the guidelines or (b) like this, we have an impromptu comment thread on HN's mechanisms. In either case, the content gets buried pretty quickly and we're relying essentially on human memories to keep this institutional knowledge alive.
I wonder if it would help to explicitly collate this information somewhere. Think, something parallel to the guidelines. But the guidelines answer the question, "how should I behave on HN?" whereas this would be answering "how is HN run?" (Or perhaps, how is it not run.)
It's a half-baked thought, so don't take it too seriously, but I figured I'd mention it.