4 ms·
A couple other things I've noticed having to do with "promoted content": 1. uBlock origin seems to block ads in the normal web client, but not in the mobile we
by Sindisil 10y ago
A couple other things I've noticed having to do with "promoted content":
1. uBlock origin seems to block ads in the normal web client, but not in the mobile web client (in desktop FireFox as well as mobile FireFox).
2. Mobile twitter client lacks the drop-down menu where you used to be able to choose "I don't like this ad".
Now that I look at it, though, that menu on the main twitter web app doesn't have that option any more, either. You can "report this ad", which isn't quite the same.
To get to the same menu in the mobile web app, you need to tap/click the add tweet, then choose the more options icon.
The normal twitter web app has now added a "dismiss" option on mouseover.
FFS, there's no consistency of interface across the three at all!
- deleted 10y ago[deleted]
- vincentriemer 10y agoFrom what I understand, the twitter mobile web client uses react and from a quick look at the source, they're using css modules which means the class names are generated at build time. Considering that most ad blockers work by identifying ads through class names, it would explain why uBlock origin wouldn't work on the mobile site.
- Sindisil 10y agoMakes sense. Thanks.
- mintplant 10y agoThis uBlock rule should do the trick, despite the use of CSS modules: mobile.twitter.com##div:has(:scope > div[role="article"] > div[data-testid="tweet"] > div > div:last-child:nth-child(3):nth-of-type(3)) https://github.com/uBlockOrigin/uAssets/issues/351 https://github.com/uBlockOrigin/uAssets/issues/351