The twitter ones are really hard, because I think they're interstitial with the actual twitter content. I haven't used the platform in ages, either, but I think they come form the same domain as the rest of the content.
To see if that's the case, you could close everything, use the app and wait until you get an ad, then check the logs of your ad blocker to see what domains sre being hit. Pick a suspicious one, block it, and try to load the content. You'll break something almost guaranteed, but it's easy to just unblock the domain afterwards
I'm not too sure how adguard works, I've never tried it, but I think it worked on the same concept as pihole etc, by blocking domains. As long as there's a log file, you should be able to fiddle and see if you can block just that ad domain.
Someone with more direct experience will likely have more to say on the matter, of course. This is just the technique I used to block ads on my city's parking app - which I have to put up with AFTER I pay for parking! Heh
Looks like you may be right. Most requests came from api.twitter.com (and variations of that, such as api-33-0-0.twitter.com). The only different one was from global.albtls.t.co, and it was already blocked thanks to Peter Lowe's Blocklist.
The twitter ones are really hard, because I think they're interstitial with the actual twitter content. I haven't used the platform in ages, either, but I think they come form the same domain as the rest of the content.
To see if that's the case, you could close everything, use the app and wait until you get an ad, then check the logs of your ad blocker to see what domains sre being hit. Pick a suspicious one, block it, and try to load the content. You'll break something almost guaranteed, but it's easy to just unblock the domain afterwards
I'm not too sure how adguard works, I've never tried it, but I think it worked on the same concept as pihole etc, by blocking domains. As long as there's a log file, you should be able to fiddle and see if you can block just that ad domain.
Someone with more direct experience will likely have more to say on the matter, of course. This is just the technique I used to block ads on my city's parking app - which I have to put up with AFTER I pay for parking! Heh
Looks like you may be right. Most requests came from api.twitter.com (and variations of that, such as api-33-0-0.twitter.com). The only different one was from global.albtls.t.co, and it was already blocked thanks to Peter Lowe's Blocklist.