v0.0.1-beta.2

Public key of recipient still has to be in compose field, when switching to DMs, but there are proper buttons to encrypt and decrypt, now. (That are hidden from view unless you switch to visibility scope direct message.)

Own public key still in compose field by default to suggest publishing one's own public key. Although one might have to split it into two or three messages, depending on the character limit of one's instance.

The encrypted messages themselves fit into a character limit of 500 as long as the cleartext isn't longer than about 200 characters.

Full Changelog: v0.0.1-beta.1...v0.0.1-beta.2

v0.0.1-beta.1

v0.0.1-beta.1

This is a very hacky but working first version.

Usage

• With visibility scope public (globe symbol), publish your public key that is already in the draft of compose view
• For further steps delete public key from compose view first
• To import public keys of other users, paste them into compose text field, remove everything else and switch visibility scope to direct (mail symbol) or public
• To encrypt a message for a user who's key you've added, put their handle in the first line and nothing else (except spaces which are removed automatically before reading it in and therefore fine). In the following lines you can write your message. For the actual encryption, switch to visibility scope private (lock symbol). While the handle remains, so the recipient is notified, the rest of the message turns into a PGP encrypted message. Send message draft as is.
• To decrypt a message sent to you with Crypty, you copy-paste the encrypted part of the received message into your compose view and remove everything else. Now you switch to unlisted visibility scope (unlocked lock symbol). The message will be decrypted and will contain your handle in the first line again. That's how you know everything worked and you can enjoy your secret message!

Some ideas for future versions

• Write proper UI for encryption and decryption procedure
• Add support for encrypting files as well
• ... (The sky is the limit.) (BTW, you need to work around character limits by splitting messages on vanilla-flavored Mastodon instances for now, where the character limit is 500. But lots of other fedi server software implementations have higher character limits, that don't pose any problems.)

Full Changelog: https://github.com/programizer/Crypty/commits/0.0.1