Oh, okay. I found the option. Just didn’t know that was a thing.

That’s not anti-echohamber. That’s the algorithm reinforcing the anti-trans propaganda that drives clicks and views on most platforms. Controversy is sensational, and anger provokes responses.

Replace “woman” with “Black” in this rant and it sounds just like someone trying to make reparations look bad by strawmanning its supporters.

I agree that neoliberal capitalism has (largely successfully) used feminism as a way to distract from society’s real problems. But this ain’t it.

They’re not user unfriendly changes if 95% of users just don’t care.

Why are people up voting this? This is such ridiculous FUD that I can’t take it seriously.

Google chose to make MV3 neutered in comparison to MV2. They could’ve found a way to allow the capabilities required for runtime adblocking. They chose not to.

Because who is going to operate the servers?

Originally with RCS it was the carrier, but basically every carrier switched to using Jibe (by Google) for the backend.

And it sounds like Apple is going to operate their own as well.

Alternatively, this is perhaps the only way for Microsoft to pressure hardware makers to stop shipping BIOS motherboards. They won’t naturally go away unless there’s an incentive.

Nah it just makes it confusing, especially to non native English speakers

That’s the point. To many, they didn’t matter and still don’t. Which is abhorrent.

• Ublock Origin, not Ublock