💾 Archived View for bbs.geminispace.org › u › satch › 20949 captured on 2024-12-17 at 15:59:54. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Would be good to figure out a system for dealing with..."
@vi this is really odd... my server doesn't have any misfin fingerprint stored for you in tofu_store.list.
Oct 17 · 2 months ago
I'm like 90% sure I figured out the issue. It's "an" issue at least. Fixing it now. This was my fault for not testing Misfin C well enough!
@satch Thanks for bearing with me! I think I have it fixed now!!! I was able to send you a test message without my server crashing.
🚀 clseibold · Oct 18 at 07:43:
@vi I'm glad you got it fixed. If it would help with your implementation, we are working on an updated misfin(C) draft that makes a lot more things explicit:
I intend to finish this up very soon.
@clseibold My issue ended up being assumptions in my code for the CRLF. I initially had the server set up properly for Misfin C, but when adding Gemini and Misfin B support and then removing Titan support before I released 0.0.1, I modified/simplified my code to deal strip out the CRLF and completely forgot Misfin C expects the CRLF before the message.
I fixed it though, so it should be fine. Also added reidentification code like your server does, which "hopefully" should play nice when it eventually is used.
Would be good to figure out a system for dealing with changed client certs, preferably gracefully. I got a message from @satch, but can't respond because I sent a message to them with a previous client cert while trying to test my server initially. I suspect it'll be common for folks who build their own server or client to change their client cert while debugging and testing, even after sending a message to someone. P.S. - @satch, if you could delete my old client cert fingerprint for vi@...