>>17697501

That's my understanding of it. I think you have to link the different devices to the authenticator in order to retrieve codes on that device. Not a tech wizard at all, but I think it's just giving the assigned device an ability to receive a password to post. This prevents spam bot from using multiple devices to mass post using automated systems.

>>17697510

I deleted the extension, since I thought it was interfereing with the bluestacks android simulator. I haven't had a chance to try it yet, but prefer to use brave browser which isn't an option w/the browser extension. So since the android simulator is working for me now, will prob switch to brave, I'm on chrome now, and will just use the bluestacks simulator. But maybe this anon knows about this for instruction related to the browser >>17697442, >>17697446

>>17697510

I assume you set up the extension w/the key code and it's save in the setup. But you also leave the key code in your reply box up top. Save the key code in your notes, in case you lose it or delete it. You use that same key code every time you post. It should be saved in the setup of your extension already. You just have to post that original key code in the reply box up top and also add the new TOTP code generated every so many seconds, to be able to reply.

>>17697531

Save it in a notepad. Otherwise you have to retrieve a lost code which is prob a pain or impossible. And if it disappears you just copy paste from your notes. I use the bluestacks android simulator and the key code stays in the box up top. I'm posting this reply from the bottom.

>>17697531

Also what I did, since I deleted the key code, is just uninstall and reinstall the google authenticator. Then after setting it back up, save the key code in a notepad, so you have it if it disappears or gets deleted. You have to use the one you setup the authenticator with along w/a new TOTP code for each post. So just delete, reinstall and save you key code in a safe place to reuse.