this post was submitted on 24 Nov 2023
235 points (98.4% liked)

Technology

59207 readers
2845 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Chrome pushes forward with plans to limit ad blockers in the future::Google has set a date for the introduction of Manifest V3 which will hurt the capabilities of many ad blockers.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 11 months ago (1 children)

I’m just a tech hobbyist and not a network engineer but my general understanding is that even if chrome is “updated” so as blockers won’t work as before, blocking at the DNS level should still work, right? Assuming that they still use separate ad servers.

[–] [email protected] 2 points 11 months ago

So, dns blocking will always block the requests to things on the block list, which includes ads… however I’ve noticed that a many sites are now using js to detect images that don’t load before calling the “full the body with text” api call. Originally this would just do some fancy css hiding of the content so SEO scraping would still work (and oh can just use reader view), but now I’ve seen them pull the first paragraph and then, if the images loaded (or an additional call to a tracking pixel for instance) it would also call to their API to get the remainder of the content.

The other way it’ll fail is if they use the same server/dns hostname for content as they do for ads.