I get that it took some engineering changes on the parser front, but this is so much cleaner as far as syntax goes.
5,684 karma · joined November 8, 2011
I get that it took some engineering changes on the parser front, but this is so much cleaner as far as syntax goes.
Would love to see a part 2 focusing on subgrid and the "rest of the iceberg".
It is incorrect. MV3 definition updates go through an automated fast-track process for safe rules. See the presentation[1] and Q&A[2] at the recent Ad Blocking Summit.
I wouldn't hold my breath on a correction. Ron never corrects his articles, like when he confused the Privacy Sandbox with the Topics API a couple months ago[3].
[1] https://youtu.be/Vw1eIaRuy7w?t=24745
Checking 150K rules once wouldn't be a problem, but if you have to do that for 50 network requests on every single page load, that adds up. So the hope, as I understand it, is to set a ceiling to encourage developers to keep more up-to-date lists by pruning old and outdated rules. This prevents a situation where browser performance slowly degrades.
I'd like to see a system where users opt-in to allow ad blockers to collect metrics on which rules are actually applying, and have them occasionally trim anything under 0.01% usage. Which sounds like a small number, but should capture the majority of dead or unused rules. Of course, that would require a new browser API in a declarative system.
You are likely aware of this already, but for others readers, it's important to know that placebos are still effective even when you know they are placebo. The term is "open-label placebo".
https://web.archive.org/web/20180117100018/https://abc.xyz/i...
https://web.archive.org/web/20181225060308/https://abc.xyz/i...
Of course at that point you're probably more interested in a common binary format, and should start thinking about wasm instead.
Ars seems to be confusing the topics API with the privacy sandbox as a whole. Most features are early, like client hints, while others like privacy budget haven't even been released yet.
https://imgs.xkcd.com/comics/angular_diameter_turnaround_2x....
> Refused to frame 'https://www.w3.org/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://cms.w3.org/".
If so, nice meta-commentary.
https://support.google.com/a/answer/10741897
https://security.googleblog.com/2023/06/gmail-client-side-en...
The repo's own description uses the phrase vanilla JavaScript in this way, and even mixes both meanings within a single sentence.
If the author likes the theme, I'm sure they can still use it indirectly. eg. "icecream.js: add a scoop of vanilla to your project". Or "Go nuts and sprinkle in some Reactive syntax". It's still very punnable, I assure you.
So are you saying I need to change how I log into Windows to be able to use this website / security method? I didn't really trust Windows Hello because of all the junk they bundle with Windows now. I just assumed it had some angle to it.
I'll have to do some more reading into how this works. So far this seems much more complex than a password though. If the browser is just generating a keypair and sharing the public key, you'd think that would be possible without any specialized hardware chips or USB keys.
Models are not trained during inference, are they?
Regardless, it seems like LLMs are going to have some role to play in search in the future. It's just not clear what that role is yet.
If that's not what you're saying, then you'll need to clarify.
I think this tool may be good for documents with careful typesetting and layout, but maybe not modern, interactive, responsive pages.