5 ms·
The submitted title was "Apple put their weight behind an open HDR standard called “ISO/TS 22028-5”" but that broke the HN guideline against editorializing: "Pl
by dang 3y ago
The submitted title was "Apple put their weight behind an open HDR standard called “ISO/TS 22028-5”" but that broke the HN guideline against editorializing: "Please use the original title, unless it is misleading or linkbait; don't editorialize." - https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
If you want to say what you think is important about an article, that's fine, but do it by adding a comment to the thread. Then your view will be on a level playing field with everyone else's: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=%22level%20playing%20field%22%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...
- wilg 3y agoI simply wouldn’t have looked at this with the new title. The original title was better. The new title deletes the interesting insight about the format they are using. Now it just looks like a video about general HDR workflow and I don’t know why it’s been posted. The newsworthy element may not be the entire link but some element on the page, especially for longer form content.
- altairprime 3y agoSubmitting a blog post about this would have been much more effective than linking an Apple developer video with a modified title. (And, then I wouldn’t have had to add quotes and context as a comment below.)
- wilg 3y agoArguably, everything worked out fine until the title changed.
- pvg 3y agoIt didn't - one of the main reasons you can't make up your own title is that it acts as a kind of mega-comment over everyone else's comments. If you want to just comment, write a regular comment. If you want your own title with your own commentary, write your own commentary and submit it to HN with your title. What you can't do is use someone else's stuff to make your commentary more important.
- Dylan16807 3y agoWould it have been more effective? HN hates blogposts that reiterate a piece of news, and since the blog post would be only a paragraph long I would expect it to be replaced with the source video as soon as a mod sees it.
- pvg 3y agoA huge chunk of HN stuff is blog posts. Plus if there's nothing to say about the thing than isn't more than a messageboard comment then there's not much reason it shouldn't just be a messageboard comment. It's definitely less 'effective' at dominating the discussion with a single comment but that's more or less the point.
- Dylan16807 3y agoA huge chunk of HN stuff is substantial blog posts talking about their own things. Things get called blogspam all the time, and a three sentence post linking to a video will definitely get called blogspam. And the goal isn't to "dominate the discussion". Nobody else wants to submit this video. Nobody is being shouted over. The goal is to start a discussion about a specific thing, and making a comment on an otherwise boring link is not actually very good at starting a discussion.
- pvg 3y agoThe thing has to be interesting/substantial/big enough to carry a discussion. That's pretty much the functional difference between a comment and an HN story. 'Every comment should be allowed to also be a story' doesn't seem like a practical way to have a site that distinguishes between stories and comments.
- Dylan16807 3y agoBig enough to carry a discussion doesn't mean you have an entire blog post ready to write all by yourself. In general my complaint is that it's hard to link to a specific section or piece of information inside a larger article. So letting comments become stories willy-nilly is not my suggestion. This is about having an external story, but no good way to point at it. And a submission like this can't just be a comment because there's no story for it to be a comment on. The video would not otherwise have been submitted. And yes the option of "submission plus comment" exists but again that's a bad way to start a discussion when the submission has nothing obviously interesting about it. And it makes the experience even worse for someone that tries to read/watch the entire submission before looking at the comments, when most of the submission is pretty boring and the submitter only wanted to submit one portion.
- xd1936 3y agoAgreed. Original title was not clickbait or misleading in any way.
- pvg 3y ago"original title" means the original title of the article, not the title the submitter originally made up.
- tormeh 3y agoThat's the original title of the submission, though.
- pvg 3y agoYes but the guideline about 'original title' doesn't mean that. That's the editorialized title, not the original title of the thing. What you're suggesting is misconstruing the guideline to mean the opposite of what it actually means.
- dang 3y agoA good place to explain why an article is being posted is by adding a comment to the thread.
- wilg 3y agoNo it isn’t, because you can’t see that from the main page so there’s no reason to look at the link or comments if you don’t know what is interesting about the post. This rule makes sense for editorialized titles, but not as much for trying to point to news that is buried in some larger page that does not have a useful title.
- ShamelessC 3y agoPutting a notice either like this or as an indicator on the submission would go a long way towards reducing (my) frustration with moderation’s title edits.
- dang 3y agoThe problem with that is that there are many such notices and indicators we might put up about many things. If we did all of them, the site would get messier and more annoying and nannyish. It seems generally better (or at least in keeping with HN's 'DNA') to err on the side of keeping things minimal and trust users to figure them out.
- ShamelessC 3y agoThat’s fair. I was thinking something in the realm of a bolded asterisk next to the title. Or something similarly subtle with an explanation in the rules perhaps. Obviously there are users who would meta comment about this each time it happened (as is happening currently), so I can understand the reluctance.
- janandonly 3y agoHi Dang, OP here. I am aware of this guideline. The problem is that the original title is so... meaningless? that I decided to give the site a title that explains why it's interesting. In no way do I disrespect the idea behind this rule, I can see how it would lead to clickbait titles and such. I also didn't want to write a blogpost with a better title that simply refers to this resource at Apple's. For full transparency, I came across this site because this interesting blogpost referred to it: https://www.lux.camera/halide-for-ios-17/ https://www.lux.camera/halide-for-ios-17/ The reference is in this sentence: > Apple wants to avoid a similar fate in still photography, so this year they put their weight behind an open standard called "ISO HDR." Ok, technically it's ISO/TS 22028-5, which doesn't quite roll off the tongue. The important thing is that with iOS 17, Halide captures HDR photos. In fact, it has for years!
- dang 3y agoThat all seems reasonable to me. It's a tradeoff. One thing that frequently happens is that an edited title helps an article make the front page, and then we revert it after that. I think this can be a good balance sometimes. (If it were a bad article for HN, we wouldn't do that—rather we would downweight the thread.) I don't want to say "it's ok to break the rule in such a case for such a purpose" because one can't say that with any precision—it will just be heard as "ignore the rule and do whatever you want".