From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 883D21F47D for ; Tue, 7 Mar 2023 22:17:38 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=YKgKI/gR; dkim-atps=neutral Received: by mail-qv1-xf2b.google.com with SMTP id g9so8271089qvt.8 for ; Tue, 07 Mar 2023 14:17:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1678227457; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=uuyFWosdMOykU1CPPKj+1RdfM/18j24e4X9uKQTgbyo=; b=YKgKI/gRSx3zVpPvn6eCYrPA8FYRctVKhND48dmtnhd4Q3zMaRid2Sa41ZGdi/LAhi 6tTK4z+ouJukb+YCVEAzPvGru9rPwjkm/MONgDQobxPoaiTuAFsk8kcfMXM3K7Eg+6ca xWM9hE85cQAXa0l03/wfEXen2Trbn0SctK3/4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678227457; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=uuyFWosdMOykU1CPPKj+1RdfM/18j24e4X9uKQTgbyo=; b=sTgQv6/KYL4FJ9S/RqJCvyRKyHf2m9a+tVaETr5tJe5I3MdYswSzxrQ8PGmd8ESjXe jdM6NK0T3p3izZK+9E+rW6J/yJnBt3tKEmdDR5/zXlvGD+jKKA91sBM3WLkQPd2AmlPX 2pny39KerYxNjmxj58Lkmmrhqf6jRIwDcqceXoCZvi+Dcy2MiHE5ER+wsV6WZU8nCIvk pxG+ID4ww3sg6Yrksy50u36ouLmVMi25XuPzRhWcTEGLte3ZYZLb8MyHtHVHOzQNxlmE rXOzKw+K791QLayehOoSNm2bi9tD5q/wE8y24Vvzc8/FSO1m4OrF7GpsZwwv82srJSED wlnw== X-Gm-Message-State: AO0yUKWLuiC3qBLUSO4YEHwMvilsgQmJhAaukQ+iNkF2sKNWJJj7y7I0 CtLlvDg9daO/CempkTevN8KFQKmkk4GLjR5m/6c= X-Google-Smtp-Source: AK7set9h0CUBIlaSyAaCNqXa8qe753bq1nglpuxylikfdijTMp0qEXV0YE4yI074U0C1P90yJXD6YQ== X-Received: by 2002:a05:6214:d0e:b0:571:314:d725 with SMTP id 14-20020a0562140d0e00b005710314d725mr27264795qvh.49.1678227457435; Tue, 07 Mar 2023 14:17:37 -0800 (PST) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-30-209-226-106-7.dsl.bell.ca. [209.226.106.7]) by smtp.gmail.com with ESMTPSA id c194-20020a379acb000000b0071aacb2c76asm10112417qke.132.2023.03.07.14.17.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Mar 2023 14:17:36 -0800 (PST) Date: Tue, 7 Mar 2023 17:17:35 -0500 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: ActivityPub <=> email bridge? Message-ID: <20230307221735.arhy7xt6ciz5djni@meerkat.local> References: <20190330014915.o2hw333fjotxkrjy@dcvr> <20230307221210.M598524@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230307221210.M598524@dcvr> List-Id: 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