4 ms·
That is not addressing my question; why are they posted as 5 separate submissions instead of being 1 LiveBlog post or something?
by ebbv 11y ago
That is not addressing my question; why are they posted as 5 separate submissions instead of being 1 LiveBlog post or something?
- andyjohnson0 11y agoBecause they were posted by different people who didn't take your preference for a single post into account.
- ebbv 11y agoAt least two of them are posted by the same guy. And at least some, if not all of them, are being posted by Amazon employees. So again, I say, the AWS team is spamming HN and it's in poor form. It should all be one submission.
- kordless 11y agoNote that you are also getting voted down. Lot's of Amazon employees to hit down votes on people who say anything against them. This text may be grey. :)
- WaltPurvis 11y agoHe's getting voted down because he's completely wrong and semi-slandering Amazon employees with no factual basis, as are you.
- WaltPurvis 11y agoNo, it should not be all one submission. These are separate and distinct products, and I want to read separate and distinct HN discussions about them.
- ceejayoz 11y agoEach one is a separate post, about a separate service, which would logically generate separate, product-specific discussions.
- deleted 11y ago[deleted]
- andybak 11y agoI agree. A single post would just end up unmanageable and dominated by whoever had the top comment. (I always yearn for a 'by date' sort for HN comments as often the top comment hijacks the discussion on a tangent and it's annoying to find people discussing the primary topic)
- dang 11y ago> I always yearn for a 'by date' sort for HN comments We can't make a big flat list and sort those by date without losing the threadedness of the comments and thus their context. But we could sort siblings by date at each level of the tree, including the top level. Is that what you mean?
- andybak 11y ago> without losing the threadedness Sometimes this would be a good thing. Top-level (and in general 'higher up the tree' comments completely dominate. It's rare for the direction of a HN thread to shift much after a reasonable number of comments as everything gets buried quite far down. I'd really like a 'what changed since i was last here' button. Quite often I come back to a long thread I was especially interested in and I'm completely unable to find out if anything of value has been added. > But we could sort siblings by date at each level of the tree More options = better. The intended audience of HN can cope with a few more things to click. Treat us like power-users.
- dang 11y agoHN has always treated users like power users. That's part of its design. But there are other considerations, such as its minimalism and the fact that there is a single shared view of the content.
- 11y ago
- derwiki 11y agoI don't think it's fair to assume that this is spam from the AWS team. Many of us use AWS services daily and like to keep up with new offerings.
- ebbv 11y agoIf you look at the profiles of the submitters, at least one admits to being an Amazon employee. Yes, lots of us are interested in AWS (I am too), but that doesn't mean each separate announcement should be its own post. And I don't think the nearly uniform submissions we see would have happened organically.
- tedunangst 11y agoWelcome to the future, where it is now required that you organize your website to conform with the HN submission process.