bitwarden-autotype VS AutoHotkey-SerDes

Anyway, Bitwarden is free and the auto-type app is free too.

I wrote an application that does the same: Bitwarden Auto-Type. Among the features is TOTP, I used the RFC 6238 reference implementation (if you wish to write your own).

Bear in mind that you can always use AHK to extract zip files via COM. For example I wrote a few functions to handle zip/unzip (here) used in a project. with that in a Lib, you can do something like:

I wrote a small app in AHK for Bitwarden (which is a password manager). Lives outside the browsers yet you have auto-typing capabilities within browsers and any other app.

I built a small app around the CLI tool to provide KeePass-like Auto-Type capabilities but I don't like being a walking-talking advertising, however by what you post seemed a good fit.

Thus I wrote a workaround with RegEx, but that one is not battle tested, so for the time being I leave the no space between values. But in other instances (ini) where I can control the outcome I use the proper spacing :P

curl -sI https://github.com/anonymous1184/bitwarden-autotype/releases/download/v1.1.3/setup.exe | findstr Location Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/249704206/0364f9db-5321-46a9-a148-2371c0986d61?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211116%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211116T180120Z&X-Amz-Expires=300&X-Amz-Signature=81386c5d2b434355188d70bf152eaf593447f6858e264f6f4a6573ceb4d8eb86&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=249704206&response-content-disposition=attachment%3B%20filename%3Dsetup.exe&response-content-type=application%2Foctet-stream

SerDes is meant for (de)serialization. Which is completely different to load-as-object-save-reference.

For example, cocobelgica SerDes function can be used both ways, although I haven't checked how strict it is on handling case.

JSON is a nice way to persist an object to disk, another option is SerDes() which has simpler parsing as is meant for ahk_string only ecosystem, plus it supports object references.

I only use AHK_H for a specific project so I don't rely on its extra functionality, in my Standard Library I have a wrapper for SerDes(), the main selling point for me is that it has support for (circular) references.