WebP is basically the format used to store i-frames in WebM/VPx videos. Google acquired on2 technologies for this tech many years ago, and it was to stop W3C from standardising a patent encumbered codec like H.265. These were all well intentioned.

WebP / WebM has all been superceded by AV1 / AVIF anyway. It never really took off, and it’s too late to start now.

If it leaves your device, you cannot control it.

i could add more detail, but it just raises further questions.

• The payroll officer was emailed from an aol.com address, not the company email domain.

• The bank account was changed to a branch in another state, several thousand kilometres away.

• My office was physically next to the payroll officer. Despite sitting 2 metres away, I was not contacted in-person at any stage.

• At least two staff members oversaw this.

• They just wrote off the money and paid me for the month again.

This triggered a policy change. Bank account updates had to be confirmed in-person after that.

It doesn’t take much. I once put my name, job title and employer on LinkedIn. That was enough for someone to email my payroll officer and convince them to change my paycheck to a different bank account. I had no idea until my pay was missed.

My payroll officer was a dumbfuck, but that’s all it took.

A bank card is far more practical than a second phone. Even if Google Pay did work on GrapheneOS, I would not use it. It looks like a privacy nightmare.

I have configured my home router to redirect all plaintext DNS traffic through it. I did it because Chromecasts try to sidestep DNS and go straight to Google.

While doing that was a couple of lines of nftables config, blocking DoH would require an actively maintained list. Even then, it would be trivial to host your own by renting some server space.

This reminds me of something I worked on at my last job. I made software to detect plumes of dust pollution from a mining site blowing onto a nearby school and town. The EPA issued fines if they detected too much dust over the town. This system could catch it early for quick intervention.

After it was deployed, I got a glimpse of their production config. They hadn’t configured the alarms for early intervention. They had configured them so that they could get as close as possible to their allocated limit before they intervened at all. Because, ya know, spraying water on stockpiles of ore is expensive.

Fucking mining companies, man.

My bank apps all work fine. Just keep your physical bank cards on you because Google Wallet won’t work with credit cards, NFC or transport passes. Your gig tickets and membership cards will load fine though.

You probably don’t want Google rummaging through your purchase history anyway. I certainly don’t miss it.

Not really. If they use TLS / HTTPS then you won’t see a damn thing.

My car is built in 2003 and I don’t think I’m ever moving it on.

It peaked in 2005 before the driver inputs got overrides and and speed outputs started lying to you.

I couldn’t even imagine a car connected to the internet.