I literally just discovered Lagrange's ability to send misfin emails right from the interface.
Identities --> right-click your misfin-compliant cert --> send message
Also, it looks like @cipres has been pushing out some updates lately. I just installed the newest version on my capsule.
🍀 gritty [misfin:gritty@gemini.smallweb.space]
Apr 11 · 4 weeks ago · 👍 roughnecks, A161, cipres, astrowat, CalvusRex
9 Comments ↓
🐦 roughnecks · Apr 11 at 20:05:
I upgraded wpn's misfin server just a few minutes ago as well.
About lagrange, I new about that, but it's easier for me to send directly from misfin interface.
@gritty Lagrange's misfin features are really cool.
The python implementation now also shows sender and recipient addresses with a misfin: link (Lagrange shows an email icon next to these links), and if you click on these links it will use Lagrange's built-in misfin implementation to send the message.
I am probably misunderstanding something but I wonder why misfin is a new protocol rather than a specialised use of Gemini. Why not just set up a Gemini server to receive input at a particular URL, and if the sender wants to be contactable, they can send a cert with their own URL in it?
@lab6 Good question. If you were to use the Gemini protocol instead of a new protocol like misfin, one thing that would be problematic is sending and encoding the request (which contains the recipients and message body) into the URL. While it could be done, it's not very elegant, also i'm not sure about the URL's query size limit with gemini servers, if you send a large query it might just refuse it. But your point is quite valid, it could be implemented using the Gemini protocol.
You could maybe use titan for sending longer messages. technically that's a different protocol but it's pretty intertwined with gemini
I saw the misfin message limit was 2048 bytes, with advice to send two messages if you want to send more. That’s not a whole lot longer than Gemini’s 1024 bytes limit.
For multiple recipients, does that only work if they are both handled at the same server? In which case maybe just have separate URLs for each recipient and send the message twice.
@zipsegv So this all started with "Why not just use gemini instead of new protocol" and we're now at the "you can totally do it with gemini + titan" stage :=)
But yeah, you could do totally it with gemini + titan ...
🍀 gritty [OP, misfin:gritty@gemini.smallweb.space] · Apr 13 at 00:48:
@cipres - is there a way to see sent items?
@gritty No, there isn't. Will create an issue for that, wouldn't be difficult to implement.