What have I done?! My abomination of an idea of bridging my email and ActivityPub progresses. If you see this message, something is working! Comments replies are welcome as it's a good test of this system :)
People keep saying ActivityPub is a lot like email. If it's so similar to email, could I use my email client to interact with the fediverse?
Previously I did this by writing a SMTP interface to the Mastodon HTTP API. That worked. But as we probably know, the fediverse is not Mastodon; it's really ActivityPub. The real deal would be working with ActivityPub directly, not the Mastodon HTTP API.
And that's now (mostly?) working! In shonky diagram form, sending looks like this:
laptop --SMTP--> my_server --ActivityPub--> fediverse
Replies look like this:
fediverse --ActivityPub--> my_server --SMTP--> mailbox <--IMAP-- laptop
my_server translates back and forth between ActivityPub messages and
mail messages.
For example given the message:
Date: Wed, 6 Mar 2024 16:37:59 +1100
From: Oliver Lowe <otl@apubtest2.srcbeat.com>
To: localtesting@aussie.zone
Subject: test 2
test hello world!
The following ActivityPub message is created:
{
"@context": "https://www.w3.org/ns/activitystreams",
"id":"https://apubtest2.srcbeat.com/outbox/1709703480070628170",
"type":"Note",
"name":"test 2",
"to": ["https://aussie.zone/c/localtesting","https://www.w3.org/ns/activitystreams#Public"],
"cc": ["https://aussie.zone/c/localtesting"],
"published":"2024-03-06T16:37:59+11:00",
"attributedTo":"https://apubtest2.srcbeat.com/actor.json",
"content":"test hello world!",
"mediaType":"text/markdown"
}
There's still a lot of bugs (of course) and unimplemented bits (of course). I can't call this a proper fediverse service yet. I'm going to roll with this for a bit and see how it holds up.
Darn it, you got me. I hadn't thought about it more deeply, but now I'll give it a few minutes.
So yeah, a lemmy UI to LKML would make the experience much better. Obviously the LKML serves two purposes: discussion and code review, for which the latter lemmy probably isn't too well equipped, but it would help make it more approachable.
Probably to make it work there'd need to be some kind of listener. I imagine signing up to a mailinglist with an email address of the domain running your software would suffice. Incoming emails would then be converted to activitypub messages and sent to the lemmy server you control.
You'd have two classes of email addressed: list email addresses which map to lemmy communities and user email addresses which map to users on the lemmy server (which could also be remote users in the fediverse). The list email addresses are there to create posts in the lemmy community and populate existing lemmy posts (created in the mailinglist) with responses from the mailinglist (response = comment).
A user on lemmy on lemmy commenting on a post from a mailinglist would be automatically signed up to the mailinglist with a user email address that's dynamically created (I think your email has to be signed up otherwise the mailinglist rejects it). Upon successful signup, the response would be sent using their email address to the maillinglist thread.
The other way around, a comment would show up on lemmy with email address and username of the person that responded on the mailinglist.
(10 minutes later) After writing it out, I'm not sure it's what you're doing and more like a bridge, but maybe it'll inspire you. Who knows. There's probably something I'm missing and probably this isn't even what your intention was when you started out with this.
Anyway, do your thing dude and have fun!
CC BY-NC-SA 4.0
Hey mate thanks for writing all that down. Gives me a few ideas - in particular how NNTP could fit in to the equation.
LKML can be accessed by a usenet client at nntp.lore.kernel.org. In theory, then, it should be possible to at least read both LKML and ActivityPub stuff hosted at the same NNTP server. To get that working means making sure all the conversion and mapping of concepts are as clean as possible. It's a good test!
Thanks again!