From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Cc: Ben Zanin <bzanin@gmail.com>
Subject: notes on potential standalone-ish AP support
Date: Thu, 27 Mar 2025 22:41:43 +0000 [thread overview]
Message-ID: <20250327224143.M385019@dcvr> (raw)
Eric Wong <e@80x24.org> wrote:
> IOW, we'd support a public-inbox-ap-v0-format independent of the
> existing v1 and v2 mail-only formats.
...
> Now, AP also supports (or encourages) a lot of things I disagree
> with (namely images/video) and those don't fit well with git.
> More on that in a separate reply...
Storage format:
* JSON for text content instead of raw RFC{822,2822,5322} messages
* Non-text attachments could probably use git-lfs or similar and
probably referred to by git SHA-256 blob OID
I don't know much about git-lfs, is it appropriate for this?
Or some global DHT storage thing (IPFS?, I don't know...).
WWW implementation:
* support POST to write messages to storage; -httpd/netd
would need R/W access to AP inboxes...
* any HTTP requests made by the WWW server needs to support
SOCKS for Tor or SSH tunnels
* not sure how to support anti-spam, extract text + URLs
from posts and feed to SpamAssassin?
WWW display:
* no inline images/audio/video + deeplinking prevention;
same as current WWW mail UI
* text wrap options via URL parameter or opt-in cookie?
Maybe use the old <tt> tag instead of <pre>
(might go for some mails, too...)
* linkify emojis to text names for non-GUI terminal users
(using charnames::viacode, should probably be done to the existing
WWW mail UI as well since emojis are a problem in mail, too)
NNTP|IMAP|POP3 support for AP:
* done last
....
reply other threads:[~2025-03-27 22:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250327224143.M385019@dcvr \
--to=e@80x24.org \
--cc=bzanin@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).