ajayyy

The tokens are "generated" on the client, and the server just gives the client enough information to make that locally generated token become "valid", without being able to link that token to a specific validation attempt

youtube hasn't touched their anti-adblock code since june

uBlock Origin already blocks them by default at the request level, no need to hide the actual HTML element

DMA requires that the interoperability be at the same level of encryption than normal chats. In whatsapp's case, that means all interoperability must be E2E

It's not an open federation

There is a whitelisted set of apps in the OS. Samsung's messenger also is allowed on Samsung devices. They talked about opening the API many years ago and then suddenly stopped talking about it.

For most people, Google Messenger app now uses Google's RCS gateway anyway, so the carrier does not need to support RCS.

I do not know of anyone trying to get carrier-based RCS working with a non Google app using a custom rom with a different whitelisted set of apps, but it sounds to like maybe that would be possible

uBlock Origin filter type called has-text

On Android, I can create a PWA that runs in Firefox and it works great. Apple could easily implement the same thing

Kiwi has historically faked the version number to prevent websites from telling you to update your browser. I would assume that number is not legitimate.

The name origin was used because google took it down for using the name ublock after the GitHub repo transfer

They encourage people to wait to buy their product only until they aren't able to repair their current one.

Mozilla reviewers do very detailed reviews. Unlike Chrome, they sometimes do manual reviews, looking for potential XSS or similar problems, and will let you know the exact line causing it. The Chrome web store is almost unmoderated though.

One cool side-effect is that existing mastodon bots (like remind bots) work seamlessly. Just ping them as normal and they will reply.