otpauth VS twirp

will generate a PNG file for each account, name after the account name and site name, and containing the QR code for the account.

Going forward, save those PNGs somewhere secure (I use an encrypted tar file). Any new accounts you set up save the QR codes for those as PNGs and add them to your collection. If you keep that collection up to date you will be able to readily handle any device updates or replacements readily or adding new TOTP apps.

[1] https://github.com/dim13/otpauth

afterwards you can use https://github.com/dim13/otpauth to convert the GAUTH code to plaintext

Open google authenticator, export accounts, screenshot QR code, decode with cyberchef, decode otpauth-migration link with https://github.com/dim13/otpauth

Scan the code with something else and pass the string inside to a tool like this in order to get the individual tokens/codes: https://github.com/dim13/otpauth

latest google authenticator has an export option. save the url or QR code and you will be able to load it in the next phone (or use a tool such as https://github.com/dim13/otpauth / https://github.com/digitalduke/otpauth-migration-decoder to decode the keys/timers and load in TOTP inside keypassx etc')

The code on this page is a standard otpauth string.

Not tested yet but this tool should allow you to create scanable QR codes for other auth apps as far as I understand. https://github.com/dim13/otpauth

The next time I want to build an API, I will probably make use of https://github.com/twitchtv/twirp. I like working with Protobuf and having strongly-typed and well-defined messages, but gRPC is way, way too much. It's obviously a Google product, built for what Google needs.

Use Protobuf for messages, but just use HTTP for transport.

- Twirp (Twitch light version of gRPC, with optional JSON encoding, HTTP1 support and without streaming) - https://github.com/twitchtv/twirp

There is another: twirp

And addition to what was mentioned there are also webrpc and twirp.

If you find one, you maybe also interested in twirp.

Twitch has a great framework for it https://twitchtv.github.io/twirp/docs/intro.html

We have better experience with https://goa.design/ than with https://github.com/twitchtv/twirp

Take a look at Twirp (https://github.com/twitchtv/twirp) open sourced by TwitchTv. It's a lot lighter weight than gRPC. It does use Protobufs but addresses some of the concerns you mentioned, such as being able to test with JSON payloads, works over HTTP 1.1 and HTTP/2, good client libraries, and doesn't require a proxy.

They address your concerns in more detail in the Twirp release announcement (2018) - https://blog.twitch.tv/en/2018/01/16/twirp-a-sweet-new-rpc-f...