Fediverse @lemmy.world Oliver Lowe @hachyderm.io 10 mo. ago

Accessing Mastodon and the fediverse via email:

Accessing Mastodon and the fediverse via email:
https://www.olowe.co/tmp/fedimail.mp4
An experimental #IMAP and #SMTP interface.
I feel like #NNTP #Usenet interface would be more appropriate.
But gotta start somewhere!
Threading and replies work ok too (so far!).

@fediverse

4 comments

I see that you're using Acme over there... :)

Are you somewhat inspired by how Plan 9 handles e-mail? I was wondering if I could do the same but for 9front.
- Ha good eyes! :) I have basic receive-only working with Lemmy using a virtual file system interface I wrote (https://pkg.go.dev/olowe.co/lemmy). Just realised we actually spoke about this a while ago haha (https://lemmy.sdf.org/post/1035382 )
  
  But synchronising to disk is super inefficient: too many API calls. Should subscribe using ActivityPub proper and store updates received as RFC 5322 messages.
  
  From there we could serve the messages via NNTP. Then, finally, we could use nntpfs(4)
Permanently Deleted
- Oh wow thanks! :) One program syncs my home Mastodon timeline, with all replies, to a Maildir. Dovecot serves that over IMAP. Sending involves a custom SMTP server which reads the mail message and creates a post from it.
  
  For Mastodon it was all about converting statuses (toots? Posts?) into RFC 5322 messages. Using the status’ ID as Message-Id in the message header is handy. Mail clients do the heavy lifting of rendering threads thankfully!
- @skullgiver Oh wow thanks! :) One program syncs my home Mastodon timeline, with all replies, to a Maildir. Dovecot serves that over IMAP. Sending involves a custom SMTP server which reads the mail message and creates a post from it.
  
  For Mastodon it was all about converting statuses (toots? Posts?) into RFC 5322 messages. Using the status’ ID as Message-Id in the message header is handy. Mail clients do the heavy lifting of rendering threads thankfully!
  
  Permanently Deleted