Just submitted a fix to @blindndangerous's Discord Messages Reader NVDA add-on, as it had become completely unusable for me and that just wouldn't do. He merged it, and so now if you're having issues with the 2.0 version, go grab! https://github.com/blindndangerous/discord-messages-reader/releases/download/v2.1.0/discord_messages_reader-2.1.0.nvda-addon
Replying to @mewproj@fwoof.space
@mewproj You should set up commit verify.
Replying to @blindndangerous@mstdn.social
@blindndangerous I've never heard of that.
Replying to @mewproj@fwoof.space
@mewproj https://docs.github.com/en/authentication/managing-commit-signature-verification
docs.github.com/en/authentication/managing-commit-signature-verification
GitHub DocsManaging commit signature verification - GitHub DocsGitHub will verify GPG, SSH, or S/MIME signatures so other people will know that your commits come from a trusted source. GitHub will automatically sign commits you make using the web interface.
Replying to @blindndangerous@mstdn.social
@blindndangerous @mewproj I don't save any pins, why for? I have my keys in OneDrive and in the .ssh folder in the profile.
Replying to @blindndangerous@mstdn.social
@blindndangerous @mewproj Wait, you save the key in 1password to do what, sign with it every time? You can have it in %USERPROFILE%/.ssh (like C:/users/User/.ssh), then point .gitconfig at it and that's it.