💾 Archived View for bbs.geminispace.org › u › clseibold › 5779 captured on 2023-11-14 at 10:01:11. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Gaah! Ok, thanks for letting me know. I'll look into it quickly.
Oct 01 · 6 weeks ago
🚀 clseibold · Oct 01 at 08:49:
@alexlehm Ok, I think it should be fixed, maybe. The problem seemed to be with how I'm detecting the word "subscribe" in the message subject, although I'm not totally sure why your original message didn't go through. When you try it again I will know more.
How can I tell whether I was successful?
🚀 clseibold · Oct 01 at 19:20:
Hello @satch, Your message didn't go through because your server is sending a different fingerprint from the certificate you are using to send with, by the looks of it. Your client should be printing out error messages to the terminal, so when you sent your message, it should have printed out a "62" error.
I got a 20 back the second time though.. :(
🚀 clseibold · Oct 01 at 22:10:
@satch Hm, ok. Can you try sending the message again, whenever you have the time? Just so I can see what the problem is. I'll try to get it fixed as soon as possible. Thanks.
I am still not getting subscribed, i get a callback with an empty message (just misfin.//user@address so i guess it is trying to add the address but when sending anything it say 61
🚀 clseibold · Oct 01 at 22:51:
@alexlehm Thanks. I added better error logging and it looks like the message with Subscribe as the message subject got through (did you receive a 20 success for that one?), it just wasn't adding you to the subscribers list for some reason. I'm still looking into why.
🚀 clseibold · Oct 01 at 23:03:
@alexlehm You know what, I'm an idiot. I added code that broke the subscribe functionality because I was detecting blank text lines for verification requests, but I wasn't checking that the subject was blank as well, so subscribe messages were acting like verification requests.
Anyways, it should be fixed now! 🎉 You should be able to send another message with Subscribe as the message subject. Thanks for helping me test this!
@satch This was probably also the bug you encountered, so it should be fixed when you try to subscribe again. Thanks again for helping me test the mailinglist.
when I send # Subscribe I get 20 and the cert has
Misfin Mailinglist! — I have created a mailinglist! You can try it out by sending a misfin gemmail to misfin@auragem.letz.dev with the subject "Subscribe". For clients that don't handle subjects fully (like the original reference implementation), you need to put a "# " in front, so it should be: "# Subscribe". You should instantly get a gemmail sent back to you saying you have subscribed. Once you've subscribed, all messages sent to the mailinglist will be forwarded to you (except for your own...