An updated Misfin specification
Hi all,
While implementing my own Misfin server (hermes), I started desperately wishing for a version of the Misfin B standard that was a little more formal. At the time, I had not seen Misfin C - so I, sort of foolishly, decided to take the Misfin B standard, and add a bit of technical formalism to it.
Having now gotten a little more in depth with Misfin as it is now, I realize...this seems a bit presumptious! Just to be clear - this is specifically, at this point, a revision of Misfin B intended to increase the technical specificity. I figured I would share it with anyone who was interested.
As stated in the blogpost: I am (now) aware of Misfin C, and I am sorry - I still wanted to share this for anyone who was interested, but please be assured that I was not intending to step on anyone's toes with this :)
Please let me know what you think, either here, or through the contact methods provided in the blog post.
Feb 21 · 2 months ago · 👍 cipres
7 Comments ↓
it's a bit like that xkcd standards comic :)
eventually misfin.org will expire and I'll snatch it
There are probably tons of other top domains where misfin is available.
🐁 iikorni [OP] · Feb 21 at 18:13:
@stack - absolutely, haha :)
@satch that would be cool! would be nice to have it active again :)
@iikorni It's great that you're taking an interest in misfin. Read your blog post and the spec, nice job and saw your hermes project.
Yes people use misfin, i still use it, there's also @roughnecks who set up a server recently. There are many implementations, this is a python implementation (fork of lem's):
— https://gitlab.com/cipres/misfin
Misfin C is the most recent protocol spec and that's what misfin server & clients should implement.
— satch.xyz/misfin/proposed-misfin-c-9th-draft.gmi
Oh. I thought it was a C implementation.