uBlock can already do this (I use it for hiding the Twitter "while you were away" nonsense), although I suspect that the next step is Facebook scrambling DOM classes and ids with no discernable pattern.
That's why I have been beefing up the DOM filtering code in the latest versions -- there are already sites doing this.
There is a lot of untapped potential with the new operators, I am waiting for opportunities to put them to test, and fine-tune them if needed.
If you can't filter on classes or id's, what else? Dom element ordering? Image size properties? Structure of ad text?
> That's why I have been beefing up the DOM filtering code
Isn't it all done through CSS selectors? Could you share more?
How about leveraging other heuristics such as HTTP headers (response cookies for starters) or timing information?
But you still have to identify features and use an algorithm that basically goes "users identify images with features A, B, and C as ads, and they identify images with features X, Y, and Z as not ads, so put positive weights on A, B, and C and negative weights on X, Y, and Z, and block anything with a negative enough score".
Which is apparently a usage pattern nobody at twitter gets.
I'd love it if the infinite scrolling shit went away and I could look at tweets by last hour, last 12 hours, last 24 hours, etc, and then paginate by day after that.
You're not going to please everyone. Even people who will like it a month down the line will hate it when you first roll out the change. And we should you have to support (|feature|!) different websites?
Like or is being exploited based on genetical brain responses to like because of the result of the "quest for new information" ?
This behaviour is psychologically engineered to trigger more dopamine fueled hits and with it fueling site engagement.
I hope you don't like music, movies, amusement park rides, love, etc., because I have some bad news for you.