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

View Raw

More Information

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

Comment by ☀️ vi

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

In: s/misfin

@clseibold that gives me some info to work off of, thanks! I'll try again with verbose printing later tonight. I just wrote my server from scratch.

☀️ vi [OP]

Oct 17 · 2 months ago

7 Later Comments ↓

☀️ vi [OP] · Oct 17 at 06:53:

Sorry, things got in the way tonight, gonna do it in the next day or so.

🚀 clseibold · Oct 17 at 07:42:

@vi No problem. I obsessively keep track of the misfin subspace here, so there's no rush.

🐐 satch · Oct 17 at 09:17:

@vi this is really odd... my server doesn't have any misfin fingerprint stored for you in tofu_store.list.

☀️ vi [OP] · Oct 18 at 06:00:

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!

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

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

— Misfin(C) Draft 10 Overhaul

I intend to finish this up very soon.

☀️ 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