I'm not sure why the article picks these 3 options as if that's it.
An RPC API can happily exist over plain old HTTP/1 (no protobuf required) and it also doesn't mention the primary benefit of RPC over REST/RESTish (IMO) - and that's the ability to stack multiple RPC calls into a single request.
De-anonymization would take monitoring over a period of time, but it could definitely work. Take this scenario for example: a person of interest is in the area of New York on Jan 1. On Jan 4 they travel to the UK. On Jan 7 they travel to Germany. On Jan 21 they travel back to the US.
The list of suspects would be fairly small when US officials cross-check individuals that travelled US-UK on Jan 4 and Germany-US on Jan 21.
For the previous 20 years I had no real routine other than wake>commute>work or wake>work if wfh, but over the last 2 years I've been more focused on my health. Every weekday I get up around 06:00 and am at the pool by 06:40. I swim 1500m then have a 15min sauna and 4min cold plunge. Normally I'm back at my desk by around 08:20. I drink 1L of water with electrolytes while at the pool and then have a light breakfast and espresso when I get home.
I'm in better shape than I was throughout my 30s, have more muscle, better posture and generally feel more energetic and alert through the day.
While at the pool I listen to Audible books (wearing Shokz), so get through a new book every couple of weeks also.
An RPC API can happily exist over plain old HTTP/1 (no protobuf required) and it also doesn't mention the primary benefit of RPC over REST/RESTish (IMO) - and that's the ability to stack multiple RPC calls into a single request.