zlacker

[parent] [thread] 23 comments
1. notato+(OP)[view] [source] 2025-12-05 02:58:28
I understand that sometimes the HN titles get edited to be less descriptive and more generic in order to match the actual article title.

What’s the logic with changing the title here from the actual article title it was originally submitted with “AV1 — Now Powering 30% of Netflix Streaming” to the generic and not at all representative title it currently has “AV1: a modern open codec”? That is neither the article title nor representative of the article content.

replies(6): >>7e+A >>Verifi+62 >>pants2+U3 >>cortes+Z8 >>wltr+5d >>tomhow+Ah
2. 7e+A[view] [source] 2025-12-05 03:05:02
>>notato+(OP)
Also, it’s not the whole picture. AV1 is open because it didn’t have the good stuff (newly patented things) and as such I also wouldn’t say it’s the most modern.
replies(2): >>bawolf+h1 >>adgjls+b7
◧◩
3. bawolf+h1[view] [source] [discussion] 2025-12-05 03:11:22
>>7e+A
Just because something is patented doesn't necessarily mean its good. I think head to head comparisons matter more. (Admittedly i dont know how av1 holds up)
replies(1): >>parl_m+s3
4. Verifi+62[view] [source] 2025-12-05 03:23:09
>>notato+(OP)
Amen. The mania for obscurity in titles here is infuriating. This one is actually replete with information compared to many you see on the front page.
replies(2): >>CyberD+tc >>tomhow+Wx
◧◩◪
5. parl_m+s3[view] [source] [discussion] 2025-12-05 03:36:52
>>bawolf+h1
Yes, but in this case, it does.

AV1 is good enough that the cost of not licensing might outweigh the cost of higher bandwidth. And it sounds like Netflix agrees with that.

replies(1): >>Sunspa+BA4
6. pants2+U3[view] [source] 2025-12-05 03:42:30
>>notato+(OP)
Though in the original title AV1 could be anything if you don't know it's a codec. How about:

"AV1 open video codec now powers 30% of Netflix viewing, adds HDR10+ and film grain synthesis"

replies(3): >>nerdsn+r6 >>efitz+6a >>lII1lI+Me
◧◩
7. nerdsn+r6[view] [source] [discussion] 2025-12-05 04:17:04
>>pants2+U3
AV1 is fine as-is. Plenty of technical titles on HN would need to be googled if you didn't know it. Even in yours, HDR10+ "could be anything if you don't know it". Play this game if you want, but it's unwindable. The only people who care about AV1 already know what it is.
replies(1): >>pants2+x8
◧◩
8. adgjls+b7[view] [source] [discussion] 2025-12-05 04:26:49
>>7e+A
AV1 has plenty of good stuff. AOM (the agency that developed AV1) has a patent pool https://www.stout.com/en/insights/article/sj17-the-alliance-... comprising of video hardware/software patents from Netflix, Google, Nvidia, Arm, Intel, Microsoft, Amazon and a bunch of other companies. AV1 has a bunch of patents covering it, but also has a guarantee that you're allowed to use those patents as you see fit (as long as you don't sue AOM members for violating media patents).

