💾 Archived View for bbs.geminispace.org › u › clseibold › 20964 captured on 2024-12-17 at 15:59:56. Gemini links have been rewritten to link to archived content

View Raw

More Information

-=-=-=-=-=-=-

Comment by 🚀 clseibold

Re: "Would be good to figure out a system for dealing with..."

In: s/misfin

@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:

— Misfin(C) Draft 10 Overhaul

I intend to finish this up very soon.

🚀 clseibold

Oct 18 · 2 months ago

1 Later Comment

☀️ vi [OP] · Oct 18 at 07:52:

@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.

Original Post

🌒 s/misfin

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@...

💬 vi · 14 comments · Oct 16 · 2 months ago