Can someone shed some light on an inconsistency with the otpauth/totp protocol relative to Rift

From what I understand steam uses the same TOTP as everyone else, they just use some code to convert some of the numbers into corresponding letters.

Either way, nothing can be done without intervention on your end, or valve's - at least without changing to another password manager.

as for rift, they are all numbers so no idea whats going on or why i cant get that one functioning properly beyond the first number cycle or two.

can you tell me if digits in totp are always read backwards? aka if I had a code that was 12345678 and I had digits=5 in my string would it be picked up as 12345 or 34567? trying to ascertain whether or not the behavior im seeing is due to 1password, due to the way the protocol works, or due to something else altogether (trion/glyph's implementation)