It's not being intentionally buried, but the rapid drop in interest is a testament to the utter dullness of "A response to feedback on the proposed changes in Manifest V3"
"Manifest V3" is jargon, which is a big problem in HN. See Show HNs that don't really explain what is the thing being introduced.
The Response -> feedback -> proposed changes chain is verbose. The three concepts are almost a single concept (changes) wrought as present -> past -> future.
"A response to feedback on the proposed changes in Manifest V3" is a characteristically Google-internal-y [0] way to say "Update on coming changes to Chrome extension APIs".
[0]: My unscientific feeling is that a lot of engineers at Google write about projects as if the audience is other Google engineers. It's not out of malice, but it's convenient when you don't have to explain the full rationale for a change.
"Manifest V3" is jargon, which is a big problem in HN. See Show HNs that don't really explain what is the thing being introduced.
The Response -> feedback -> proposed changes chain is verbose. The three concepts are almost a single concept (changes) wrought as present -> past -> future.
"A response to feedback on the proposed changes in Manifest V3" is a characteristically Google-internal-y [0] way to say "Update on coming changes to Chrome extension APIs".
[0]: My unscientific feeling is that a lot of engineers at Google write about projects as if the audience is other Google engineers. It's not out of malice, but it's convenient when you don't have to explain the full rationale for a change.