I've got a few old PCI cards around somewhere. I should pull one of them out and give them a try at this.

When I migrated emails last time, I setup my old email to automatically forward to the new email. Then on my new email, I setup an automatic label for any email that was addressed to the old address. Every week or two I'd review what was sent to it and either update the email address used or unsubscribe. Eventually it got to a level where I wasn't getting much at the old email anymore and finally deleted it.

Ah, so it isn't just me. I had noticed this myself recently.

I believe Steve has said that he hates the title/thumbnails too. But Google's algorithms heavily incentives them, so he reluctantly uses them while maintaining the good quality content.

You technically could make cheese without murdering a cow but you won't find any made that way. Cows only produce milk for their young. To make milk they need to be repeatedly impregnated over and over again. Lifespan of a cow can be 20 years, though they are usually killed after about 5 as their milk output drops. Half of the cows they give birth to will be male and almost all killed as they don't produce milk. Some of the females may be killed too as you'll end up with more cows than you have room for it you keep them all.

As for a human child, drinking human breast milk is considered vegan as long as it was given consensually. If you kidnap someone and tie them up in your basement then it wouldn't be.

I've never worked directly with FCM, but that's my understanding of the issue. I don't know about WhatsApp. But it may do the same thing as Signal where the notification is just a wake up call and then the app connects directly to the WhatsApp servers to get the actual message.

The issue lies with Google's FCM (Firebase Cloud Messaging) system, so it's not something GrapheneOS can really fix. As far as I know FCM doesn't offer a way to encrypt notification content. Some apps like Signal work around this by instead of sending the message content, they send a little "wake up" notification. This tells Signal on your phone to wake up and it goes and retrieves the new message.

If you don't install Google Play Services, you won't be impacted. But you'll also not get notifications for most applications. There is an alternative push notification system called UnifiedPush which allows you to choose any server to handle your notifications (and even self host it). But it does require both the service and the app to support it, so it's not very wide spread yet.

I swapped to it at the start of the year. I've been really enjoying it so far. I'm down to a single app which requires Google Play Services installed. As it's only one app I've created a second profile specifically for it and only have Google services installed in that one. I've disallowed it running in the background too, so my phone is never running the services outside the brief times I need to use the app.

Losing contactless payments was a minor inconvenience, but I picked up one of the cases which can fit a couple of cards inside as an alternative.

That's not entirely true. It's only very recently that browsers have started using a new system called Encrypted Client Hello which hides the domain of the request. Prior to this all requests needed too have the Host field unencrypted so the receiving server knows which certified to respond with. I imagine there's still quite a few servers which don't support the new setup still.

This feels like a weaker version of GRC's Off The Grid system. https://www.grc.com/offthegrid.htm

It doesn't require you to remember something different per website. It's designed so that you can turn any site name (E.g. Amazon) into a secure password which is unique to you. If you really need a completely offline solution, I don't think it gets too much better than that.

1. We get paid $70 per weekday and $105 per weekend. I think it's $140 for public holidays.
2. Eh, it can be a bit annoying at times. It's pretty easy to swap with people as needed. I believe we're allowed to opt out of it too, some of the other devs have. Since we've started it we've tuned our monitoring scripts that false alarms are pretty rare.
3. Any time spent on incidents is rounded up to 15m. Which can make it feel quite unworth it if you get an alert in the middle of the night. Unsurprisingly since they reduced down from an hour it's taken at least 16m to investigate any alert.
4. We've got a decent number of people on rotation that I'm only on call about three weeks a year.
5. Australia

I second this. Especially useful as you could be following an exact or similarly named community and not notice it's on a different instance.