Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I get that extensions are scary & dangerous, but it's absurd to me that dynamic code is now verboten.

Your header issue doesn't totally click with me. Because it seems like a separate issue. I agree you should have the day over your user agent! But an extension executing remote code doesn't seem to be a factor.

Remote code means that we can't create extensions with pluggable modularity. We can't build an Yahoo Pipes like thing in the browser. We can't have a repo of cool features that users load into their extensions. Everything has to be made in advance.

So much of the awesomeness of the web is that it's live systems, love code, not dead systems dead code. It's a flexible system. Demanding that extensions have only fixed function dead code eliminates so many possibilities, makes the extension so many million degrees less capable and powerful than the web they are supposed to bestow agency into. (Forgetting the other influences but the alive vs dead systems showed up 2yr ago in Stop writing dead programs, https://jackrusher.com/strange-loop-2022/ https://news.ycombinator.com/item?id=33270235 )

Its absolutely fucking rip roaringly bullshit that remote and dynamic code is prohibited in extensions. I'm fine with it as a default, as requiring some special setting or mode to be flipped, warnings to be clicked through. But it's just such horrible thing to main user agency so blankety, to demand agency be channeled through dead code.



Header issue is essential for things like Greasemonkey/Tempermonkey. Cant run own scripts without overriding CSP headers.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: