💾 Archived View for bbs.geminispace.org › u › pollux › 18758 captured on 2024-08-19 at 01:02:23. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "How many of you actively use misfin? I have been tempted..."
@gemalaya I can not open the messages, because they are not clickable and say:
Message with ID 4 is encrypted or has an invalid status.
Message with ID 3 is encrypted or has an invalid status.
Jul 21 · 4 weeks ago
@gemalaya Never mind ... Decrypted your message and replied. :-)
@pollux Got your (correct) reply, proof that you could decrypt the question .. Authentication with x509 certificates, (fast) at rest message encryption, text only (gemtext) payloads, gemini interface. What else does one need for electronic mail ...
@gemalaya Maybe a Cc: Field would be nice, to allow people to send to multiple recipients.
@gemalaya I now have some problems. I regularly receive an encrypted message and when I try to decrypt it it is gone.
@pollux Not sure what you mean by that. What do you mean by "it is gone" ? What do you see in the messages list before and after you click "decrypt messages" and send the key ?
@gemalaya before I decrypt I always see this:
Message with ID 3 is encrypted or has an invalid status. and when decrypting the message goes away, so that I can't see it's content. Now I disabled encryption and saw your message..
@pollux Please post a screencast somewhere that shows the problem. If by "goes away" you mean, before sending the key there are 4 messages in the inbox, and after decrypting there are only 2 or 3 messages, that means some messages can't be decrypted with the key you sent. Remember that you've changed your key once and therefore the messages you've received for the first key can't be decrypted now if you didn't store the key, so they won't be in the list once you send a key.
I use encryption on my hashnix account, no issue yet.
@gemalaya I can't get rid of Message with ID 3 is encrypted or has an invalid status.. This message #3 comes again after a while, when decrypting my inbox, but show nothing, when decrypting. Your message #4 is no problem, or other messages that may follow. Sorry for providing no screencast, because I do not have such software.
@pollux All of this is normal: message #3 was encrypted for another key (the previous key, that you didn't save, right ?). Since you've changed keys now, you can't decrypt msg #3, that message can't be read (unless you recover the prev key). Subsequent messages, starting with message #4, were encoded for the new key, and so once you call "decrypt messages" with that key, you're able to decrypt all messages starting from #4. So you can ignore these "is encrypted or has an invalid status" text messages, they're just there to make it clear that there are encrypted messages in your gembox. I hope i explained it correctly.
@gemalaya Ok, thanks, but it is a bit annoying that I can't get rif of that particular message #3.
@pollux You should be able to delete it by going to this URL:
— hashnix.club:1958/msg/3/delete
With automatic confirmation:
— hashnix.club:1958/msg/3/delete?YES
@gemalaya It does not work, it says message not found, while it is still there. :-(
@gemalaya when I fetch my inbox messages it says that message #3 is from < invalid@misfin.org
: invalid@misfin.org
@ 2024-07-26T09:27:28Z
@pollux Ok. Well please ignore it for now, it's really unimportant. Next update will fix this (deletion of messages regardless of status).
@pollux Yes, when it cannot decrypt a message, the gembox reader yields a message with status 4:
— https://gitlab.com/cipres/misfin/-/blob/master/misfin/letter.py?ref_type=heads#L514
Pushing a change soon that lets you delete those messages from the inbox.
Thanks!
@pollux Pushed the changes, won't be available until there's an upgrade on hashnix.
@gemalaya No problem.
How many of you actively use misfin? I have been tempted to make a personal misfin server for a while, but keep stopping short of starting because I end up fearing that few enough folks use it. Would be nice to use it to reply to gemlog posts rather than relying on email.