glawrie

Here's Python3 version for those who don't want to download Python2 for macOS 12.3 => https://github.com/tbrek/alfred-workflow-gauth/blob/master/Google Authenticator.alfredworkflow?raw=true

It absolutely is.
 
 
Plenty of them. Converting Workflows to Python 3 is considerably more work, thus takes way more time and requires a lot of testing just to reproduce what the Workflow did. Plus I dislike Python, so I don’t use it much and am not up-do-date with all the language features. Converting a ton of Workflows I don’t use from one language I dislike to another language I dislike wouldn’t be a pleasant or productive use of time. If I were to take on these conversions, there wouldn’t be time to do all the ones people are asking for. And even if there were, not all developers continue to be active to accept a pull request, meaning forking the Workflow and maintaining something I didn’t start. Disadvantages all around.

It’s way more beneficial and makes way more sense for me to cast a wide net and provide the stop gap solution for most things to work again in the short-term. That allows others (like yourself with this Workflow) the time to develop the long-term ports which will eventually replace the temporary fixes I’m posting. The GitHub repo is explicit:
 
 
The ideal scenario is one where that repo is no longer necessary. In the meantime, its existence eases the transition.

Ignore the fix I posted above it's not relevant. The issue was caused by secret which were not multiple of 8. So the actual fix is to replace `16.0` and `8` in the line you posted to `8.0` and `8`
 
secret = secret.ljust(int(math.ceil(len(secret) / 8.0) * 8), '=') This will fix the padding for the keys which length is not a multiple of 8, such as Amazon.
 
With 16.0 and 16 the script was adding too many "=" to the secret which was causing an error with b32decode.

I've now improved the dropdown sheet for rebuilding the metadata to be more clear on the processes needed, and updated the .Spotlight-V100 path for Catalina instances too.

I've been recently playing around with launchbar and switch back and forth between it and Alfred. 
One thing I noticed that is pretty killer in launchbar, is the ability to use macOS services. Launchbar is indexing them by default and lets you use them either with normal text or files. 
 
A proposal could be:
Type some text (or use a workflow to get the selected text and propagate the alfred window with it) Hit CTRL Select "Use Service" (or directly suggest them) Hit enter on a service to use them  
And the same with files. Hit CTRL and propagate the actions window with services that support the file type, next to workflow actions and default alfred actions
 
I think this would make Alfred a lot more powerful without the need to create custom workflows. A lot of apps (the majority?) already exposes services, and being able to use them directly within alfred would be great. 
 
For example, some workflows that I manually wrote that would be possible with a service:
DEVONthink: Add notes or files Delivers: Add a delivery from a text string Fantastical, Cardhop, Things: Add new entry directly from text  
Screenshot of available services enabled on my system when selecting text:

 
Screenshot of available services when selecting a file: