| Date | Commit message (Collapse) |
|---|
|
Letz trie 2 uphear liter8
|
|
Setting the "In-Reply-To:" header via mailto: links is not
well-supported and should probably not be encouraged unless
the client situation improves.
So instead, teach users more widely-supported ways of setting
the In-Reply-To: header to ensure proper threading of replies.
|
|
This requires POST and (small file) upload support from the
PSGI/Plack web server. CGI.pm is currently not supported with
this feature.
We'll serve everything git can handle by default for performance
in the general case.
To avoid introducing cognitive overhead for sysadmins managing
existing HTTP backends, we do not introduce new configuration
directives.
Thus, setting http.uploadpack=false in the relevant git config
file for each public-inbox (ssoma) git repo will disable smart
HTTP for CPU/memory-constrained systems.
Technically we could support http.receivepack to allow posting
messages to a public-inbox over HTTP(S), but that breaks
the public-inbox model of encouraging users to Cc: everyone.
Again, we encourage users to Cc: everyone to reduce the chance
of a public-inbox becoming a centralized point of
failure/censorship.
|
|
Add a few newlines for readability (perhaps at the expense of
economy). Stop mentioning "Open Source" as it is redundant
and "Free Software" fits our goals, better.
|
|
This project is currently implemented in Perl, and pod2man is
probably more common among potential users and developers of
this project.
|
|
HTML has one major advantage over plain text: <a href=...> links
That's about it.
|
|
Shorter URLs are easier to read, remember, and more efficient.
|
|
That's right, we now have our NNTP server running and are
self-hosting a read-only news gateway at:
nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
|
|
In the future, it should be possible to use this:
git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \
UPDATE_COPYRIGHT_USE_INTERVALS=2 \
xargs /path/to/gnulib/build-aux/update-copyright
|
|
Despite best intentions, things like strike-throughs and italics
won't render well and will harm accessibility.
|
|
This allows common /m/ links to be used without a prefix,
saving 2 precious bytes for permalinks and raw messages.
Old URLs continue to redirect.
|
|
The MIME type entry for Atom feed relies on "atom",
so allow properly-configured static file servers to serve
it with the correct Content-Type header.
|
|
This allows users to subscribe to only a single thread
with their feed reader without subscribing to the rest of
the thread.
Update our endpoint notes while we're at it.
|
|
This improves compatibility and allows individual messages
to be concatenated into an existing mbox without further
modifications. "git format-patch" does something similar
(but does not do "From " line escaping(!))
|
|
Threading in Xapian is mostly supported by now; so start
documenting things.
|
|
Table rendering in lynx is crap compared to w3m and links.
However, we still use it for filtering HTML since the renderer
is otherwise nice...
|
|
SpamAssassin queries URI blacklists, so it's probably OK
to start generating links in the future...
|
|
This allows us to generate links without caring about discoverability
and remains reasonably WYSIWYG for folks editing our documentation in
their favorite $EDITOR
|
|
Occasionally we'll use these for links.
|
|
|
|
Some readers may not be familiar with ssoma internals such as
ssoma-rm.
|
|
Some of these projects are not well known, so link to them
to help new users.
|
|
Even with txt2pre, the maintenance/discoverability burden is too
high and lynx still uses too much memory. Unfortunately, we'll have
to keep our INSTALL.html for a while longer on the server since it's
linked, but not index.html!
|
|
Hopefully this simplifies and corrects our usage of Perl encoding
APIs.
|
|
While we're at it, make sure strange characters are escaped properly
in Message-IDs. We'll need tests for all this behavior.
|
|
This is not a blog. All posts, whether replies or not,
carry equal weight.
|
|
Document some of the stranger choices I've made.
|
|
The ~/.dc-dlvr.pre script for my public-inbox user does this.
|
|
It should be common for a single users to be subscribed to multiple
addresses/lists, so we must use the address before alias expansion.
This partially reverts commit b949afc9edf89dd494cac6255c78b124d58e11a5
|
|
We have an HTML homepage, OMG!
|
|
The emergency destination may be Maildir. A Maildir emergency
destination is better for volatile data which is written to
and deleted-from frequently.
|
|
This allows WWW readers to slowly page through the entire history
of the mailing list.
|
|
Fortunately, most mailing lists will never grow too large.
|
|
Hopefully this makes the scope and intent of the project clearer.
|
|
Laziness \o/
(Then impatience and hubris :)
|
|
We'll probably support these so they're easier-to-type and share.
|
|
Remove the specified /all.html while we're at it, we only have
/all.atom.xml because it's convenient for feed readers.
|
|
Message-IDs are extremely long already, so try to keep them short here.
|
|
Hopefully a little easier to find for clients and not admins running
servers. While we're at it, expand design_notes.
|
|
Things to keep in mind when working on this.
|
|
Most notably, the INSTALL is geared towards potential server admins,
whereas the README is also for interested "drive-by" readers.
|
|
We serve the short, abridge-quote version by default since
it is (unfortunately) common practice to over-quote on mailing lists.
|
|
This still needs to be fleshed out.
|
|
Mainly, start with URL routes since that's what users usually
see, first.
|
|
|
|
|