ttj - Tom Jones

I never chose to make card payments depend on my phone, but card issuers, as elements in the shitfrastructure, all force this. I'm separated from my phone till I collect it from the place I left it, which is a flight away.  To book a flight, you have to make a payment, and to make a payment, the shitfrastructure requires you to use your phone. I almost failed to buy the ticket.  It went as follows: barclaycard options were SMS to lost phone, or to old uk number disconnected, or app which I don't use, but which would be on the lost phone, or pinsentry on app (note: pinsentry via actual pinsentry device NOT an option), failed halifax SMS to lost phone, only option, failed coutts debit SMS to lost phone, only option, failed HSBC debit SMS to lost phone, or bank app, which I don't use, but if I did it would be on the lost phone, failed Lloyds debit one option was call to landline, which worked, and I entered with DTMF in the phone a 4-digit code displayed on the computer screen...

Here's a kick up the arse to finally migrate off google services: they've made my account authentication two-factor, with the second factors inevitably being shitfrastructure elements.  There was no way to prevent it happening. Losing my phone is probably annoying.  If everything else depends on it, and thus stops working at the same I lose my phone, then it's way more annoying. The available "second steps" are: SMS to a mobile number I may not have for much longer confirming on an android device I am currently evaluating and do not want to be tied to, and can not carry in my pocket because it's so huge generating a one-time code on same android device So my access to email, calendar, contacts, documents, and a load of other stuff is now contingent on temporary shitfrastucture elements still being in place. This kind of thing must be "best practice", because everyone does it.  It must be hard to argue against a legal argument that the service provide...