💾 Archived View for bbs.geminispace.org › u › skyjake › 20578 captured on 2024-12-17 at 15:27:21. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "While I was working on my misfin server, I was thinking..."
Incidentally, looks like Bubble has a bug in the composer where link segments can't correctly handle percent-coded characters like %23 and %20. I replaced the link above with regular gemtext.
EDIT: Fixed. The problem was specific to editing links with Titan.
Oct 09 · 2 months ago
🚀 clseibold [OP] · Oct 09 at 10:39:
Over on the IRC we were just mentioning the idea of having multiple recipients. In email there's no good standard to deal with this, as using comma/semicolon-separated addresses is not spec compliant and breaks on different clients. Additionally, currently misfin links treat queries similarly to gemini and its siblings, meaning no query parameters. But there is the possibility of utilizing query parameters like with mailto links, and this could be used to specify additional recipients.
Lastly, email aliases are another possible solution, although they are complicated by how misfin deals with certs. If you have a receive-only alias that is meant to stand-in for a list of recipients, the server had to then have the user's cert to send the gemmail received by the alias to the recipients represented by that alias, so that the recipients get the gemmail by the user and not the alias itself.
Servers that intend to make mailboxes using Certificate Signing Requests, where the mailserver can sign the cert but doesn't ever see or touch the private key, would not have access to the key to send gemmails on behalf of the mailbox holder.
While no misfin servers currently behave this way (for various reasons, like not having good misfin clients that can do CSRs), I was thinking about supporting this setup as an option for multi-user mailservers in the future. This makes the idea of receive-only aliases as a stand-in for multiple recipients impossible to do at the server side.
🚀 clseibold [OP] · Oct 09 at 11:04:
Just to give an update, I wanted to say that these are the main concerns with the URL syntax:
— https://www.rfc-editor.org/rfc/rfc3986#section-1.1.1
While I was working on my misfin server, I was thinking that it would be useful to be able to pre-fill the subject line (or rather, pre-fill the body with a title line, perhaps) within a misfin link, similar to what you can do with mailto links. It could be placed in the query string, like so `misfin://clseibold@auragem.letz.dev?%23%20Misfin%20Links`. @skyjake Do you have any thoughts on supporting something like this for Lagrange? misfin://clseibold@auragem.letz.dev?%23%20Misfin%20Links Test...