5 ms·
Did you read the first comment in the thread? It pointed to a draft announcement that was not intended for public release.
by eklitzke 5y ago
Did you read the first comment in the thread? It pointed to a draft announcement that was not intended for public release.
- ben0x539 5y agoSeems tricky. Surely the 262 comments were intended to be public.
- aeturnum 5y agoI mean, clearly they are public since we are all looking at them. I think this is a good reaction to accidentally publishing information that was intended to be private. Nothing is deleted, but you stop telling new people about it. People who already know can keep reading and talking.
- wrycoder 5y agoIn that case, I'd say bury it right away, not many hours later after it had collected hundreds of comments.
- deleted 5y ago[deleted]
- wrycoder 5y agoYes, it was an unintentional leak. That was obvious. What was more interesting - as is usually the case - was the HN discussion, from which I learned a lot.
- floatingatoll 5y agoWhen something that isn’t final or certain reaches the FP (such as rumors, predictions, or leaked drafts), the mods will often quash the post for being such, even when for example it’s an Apple rumors post with hundreds of comments. I’ve seen occasional exceptions to this, primarily when it’s lawmaking or RFC-type work, as those drafts are quite often newsworthy. A leaked FYIQ draft from an IRC admin wouldn’t have registered to me as newsworthy, not until it was published, so I would have made the same decision the mods did.
- Aeolun 5y agoI do not think HN should be the judge of whether a public webpage is intended as a draft. Certainly if it stays up after being covered.
- ineedasername 5y agoOnce it's out of the bag, all over reddit etc., might as well let the conversation continue.