💾 Archived View for bbs.geminispace.org › s › misfin › 20101 captured on 2024-12-17 at 15:03:34. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Wanted to make a thread mentioning some of the mailinglists we have on misfin, and if others have made their own, you can post it in the comments.
You can subscribe to any of the following by sending a misfinmail with the subject "Subscribe". A subject in a misfinmail is equivalent to a gemtext title in the message body; that is, the title prepended with `# `. Some clients handle the subject separately, others require you to add them to the message body manually.
Lastly, for the federated misfin mailinglist, for most misfin servers, you should only subscribe to one of the federated mailinglists, otherwise you will get duplicates. If you are using my misfin-server software, then you can subscribe to them all as the server handles duplicate mail detection.
Sidenote: You can see the archives of all of the above mailinglists by going to their gemini mail interface (usually on port 1958).
Sep 29 · 3 months ago · 👍 johano, mrrobinhood5
I dislike Misfin (for several reasons; I had mentioned my criticisms elsewhere), and I will not use it. I think that NNTP will be better for discussion forums though.
🚀 clseibold [OP] · Sep 29 at 02:17:
@zzo38 I did see your document with criticisms of it on your scorpion document. I do agree with some of your criticisms, actually. Misfin(C) was not supposed to change too much, because people had already latched onto the core ideas of misfin itself.
I did want to mention that misfin(C)'s max message length is limited to 16KB, much higher than the 2KB of misfin(B). We also removed the new linetypes of senders, receivers, and timestamps for misfin(C) and placed them as metadata before the message data for each request, which is a slightly different way of doing it.
The lack of a language identifier is a problem. I wonder if there's a way we can fix that though, but everyone would have to agree on it. But I think we can add a thing for that.
The final thing is a big problem that I did notice: the lack of identifying certain certs as specifically for misfin. This is fixable, but we will need everyone to change their certs.
As for emails of different filetypes: I believe I looked at the backlog of this misfin BBS and seen a lot of disagreement about whether misfin should be able to send different filetypes, or if it was just text-only. That's why we chose to ignore this idea for misfin(C), especially since it then brings in a lot of security problems for clients.
Thanks for this feedback. You bring up a long of great points.