unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: ActivityPub <=> email bridge?
Date: Tue, 7 Mar 2023 17:17:35 -0500	[thread overview]
Message-ID: <20230307221735.arhy7xt6ciz5djni@meerkat.local> (raw)
In-Reply-To: <20230307221210.M598524@dcvr>

On Tue, Mar 07, 2023 at 10:12:10PM +0000, Eric Wong wrote:
> > Something tells me that if ActivityPub reaches high-enough
> > adoption levels; it'll have to deal with a spam problem that
> > email folks have been dealing with for decades, too.
> > 
> > So ActivityPub seems like a duplicated effort as far as it's use
> > for messaging for software development goes...
> 
> Still true, but it seems to have caught on, lately...
> 
> If we manage to try this, it'll be using AP as a transport layer
> and still requiring plain-text and RFC5322 (or 822/2822) plain-text
> messages compatible with git-am.

I'm not sure about the bridge, but I would very much welcome ability to
archive activitypub messages in a public-inbox archive, with full threading.

> That would allow SpamAssassin or similar to perform spam
> filtering w/o modification.
> 
> Allowing markup or images from arbitrary posters is a nightmare
> in terms of spam, phishing and illegal content, though; so
> normal mailing list etiquette still applies.

Perhaps it's possible to allow attachments from specific instances, but the
default for any federated content is just plaintext content?

-K

  reply	other threads:[~2023-03-07 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30  1:49 ActivityPub <=> email bridge? Eric Wong
2023-03-07 22:12 ` Eric Wong
2023-03-07 22:17   ` Konstantin Ryabitsev [this message]
2023-03-07 22:25     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230307221735.arhy7xt6ciz5djni@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).