4 ms·
> so it's very hard to write selectors against This sounds perfectly matched for an on-device LLM?
by JumpCrisscross 3mo ago
> so it's very hard to write selectors against
This sounds perfectly matched for an on-device LLM?
- pjc50 3mo agoThe power cost of doing this widely would be staggering, surely?
- toomuchtodo 3mo agoApple Intelligence? I mean, you're only processing for the time your "AI|browser|agent" is acting as a firewall between you and Meta. Cache locally after processing and filtering. Use alongside the accessibility API. LLMs can, in many cases, reliably solve CAPTCHAs. I find it difficult to imagine they cannot defeat Meta ad blocking countermeasures. EFF: Adversarial Interoperability - https://www.eff.org/deeplinks/2019/10/adversarial-interoperability https://www.eff.org/deeplinks/2019/10/adversarial-interopera...
- mkeedlinger 3mo agoDepending on the model, I’m guessing it’s dwarfed by just about any electron app
- Terretta 3mo agoWorth a white paper to see which costs less energy, using Apple's built in LLM, or downloading and displaying all the FB ads using radio, playback, and screen animation energy.
- StableAlkyne 3mo agoLocal models are not the same as the giant ones in data centers. They're in about the about the same ballpark as running a AAA game on max settings. Sure, it's more computationally-expensive than running an HTML selection, but it's also not "staggering" by any reasonable stretch.
- rmwaite 3mo agoI think “staggering” is a pretty accurate way of putting it if blocking ads is in the same ballpark as running a AAA game on max settings.
- StableAlkyne 3mo agoIf the computational requirement is within the realm of another normal day to day task, and if it cannot generally achieved with another cheaper approach, it would be contradictory to say it is staggering. I would agree if this was an easily solvable problem with classical approaches. Clearly it is not, since even uBlock is giving up. At any rate, "staggering" is relative. White-labeled web browsers becoming the most common GUI engine would have made an engineer's eyes water 20 years ago.
- frandroid 3mo agoBlocking ads should not make my fans spin at full blast.
- StableAlkyne 3mo agoYeah, it's pretty awful that Facebook has made it such a demanding task.
- ASalazarMX 3mo ago"Honey, I want to buy a gamer PC. This one is too slow to block Facebook ads."
- NL807 3mo agoThe giant ones in data centers are models that broadly encompass a variety of data for general purpose applications. You can certainly train models specifically for processing DOM content, making them smaller and more efficient.
- Gormo 3mo agoEven the data-center-grade models are less intensive than people think. We recently installed a heavy-duty AI server (Gaudi2 cluster with 768GB VRAM) to run larger models up to 400B parameters on, and at full load, its power draw is about equivalent to a consumer stove or clothes dryer. If you're running thousands of those concentrated into a single data center, your aggregate power draw is going to be huge, but a single server is entirely reasonable for a small business, or even a home user, to operate.
- Gormo 3mo agoNot really, no. LLMs get more computationally efficient and hardware gets more power efficient with each passing day. We're already at the point where reasonably competent models can be run a laptop GPU off of battery power. NPUs are even more power efficient, (though a bit slower).
- deleted 3mo ago[deleted]
- aembleton 3mo agoIt keeps changing all of the time, so it might be easier to have Facebook load up in a headless browser, that takes a screenshot and sends it to an LLM and uses that to convert into a standard JSON document that can be rendered nicely. Or something like that.