gboudreau · October 26, 2025 07:53 · Aug 5, 2025 · Nov 24, 2024 · Nov 24, 2024 · Sep 23, 2024
diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -13,7 +13,7 @@ If you are not logged in anymore, but can find a backup of the necessary files,
 
 If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only options now to export your tokens are 1) to use an Android phone, root it, and use that to access the Authy data, or 2) use an iOS device and mitmproxy to capture communications between the app and Authy's server, and decrypt that. Look in the comments below to find instructions on how to do that:
 
-- For iOS and the mitm approach, [see here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5298931#gistcomment-5298931)
+- For iOS and the mitm approach, [try this](https://github.com/BrenoFariasdaSilva/Authy-iOS-MiTM) (newest option), or [see here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5298931#gistcomment-5298931) (original technique).
 
 The options below are for rooted Android phones:
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -5,7 +5,7 @@
 Past August 2024, Authy stopped supported the desktop version of their apps:  
 See [Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August](https://www.theverge.com/2024/1/8/24030477/authy-desktop-app-shutting-down) for details.
 
-And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export to tokens.  
+And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.  
 
 If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
 - [for windows](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5132609#gistcomment-5132609)

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -11,7 +11,11 @@ If you are not logged in anymore, but can find a backup of the necessary files,
 - [for windows](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5132609#gistcomment-5132609)
 - [for Mac (Time Machine)](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 
-If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an Android phone, root it, and use that to access the Authy data. Look in the comments below to find instructions on how to do that:
+If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only options now to export your tokens are 1) to use an Android phone, root it, and use that to access the Authy data, or 2) use an iOS device and mitmproxy to capture communications between the app and Authy's server, and decrypt that. Look in the comments below to find instructions on how to do that:
+
+- For iOS and the mitm approach, [see here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5298931#gistcomment-5298931)
+
+The options below are for rooted Android phones:
 
 - [Post 1](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -9,7 +9,7 @@ And indeed, after a while, Authy changed something in their backend which now pr
 
 If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
 - [for windows](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5132609#gistcomment-5132609)
-- [for Mac (Time Machone)](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
+- [for Mac (Time Machine)](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 
 If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an Android phone, root it, and use that to access the Authy data. Look in the comments below to find instructions on how to do that:
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -11,7 +11,7 @@ If you are not logged in anymore, but can find a backup of the necessary files,
 - [for windows](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5132609#gistcomment-5132609)
 - [for Mac (Time Machone)](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 
-If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an old Android phone, root it, and use that to access the Authy data. Look in the comments below to find instructions on how to do that:
+If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an Android phone, root it, and use that to access the Authy data. Look in the comments below to find instructions on how to do that:
 
 - [Post 1](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 
@@ -35,7 +35,7 @@ If you can't go back to a "logged in" state in the desktop app (because you eith
 
 ---
 
-**The instructions below explain how to use the Authy desktop app to eport your 2FA tokens. If that doesn't work, look for links in the section above, to find other options you can try.**
+**The instructions below explain how to use the Authy desktop app to export your 2FA tokens. If that doesn't work, look for links in the section above, to find other options you can try.**
 
 --
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -27,6 +27,8 @@ If you can't go back to a "logged in" state in the desktop app (because you eith
 
 - [Post 6](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5173042#gistcomment-5173042)
 
+- [Post 7](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5201894#gistcomment-5201894)
+
 - You need to install Authy from Play Store, not using an APK. [Ref](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5133448#gistcomment-5133448)
 
 - Using very old Android version (eg. Android 6)? [see here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5117610#gistcomment-5117610)

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -25,6 +25,8 @@ If you can't go back to a "logged in" state in the desktop app (because you eith
   - Ref: [@markuta's script](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5139849#gistcomment-5139849)
   - Ref: [@ShaunLWM mod to markuta's script] https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5142546#gistcomment-5142546
 
+- [Post 6](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5173042#gistcomment-5173042)
+
 - You need to install Authy from Play Store, not using an APK. [Ref](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5133448#gistcomment-5133448)
 
 - Using very old Android version (eg. Android 6)? [see here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5117610#gistcomment-5117610)

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -11,7 +11,23 @@ If you are not logged in anymore, but can find a backup of the necessary files,
 - [for windows](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5132609#gistcomment-5132609)
 - [for Mac (Time Machone)](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 
-If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an old Android phone, root it, and use that to access the Authy data. Look in the comments to find instructions on how to do that.
+If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an old Android phone, root it, and use that to access the Authy data. Look in the comments below to find instructions on how to do that:
+
+- [Post 1](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
+
+- [Post 2](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5166329#gistcomment-5166329)
+
+- [Post 3](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5161753#gistcomment-5161753)
+
+- [Post 4](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5130860#gistcomment-5130860)
+
+- [Post 5](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5152172#gistcomment-5152172)
+  - Ref: [@markuta's script](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5139849#gistcomment-5139849)
+  - Ref: [@ShaunLWM mod to markuta's script] https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5142546#gistcomment-5142546
+
+- You need to install Authy from Play Store, not using an APK. [Ref](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5133448#gistcomment-5133448)
+
+- Using very old Android version (eg. Android 6)? [see here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5117610#gistcomment-5117610)
 
 ---
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -7,7 +7,9 @@ See [Authy is shutting down its desktop app | The 2FA app Authy will only be ava
 
 And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export to tokens.  
 
-If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.  
+If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
+- [for windows](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5132609#gistcomment-5132609)
+- [for Mac (Time Machone)](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=5113144#gistcomment-5113144)
 
 If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an old Android phone, root it, and use that to access the Authy data. Look in the comments to find instructions on how to do that.
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -1,17 +1,22 @@
-# Generating Authy passwords on other authenticators
---------
+# Exporting your 2FA tokens from Authy to transfer them into another 2FA application
 
-*update: TBC, but this new might affect how easy it is to use this technique past August 2024: 
-[Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August](https://www.theverge.com/2024/1/8/24030477/authy-desktop-app-shutting-down)
+## IMPORTANT - Update regarding deprecation of Authy desktop apps
 
----
+Past August 2024, Authy stopped supported the desktop version of their apps:  
+See [Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August](https://www.theverge.com/2024/1/8/24030477/authy-desktop-app-shutting-down) for details.
+
+And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export to tokens.  
 
-*update 2: And indeed, after a while, Authy stopped supporting the desktops apps, which will now prevent you from logging in into those apps. If you are already logged in, then you are in luck, and you can follow the instructions below to export to tokens. If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.  
+If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.  
 
 If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an old Android phone, root it, and use that to access the Authy data. Look in the comments to find instructions on how to do that.
 
 ---
 
+**The instructions below explain how to use the Authy desktop app to eport your 2FA tokens. If that doesn't work, look for links in the section above, to find other options you can try.**
+
+--
+
 This gist, based in part on [a gist by Brian Hartvigsen](https://gist.github.com/tresni/83b9181588c7393f6853), allows you to export from Authy your TOTP tokens you have stored there.  
 Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -6,6 +6,12 @@
 
 ---
 
+*update 2: And indeed, after a while, Authy stopped supporting the desktops apps, which will now prevent you from logging in into those apps. If you are already logged in, then you are in luck, and you can follow the instructions below to export to tokens. If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.  
+
+If you can't go back to a "logged in" state in the desktop app (because you either never used the desktop app, or you did but don't have a backup of the necessary files), then your only option now to export your tokens is to use an old Android phone, root it, and use that to access the Authy data. Look in the comments to find instructions on how to do that.
+
+---
+
 This gist, based in part on [a gist by Brian Hartvigsen](https://gist.github.com/tresni/83b9181588c7393f6853), allows you to export from Authy your TOTP tokens you have stored there.  
 Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -63,7 +63,7 @@ Detailed How-To
     ```bash
     cd /tmp
     # curl -Lo authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
-    curl -Lo authy.snap https://file.io/rd8R1JmQYqHf # Copy of above file that is now gone
+    curl -Lo authy.snap https://filebrowser.patati.ca/api/public/dl/Tk1sjeEi/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap # Copy of above file that is now gone
     if ! echo a488d3f3c06672a78f53da144f4325d8 authy.snap | md5sum -c --status ; then
         echo "Error: invalid MD5 hash"
     else

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -74,7 +74,9 @@ Detailed How-To
     </details>
 
     <details>
-    <summary>Linux (using flatpak) (alternative method if snap above doesn't work)</summary>
+    <summary>Linux (using flatpak) (alternative method if snap above doesn't work) (NOT WORKING ANYMORE)</summary>
+
+    It seems flathub is using the `api.snapcraft.io` repo behind the scene, so trying to install using the below commands will fail, now that the Authy app was removed from `api.snapcraft.io`. Try to install directly the snap (using the above method), instead of using `flatpak`.
 
     ```bash
     flatpak install flathub com.authy.Authy

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -62,7 +62,8 @@ Detailed How-To
 
     ```bash
     cd /tmp
-    curl -Lo authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
+    # curl -Lo authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
+    curl -Lo authy.snap https://file.io/rd8R1JmQYqHf # Copy of above file that is now gone
     if ! echo a488d3f3c06672a78f53da144f4325d8 authy.snap | md5sum -c --status ; then
         echo "Error: invalid MD5 hash"
     else

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -50,7 +50,8 @@ Detailed How-To
 
     Authy will start after installation. Close it ASAP.
 
-    To prevent auto-update, go to the `%LOCALAPPDATA%\authy` folder, and delete `Update.exe`. Delete the `app-2.4.2` folder, if it exists. (The version number will probably be a higher number.) In the `app-2.2.3` subfolder, delete `Update.exe`.
+    To prevent auto-update, go to the `%LOCALAPPDATA%\authy` folder, and delete `Update.exe`. Delete the `app-2.5.0` folder, if it exists. (The version number will probably be a higher number.) In the `app-2.2.3` subfolder, delete `Update.exe`.  
+    Of note: If you later want to uninstall Authy, you'll need to restore those files, as `Update.exe` is the executable used by the uninstallation process.
 
     Or, after the app updated, you can change your shortcut to execute `"%LOCALAPPDATA%\authy\app-2.2.3\Authy Desktop.exe" --remote-debugging-port=5858` and change the `Start in` to `%LOCALAPPDATA%\authy\app-2.2.3`  
     Even after an update is installed, 2.2.3 is still installed.

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -39,7 +39,7 @@ Detailed How-To
 
     You can use the [winget (CLI) tool](https://learn.microsoft.com/en-us/windows/package-manager/winget/):
     ```
-    winget install -e --id Twilio.Authy -v 2.2.3
+    winget install --no-upgrade --force -e --id Twilio.Authy -v 2.2.3
     ```
 
     Or download and install one of those:  

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -37,7 +37,12 @@ Detailed How-To
     <details>
     <summary>Windows</summary>
 
-    Download and install one of those:  
+    You can use the [winget (CLI) tool](https://learn.microsoft.com/en-us/windows/package-manager/winget/):
+    ```
+    winget install -e --id Twilio.Authy -v 2.2.3
+    ```
+
+    Or download and install one of those:  
     64-bit: https://pkg.authy.com/authy/stable/2.2.3/win32/x64/Authy%20Desktop%20Setup%202.2.3.exe  
       MD5 hash: `efd176d89b280809b9f84fda9ba50840`  
     32-bit: https://pkg.authy.com/authy/stable/2.2.3/win32/x32/Authy%20Desktop%20Setup%202.2.3.exe  

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -16,9 +16,11 @@ Since the Authy "desktop" app is a Chromium-based web-app, we'll use the Develop
 Detailed How-To
 ---
 
-1. Install Authy desktop app, version 2.2.3 (the more recent versions won't work)
+1. Install Authy desktop app, version 2.2.3 (the more recent versions won't work).
 
-    Note: If you are prompted to update, do NOT do it; the latest version doesn't support `--remote-debugging-port` needed below.
+    Note: If you are prompted to update, do NOT do it; the latest version doesn't support `--remote-debugging-port` needed in point (2) below.
+
+    (Click your OS below to get personalized instructions.)
 
     <details>
     <summary>macOS</summary>

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -97,20 +97,21 @@ Detailed How-To
     or `flatpak run com.authy.Authy --remote-debugging-port=5858`  (if you used flatpak)
     </details>
 
-3. In Authy, Log in so you can see the codes being generated for you.  
-   If you have some codes that show a padlock next to them, you will need to enter your Backup Password before continuing below, or those codes won't be exported correctly (`decryptedSeed` will be empty).
+3. In Authy, Log in so you can see the codes being generated for you.
 
-4. Open the following URL in Google Chrome (or any Chromium-based browser): http://localhost:5858
+4. If you have some codes that show a padlock next to them, you will need to enter your Backup Password before continuing below, or those codes won't be exported correctly (`decryptedSeed` will be empty).
 
-5. Click the `Twilio Authy` link in that webpage.
+5. Open the following URL in Google Chrome (or any Chromium-based browser): http://localhost:5858
 
-6. In Chrome Developer Tools top navigation bar, go in the `Sources` tab (if you don't see it, click `>>` to expand the full list), then select the `Snippets` sub-tab (tabs on the second line; again, click `>>` to expand the full list), and finally choose `+ New snippet`.
+6. Click the `Twilio Authy` link in that webpage.
+
+7. In Chrome Developer Tools top navigation bar, go in the `Sources` tab (if you don't see it, click `>>` to expand the full list), then select the `Snippets` sub-tab (tabs on the second line; again, click `>>` to expand the full list), and finally choose `+ New snippet`.
 
     **Careful here**: do NOT open the Chrome Developer Tools like you normally do. When you go to http://localhost:5858, and click the `Twilio Authy` link in that webpage, it will show you Developer Tools for the Authy app. This is where you need to work. Here's a video that shows you exactly where you need to be, when you paste code: https://youtu.be/nArCf8iEqlw
 
-7. If you'd like to ensure the code below doesn't send anything to a remote server, you can disconnect from the internet now.
+8. If you'd like to ensure the code below doesn't send anything to a remote server, you can disconnect from the internet now.
 
-8. In the snippet editor window that appears on the right, paste one of the following code options:
+9. In the snippet editor window that appears on the right, paste one of the following code options:
 
     <details>
     <summary>Simplest</summary>
@@ -465,7 +466,7 @@ Detailed How-To
     Getting `Uncaught ReferenceError: appManager is not defined` error?  
     Go watch this YouTube video that shows you where you need to be, when you paste code: https://youtu.be/nArCf8iEqlw
 
-9. Right-click the snippet name on the navigator pane on the left (eg. `Script snippet #1`) , and choose `Run`.
+10. Right-click the snippet name on the navigator pane on the left (eg. `Script snippet #1`) , and choose `Run`.
 
 
 ### Thanks

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -192,10 +192,10 @@ Detailed How-To
     ```javascript
     let x = []; 
     appManager.getModel().forEach(i => {
-      if (i.originalName && i.decryptedSeed) {
+      if (i.decryptedSeed) {
         x.push({
           type: 1, 
-          name: i.originalName,
+          name: i.originalName ?? i.name ?? `[No Name] - Imported from Authy (${x.length})`,
           login: {username: i.name, totp: i.decryptedSeed}
         })
       }});

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -54,7 +54,7 @@ Detailed How-To
 
     ```bash
     cd /tmp
-    curl -o authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
+    curl -Lo authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
     if ! echo a488d3f3c06672a78f53da144f4325d8 authy.snap | md5sum -c --status ; then
         echo "Error: invalid MD5 hash"
     else

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -93,7 +93,8 @@ Detailed How-To
     <details>
     <summary>Linux</summary>
 
-    From a terminal: `./authy --remote-debugging-port=5858`
+    From a terminal: `./authy --remote-debugging-port=5858` (if you used snap)  
+    or `flatpak run com.authy.Authy --remote-debugging-port=5858`  (if you used flatpak)
     </details>
 
 3. In Authy, Log in so you can see the codes being generated for you.  

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -77,9 +77,24 @@ Detailed How-To
     </details>
 
 2. Start Authy desktop app, but add the `--remote-debugging-port=5858` parameter to the command-line:
-  - On Windows: right-click the Authy desktop shortcut, and in the Target field write `--remote-debugging-port=5858` at the end. Then click OK. Double-click the Authy desktop shortcut.
-  - On Mac: from Terminal.app: `open -a "Authy Desktop" --args --remote-debugging-port=5858`
-  - On Linux, from a terminal: `./authy --remote-debugging-port=5858`
+
+    <details>
+    <summary>macOS</summary>
+
+    From Terminal.app: `open -a "Authy Desktop" --args --remote-debugging-port=5858`
+    </details>
+
+    <details>
+    <summary>Windows</summary>
+
+    Right-click the Authy desktop shortcut, and in the Target field write `--remote-debugging-port=5858` at the end. Then click OK. Double-click the Authy desktop shortcut.
+    </details>
+
+    <details>
+    <summary>Linux</summary>
+
+    From a terminal: `./authy --remote-debugging-port=5858`
+    </details>
 
 3. In Authy, Log in so you can see the codes being generated for you.  
    If you have some codes that show a padlock next to them, you will need to enter your Backup Password before continuing below, or those codes won't be exported correctly (`decryptedSeed` will be empty).

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -20,16 +20,21 @@ Detailed How-To
 
     Note: If you are prompted to update, do NOT do it; the latest version doesn't support `--remote-debugging-port` needed below.
 
-  - macOS:
+    <details>
+    <summary>macOS</summary>
+
     Download and install this file: https://pkg.authy.com/authy/stable/2.2.3/darwin/x64/Authy%20Desktop-2.2.3.dmg  
     MD5 hash: `ab7e4ae5b88cb71f84394df6989950aa`
 
     You can use the following command in Terminal, before launching Authy Desktop, to disable auto-updates:  
     ```bash  
     mkdir -p ~/Library/Caches/com.authy.authy-mac.ShipIt ; rm -rf ~/Library/Caches/com.authy.authy-mac.ShipIt/* ; chmod 500 ~/Library/Caches/com.authy.authy-mac.ShipIt
     ```
+    </details>
+
+    <details>
+    <summary>Windows</summary>
 
-  - Windows:
     Download and install one of those:  
     64-bit: https://pkg.authy.com/authy/stable/2.2.3/win32/x64/Authy%20Desktop%20Setup%202.2.3.exe  
       MD5 hash: `efd176d89b280809b9f84fda9ba50840`  
@@ -42,8 +47,11 @@ Detailed How-To
 
     Or, after the app updated, you can change your shortcut to execute `"%LOCALAPPDATA%\authy\app-2.2.3\Authy Desktop.exe" --remote-debugging-port=5858` and change the `Start in` to `%LOCALAPPDATA%\authy\app-2.2.3`  
     Even after an update is installed, 2.2.3 is still installed.
+    </details>
+
+    <details>
+    <summary>Linux (using snap) (recommended)</summary>
 
-  - Linux (using snap) (recommended):
     ```bash
     cd /tmp
     curl -o authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
@@ -54,15 +62,19 @@ Detailed How-To
         cd authy-2.2.3/
     fi
     ```
+    </details>
+
+    <details>
+    <summary>Linux (using flatpak) (alternative method if snap above doesn't work)</summary>
 
-  - Linux (using flatpak) (alternative method if snap above doesn't work):
     ```bash
     flatpak install flathub com.authy.Authy
     # Update to the 2.2.3 commit (found this commit using: flatpak remote-info --log flathub com.authy.Authy)
     sudo flatpak update --commit=83c0df0dd48bbb6ad851f5cc62d6e0836e56e499c7a79041241809f8296e65cc com.authy.Authy
     # Optionally, if you want to export a JSON file, give access to Authy to your Home folders:
     sudo flatpak override --filesystem=home com.authy.Authy
     ```
+    </details>
 
 2. Start Authy desktop app, but add the `--remote-debugging-port=5858` parameter to the command-line:
   - On Windows: right-click the Authy desktop shortcut, and in the Target field write `--remote-debugging-port=5858` at the end. Then click OK. Double-click the Authy desktop shortcut.

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -78,11 +78,12 @@ Detailed How-To
 
 6. In Chrome Developer Tools top navigation bar, go in the `Sources` tab (if you don't see it, click `>>` to expand the full list), then select the `Snippets` sub-tab (tabs on the second line; again, click `>>` to expand the full list), and finally choose `+ New snippet`.
 
-    **Careful here**: do NOT open the Chrome Developer Tools like you normally do. When you go to http://localhost:5858, and click the `Twilio Authy` link in that webpage, it will show you Developer Tools for the Authy app. This is where you need to work.
+    **Careful here**: do NOT open the Chrome Developer Tools like you normally do. When you go to http://localhost:5858, and click the `Twilio Authy` link in that webpage, it will show you Developer Tools for the Authy app. This is where you need to work. Here's a video that shows you exactly where you need to be, when you paste code: https://youtu.be/nArCf8iEqlw
 
 7. If you'd like to ensure the code below doesn't send anything to a remote server, you can disconnect from the internet now.
 
 8. In the snippet editor window that appears on the right, paste one of the following code options:
+
     <details>
     <summary>Simplest</summary>
 
@@ -433,6 +434,9 @@ Detailed How-To
     ```
     </details>
 
+    Getting `Uncaught ReferenceError: appManager is not defined` error?  
+    Go watch this YouTube video that shows you where you need to be, when you paste code: https://youtu.be/nArCf8iEqlw
+
 9. Right-click the snippet name on the navigator pane on the left (eg. `Script snippet #1`) , and choose `Run`.
 
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -6,41 +6,17 @@
 
 ---
 
-There is an increasing count of applications which use Authy for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.
+This gist, based in part on [a gist by Brian Hartvigsen](https://gist.github.com/tresni/83b9181588c7393f6853), allows you to export from Authy your TOTP tokens you have stored there.  
+Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
 
-Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. I couldn't find any completely working solutions, however I stumbled upon [a gist by Brian Hartvigsen](https://gist.github.com/tresni/83b9181588c7393f6853). His post had a neat code with it to generate QR codes for you to use on your favorite authenticator.
+Since the Authy "desktop" app is a Chromium-based web-app, we'll use the Developer Tools provided by Chromium to execute Javascript code that will export the tokens in JSON or as QR codes. You can then import or manually add those in you preferred application.
 
-His method is to extract the secret keys using Authy's Google Chrome app via Developer Tools. If this was not possible, I guess people would be reverse engineering the Android app or something like that. But when I tried that code, nothing appeared on the screen. My guess is that Brian used the code to extract the keys that weren't necessarily tied to Authy.
+**Important**: If you have any accounts that use the Authy TOTP SDK (eg. Gemini, Twitch, Sendgrid, Twilio, ...), **you can NOT delete your Authy account**, even after migrating your TOTP tokens to another software! If you do, you could be locking yourself out of all the accounts that require Authy specifically! Your only option here would be to go in those accounts, disable Authy 2FA, and enable another 2FA method. More details [here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=4829538#gistcomment-4829538).
 
-I had to adapt the code a little and you can see the result below, but here's what I discovered about Authy's method:
-* They use the exact same algorithm to generate passwords as Google Authenticator and similar (TOTP)
-* The passwords are one digit longer - 7 digits (usually they're 6, with exceptions), but if you've looked at one of the Authy generated passwords already, you probably noticed it too
-* The password validity period is 10 seconds (instead of usual 30). Authy shows 20 seconds, but that means a slightly different thing. Don't substitute this period longer in your Authenticator.
-* Authy's secret keys are in hex already, so they need to be turned back to base32 for working QR codes
-
-So as long as you have an authenticator which can do longer passwords than 6 characters and do custom time periods, then congratulations, you can use the following method. If you are not sure, scan this code with your authenticator to test. Don't forget to delete it afterwards. The code should have 7 digits and should change every 10 seconds.
-
-![](https://www.google.com/chart?chs=200x200&chld=M|0&cht=qr&chl=otpauth://totp/PLEASE_DELETE_ME%3Fsecret%3DDEADBEEFDEADBEEF%26digits%3D7%26period%3D10)
-
-Known to work:
-* 1Password
-* 2FAS
-* Aegis
-* Bitwarden
-* ente Authenticator
-* Google Authenticator
-* KeepassXC
-* Keepass2Android
-* LastPass
-* 2FAS
-
-### Ok, that's nice, but I want to get rid of Authy now
-
-This method has only one gotcha - if you want add a new service that relies on Authy, you will need to run Authy again. I am assuming you know how to use Authy and have some services added already. You can probably get rid of Authy on your phone and log in to Authy on your desktop using SMS.
-
-**Important: If you have any accounts that use the Authy TOTP SDK (eg. Gemini, Twitch, Sendgrid, Twilio, ...), you can NOT delete your Authy account, even after migrating your TOTP tokens to another software! If you do, you could be locking yourself out of all the accounts that require Authy! Your only option here would be to go in those accounts, disable Authy TOTP, and re-enable another 2FA method.** More details [here](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=4829538#gistcomment-4829538).
+Detailed How-To
+---
 
-1. Install Authy desktop app, version 2.2.3 (the versions after that won't work)
+1. Install Authy desktop app, version 2.2.3 (the more recent versions won't work)
 
     Note: If you are prompted to update, do NOT do it; the latest version doesn't support `--remote-debugging-port` needed below.
 
@@ -460,7 +436,7 @@ This method has only one gotcha - if you want add a new service that relies on A
 9. Right-click the snippet name on the navigator pane on the left (eg. `Script snippet #1`) , and choose `Run`.
 
 
-### Resources used for getting correct codes
+### Thanks
 
 * [Brian's gist](https://gist.github.com/tresni/83b9181588c7393f6853)
 * [JavaScript implementation of base32 encoding by Chris Umbel, et al.](https://github.com/chrisumbel/thirty-two/blob/master/lib/thirty-two/thirty-two.js)

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -6,7 +6,7 @@
 
 ---
 
-There is an increasing count of applications which use [Authy](https://www.authy.com/) for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.
+There is an increasing count of applications which use Authy for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.
 
 Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. I couldn't find any completely working solutions, however I stumbled upon [a gist by Brian Hartvigsen](https://gist.github.com/tresni/83b9181588c7393f6853). His post had a neat code with it to generate QR codes for you to use on your favorite authenticator.
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -96,7 +96,7 @@ This method has only one gotcha - if you want add a new service that relies on A
 3. In Authy, Log in so you can see the codes being generated for you.  
    If you have some codes that show a padlock next to them, you will need to enter your Backup Password before continuing below, or those codes won't be exported correctly (`decryptedSeed` will be empty).
 
-4. Open the following URL in your web browser: http://localhost:5858
+4. Open the following URL in Google Chrome (or any Chromium-based browser): http://localhost:5858
 
 5. Click the `Twilio Authy` link in that webpage.
 

diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -45,7 +45,8 @@ This method has only one gotcha - if you want add a new service that relies on A
     Note: If you are prompted to update, do NOT do it; the latest version doesn't support `--remote-debugging-port` needed below.
 
   - macOS:
-    Download and install this file: https://pkg.authy.com/authy/stable/2.2.3/darwin/x64/Authy%20Desktop-2.2.3.dmg
+    Download and install this file: https://pkg.authy.com/authy/stable/2.2.3/darwin/x64/Authy%20Desktop-2.2.3.dmg  
+    MD5 hash: `ab7e4ae5b88cb71f84394df6989950aa`
 
     You can use the following command in Terminal, before launching Authy Desktop, to disable auto-updates:  
     ```bash  
@@ -55,7 +56,9 @@ This method has only one gotcha - if you want add a new service that relies on A
   - Windows:
     Download and install one of those:  
     64-bit: https://pkg.authy.com/authy/stable/2.2.3/win32/x64/Authy%20Desktop%20Setup%202.2.3.exe  
-    32-bit: https://pkg.authy.com/authy/stable/2.2.3/win32/x32/Authy%20Desktop%20Setup%202.2.3.exe
+      MD5 hash: `efd176d89b280809b9f84fda9ba50840`  
+    32-bit: https://pkg.authy.com/authy/stable/2.2.3/win32/x32/Authy%20Desktop%20Setup%202.2.3.exe  
+      MD5 hash: `d66d63abb482523ad27dfe676e249fff`
 
     Authy will start after installation. Close it ASAP.
 
@@ -68,8 +71,12 @@ This method has only one gotcha - if you want add a new service that relies on A
     ```bash
     cd /tmp
     curl -o authy.snap https://api.snapcraft.io/api/v1/snaps/download/H8ZpNgIoPyvmkgxOWw5MSzsXK1wRZiHn_18.snap
-    unsquashfs -q -f -d authy-2.2.3 authy.snap
-    cd authy-2.2.3/
+    if ! echo a488d3f3c06672a78f53da144f4325d8 authy.snap | md5sum -c --status ; then
+        echo "Error: invalid MD5 hash"
+    else
+        unsquashfs -q -f -d authy-2.2.3 authy.snap
+        cd authy-2.2.3/
+    fi
     ```
 
   - Linux (using flatpak) (alternative method if snap above doesn't work):
@@ -458,4 +465,4 @@ This method has only one gotcha - if you want add a new service that relies on A
 * [Brian's gist](https://gist.github.com/tresni/83b9181588c7393f6853)
 * [JavaScript implementation of base32 encoding by Chris Umbel, et al.](https://github.com/chrisumbel/thirty-two/blob/master/lib/thirty-two/thirty-two.js)
 * [Google Authenticator URI format](https://github.com/google/google-authenticator/wiki/Key-Uri-Format)
-* Various commenters below ([gadelkareem](https://gist.github.com/gboudreau/94bb0c11a6209c82418d01a59d958c93?permalink_comment_id=4068390#gistcomment-4068390) in particular, for the alternative code above)
+* Various commenters below
diff --git a/AuthyToOtherAuthenticator.md b/AuthyToOtherAuthenticator.md
@@ -87,7 +87,7 @@ This method has only one gotcha - if you want add a new service that relies on A
   - On Linux, from a terminal: `./authy --remote-debugging-port=5858`
 
 3. In Authy, Log in so you can see the codes being generated for you.  
-   If you have some codes that show a padlock next to them, you will need to enter your Backup Password before continuing below, or those codes won't be exported.
+   If you have some codes that show a padlock next to them, you will need to enter your Backup Password before continuing below, or those codes won't be exported correctly (`decryptedSeed` will be empty).
 
 4. Open the following URL in your web browser: http://localhost:5858