AV1 definitely is missing some techniques patented by h264 and h265, but AV2 is coming around now that all the h264 innovations are patent free (and now that there's been another decade of research into new cutting edge techniques for it).

◧◩◪
9. pants2+x8[view] [source] [discussion] 2025-12-05 04:45:32
>>nerdsn+r6
Well, I'm interested in AV1 as a videographer but hadn't heard of it before. Without 'codec' in the title I would have thought it was networking related.

Re: HDR - not the same thing. HDR has been around for decades and every TV in every electronics store blasts you with HDR10 demos. It's well known. AV1 is extremely niche and deserves 2 words to describe it.

replies(3): >>cyphar+U9 >>edoceo+nc >>notato+aW2
10. cortes+Z8[view] [source] 2025-12-05 04:51:22
>>notato+(OP)
It is usually Dang using his judgment.
replies(1): >>big-an+De
◧◩◪◨
11. cyphar+U9[view] [source] [discussion] 2025-12-05 05:04:06
>>pants2+x8
AV1 has been around for a decade (well, it was released 7 years ago but the Alliance for Open Media was formed a decade ago).

It's fine that you haven't heard of it before (you're one of today's lucky 10,000!) but it really isn't that niche. YouTube and Netflix (from TFA) also started switching to AV1 several years ago, so I would expect it to have similar name recognition to VP9 or WebM at this point. My only interaction with video codecs is having to futz around with ffmpeg to get stuff to play on my TV, and I heard about AV1 a year or two before it was published.

◧◩
12. efitz+6a[view] [source] [discussion] 2025-12-05 05:06:05
>>pants2+U3
The article barely mentioned “open”, and certainly gave no insight as to what “open” actually means wrt AV1.
◧◩◪◨
13. edoceo+nc[view] [source] [discussion] 2025-12-05 05:41:40
>>pants2+x8
I'm old (50) and have heard AV1 before. My modern TV didn't say HDR or HDR10 (it did say 4k). Agree that AV1 should include "codec".

One word, or acronym, just isn't enough to describe anything on this modern world.

◧◩
14. CyberD+tc[view] [source] [discussion] 2025-12-05 05:43:39
>>Verifi+62
hacker news loves low information click bait titles. The shorter and more vague the better.
15. wltr+5d[view] [source] 2025-12-05 05:51:29
>>notato+(OP)
For me that’s a FU moment that reminds me ‘TF am I doing here?’ I genuinely see this resource as a censoring plus advertising (both for YC, obviously) platform, where there are generic things, but also things someone doesn’t want you to read or know. The titles are constantly being changed to gibberish like right here, the adequate comments or posts are being dead, yet the absolutely irrelevant or offensive things, can stay not touched. Etc.
◧◩
16. big-an+De[view] [source] [discussion] 2025-12-05 06:11:11
>>cortes+Z8
I really like moderation on HN in general, but honestly this inconsistent policy of editorializing titles is bad. There were plenty of times where submitter editorialized titles (e.g GitHub code dumps of some project) were changed back to useless and vague (without context) original titles.

And now HN administration tend to editorialize in their own way.

◧◩
17. lII1lI+Me[view] [source] [discussion] 2025-12-05 06:13:03
>>pants2+U3
> Though in the original title AV1 could be anything if you don't know it's a codec.

I'm not trying to be elitist, but this is "Hacker News", not CNN or BBC. It should be safe to assume some level of computer literacy.

replies(1): >>averag+sg
◧◩◪
18. averag+sg[view] [source] [discussion] 2025-12-05 06:27:28
>>lII1lI+Me
Knowledge of all available codecs is certainly not the same tier as basic computer literacy. I agree it doesn't need to be dumbed down to the general user, but we also shouldn't assume everyone here know every technical abbreviation.
19. tomhow+Ah[view] [source] 2025-12-05 06:44:00
>>notato+(OP)
OK guys, my screwup.

We generally try to remove numbers from titles, because numbers tend to make a title more baity than it would otherwise be, and quite often (e.g., when reporting benchmark test results) a number is cherry-picked or dialed up for maximum baitiness. In this case, the number isn't exaggerated, but any number tends to grab the eye more than words, so it's just our convention to remove number-based titles where we can.

The thing with this title is that the number isn't primarily what the article is about, and in fact it under-sells what the article really is, which is a quite-interesting narrative of Netflix's journey from H.264/AVC, to the initial adoption of AV1 on Android in 2020, to where it is now: 30% adoption across the board.

When we assess that an article's original title is baity or misleading, we try to find a subtitle or a verbatim sentence in the article that is sufficiently representative of the content.

The title I chose is a subtitle, but I didn't take enough care to ensure it was adequately representative. I've now chosen a different subtitle which I do think is the most accurate representation of what the whole article is about.

◧◩
20. tomhow+Wx[view] [source] [discussion] 2025-12-05 09:06:37
>>Verifi+62
If there really was a “mania for obscurity in titles” we’d see a lot more complaints than we do.

Our title policy is pretty simple and attuned for maximum respect to the post’s author/publisher and the HN audience.

We primarily just want to retain the title that was chosen by the author/publisher, because it’s their work and they are entitled to have such an important part of their work preserved.

The only caveat is that if the title is baity or misleading, we’ll edit it, but only enough that it’s no longer baity or misleading. That’s because clickbait and misleading titles are disrespectful to the audience.

Any time you see a title that doesn’t conform to these principles, you’re welcome to email us and ask us to review it. Several helpful HN users do this routinely.

replies(1): >>Verifi+195
◧◩◪◨
21. notato+aW2[view] [source] [discussion] 2025-12-05 21:35:26
>>pants2+x8
this is the reason articles exist, and contain more information than the headline does.

you might not know what AV1 is, and that's fine, but the headline doesn't need to contain all the background information it is possible to know about a topic. if you need clarification, click the link.

◧◩◪◨
22. Sunspa+BA4[view] [source] [discussion] 2025-12-06 15:27:12
>>parl_m+s3
I don't like newer codecs like AV1. I find them blurrier. Perhaps the bitrate is too low, but they do seem blurrier compared to h264. Even VP09 has often seemed better.

h264 is a very good codec.

◧◩◪
23. Verifi+195[view] [source] [discussion] 2025-12-06 20:00:33
>>tomhow+Wx
No, because people who point out obscure titles are downvoted in most cases, and eventually shadow-banned. So those voices are silenced here.

"We primarily just want to retain the title that was chosen by the author/publisher, because it’s their work and they are entitled to have such an important part of their work preserved."

Nobody said the title had to be deleted. But when it doesn't convey WHAT the "thing" is, it needs augmentation. Currently on page 4 there's an example that not only conveys nothing, but DOESN'T respect the actual title you find on the linked page. The HN post is entitled merely "tunni.gg".

But if you click on that, you get to a page that says, "Expose localhost to the internet." But the poster couldn't be bothered to put that important and interesting information in the title. Instead, the title is worthless.

You see plenty of similarly and intentionally obscure titles on HN daily. Try calling them out and see what happens.

replies(1): >>tomhow+VN5
◧◩◪◨
24. tomhow+VN5[view] [source] [discussion] 2025-12-07 02:45:18
>>Verifi+195
I don't know where you get the idea that the moderators or the community are such unreasonable tyrants about this!

> people who point out obscure titles are downvoted in most cases, and eventually shadow-banned

Nothing like this happens! Nobody gets banned for pointing out anything about titles. People only get banned ("shadow" or otherwise) for serial abuse or trolling (and only after multiple warnings), or for spamming. Comments only get downvoted if more people disagree than agree with the title suggestion or the way it's suggested. It's no big deal. It's how opinions are expressed and debated on HN.

> The HN post is entitled merely "tunni.gg".

That's Tunnl.gg [1], and it would have been fine for the page's heading to be added to the HN title (that routinely happens when software projects on Github are submitted). It's also not terrible for just the project name to be there, because the name of the project (a variant of the word "Tunnel") hints at what it is. But we're not dogmatic about it, and anybody could have emailed us (hn@ycombinator.com) to suggest a better title we would have given it due consideration and replied appreciatively. We do that multiple times each day.

> You see plenty of similarly and intentionally obscure titles on HN daily. Try calling them out and see what happens.

“Intentionally obscure” isn't the right framing. Maybe we don't always want to clobber people over the head with obviousness. The joy of surprising discovery is an important part of the HN experience.

But the key principles – (a) respect the original work of the author/publisher and (b) don't mislead or disrespect the HN audience with clickbait or false information – have proven to be the most stable and defensible over time. There's still plenty of room for discernment in the way those principles are applied on a case-by-case basis.

[1] >>46145902

[go to top]