💾 Archived View for bbs.geminispace.org › s › misfin › 5518 captured on 2023-11-14 at 10:03:29. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Hi sup I'm the guy who wrote Misfin. Took a little break if you couldn't tell. The outline:
1. Life events happen
2. Spend time in the woods (metaphorical)
3. Spend time in the woods (literal)
4. Get an email that jerks you back to reality
Glad to see people doing things with Misfin still. I'll be responding to things over the next couple days - feel free to hit me up.
Sep 25 · 7 weeks ago · 👍 Captain, clseibold
Lost access to your original @lem account?
🚀 clseibold · Sep 25 at 04:41:
I'm just now seeing this misfin protocol. It already sounds interesting! I've been thinking about how a new rewrite of the email system could be a good thing for a long time myself!
I have two questions;
It says in the documentation that you will choose between protocol A and B at some stage. Any idea when?
Are you and @lem the same or different people?
Finally, thanks for this project. I’m glad that you’re out of the metaphorical woods and hope that all is relatively well.
Glad you're back!
@lem-two I'm trying to add a service mode in misfin to be able to serve multiple identities. I've written a message handler that stores the messages in a "mbox".
The main thing that's left to add is how to check that the recipient's certificate is signed by the main certificate (the CA), if you have any tips on this that'd be great. My idea was to address the typical use case, where you create a self-signed CA, and then each user on the server has a certificate signed by that CA ?
— https://gitlab.com/cipres/misfin
@lem-two I found how to verify a cert's signature by a CA with pyopenssl and X509Store, so no problem now