otl

When you specify To: localtesting@aussie.zone how does the bridge know if you meant https://aussie.zone/c/localtesting or https://aussie.zone/u/localtesting instead?

Good question

The process of going from that email-like address to an ActivityPub Actor (https URL) is done by WebFinger. So whatever we get back from that lookup is who we send the message to. For example, when we look up localtesting@aussie.zone we get this response (truncated for readability):

{
  "rel": "self",
  "type": "application/activity+json",
  "href": "https://aussie.zone/c/localtesting",
  "properties": {
    "https://www.w3.org/ns/activitystreams#type": "Group"
  }
}

The value for type, application/activity+json tells us that we can send ActivityPub stuff to it.

You can play around with WebFinger in the browser.

• your account: https://webfinger.net/lookup/?resource=binomialchicken%40lemmy.blahaj.zone
• my one: https://webfinger.net/lookup/?resource=otl%40apubtest2.srcbeat.com

Hope that makes sense?

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!

Don't tempt me :D

I'd much rather have this put in front of LKML than the terrible interface they have right now.

Interesting. Could you go into this a bit more? Do you mean for example being able to use the Lemmy web UI to read LKML?

Oh wow awesome. Thanks so much!

It needs a bit more fleshing out, removing a bit of hardcoding too. And of course I want to publishit under an open source licence too. Thanks for the tip - I've written it down in the growing TODO file! :)

This is interesting, but have you considered porting to Usenet?

Yes that's on the list! Now that I have a whole bunch of RFC822 files, (in Maildirs) I can also serve them over read-only NNTP. This was the original goal actually - I like the idea of using the simpler protocol NNTP over IMAP to read stuff.

The alternative is something like FediSeer where you can get sites guaranteed by others and block anything not given the all-clear, but that really harms the ability for new sites to appear.

If something like this were to gain lots of traction I'd hope it would be something not too difficult to implement by smaller new sites.

What really sucks is the situation with email now: it's really tricky to get stuff delivered if you're not Google/Microsoft. The barrier to entry is way, way too high :(

The alternative is something like FediSeer where you can get sites guaranteed by others and block anything not given the all-clear, but that really harms the ability for new sites to appear.

If something like this were to gain lots of traction I'd hope it would be something not too difficult to implement by smaller new sites.

What really sucks is the situation with email now: it's really tricky to get stuff delivered if you're not Google/Microsoft. The barrier to entry is way, way too high :(

And ofc the extra spicy sms bridge where an AI gives you an executive summary of your memes for the day

needs more crypto

UNSUBSCRIBE

;)

UNSUBSCRIBE

;)

Thanks for replying from friendica! Confirming message received OK :)