Date | Commit message (Collapse) |
|
Inspired by interest in LKML archival:
https://public-inbox.org/meta/d5546b24-5840-4ae9-d25b-5e3e737ed73b@linuxfoundation.org
|
|
Always plenty to do while working on this...
|
|
This will allows certain feed readers to render a message thread
as described in <https://www.jwz.org/doc/threading.html>.
Feed readers with knowledge of of RFC 4685 are unknown to us at
this time, but perhaps this will encourage future implementations.
Existing feed readers I've tested (newsbeuter, feed2imap) seem
to ignore these tags gracefully without degradation.
|
|
Do not require users to have network access to know what
the link refers to.
|
|
The existing string -> number date range Xapian query is good
enough, and having too much flexibility is probably bad for
caching (as well as increasing our attack surface, because
parsing queries is tricky).
Tags-as-skiplists are probably not worth the effort given
Xapian, and we may have to import old messages after-the-fact,
anyways, and message delivery for mirrors is never orderly.
Other items are all done and need to be maintained (like the
search engine docs for the mairix-compatibility features that
just got pushed out)
|
|
Plenty more to do!
|
|
I bet there's a billion other improvements to be made elsewhere.
|
|
|
|
This should be more accessible to readers on narrow terminals
(or giant fonts) while providing a chronological view which
is also aware of message threading relationships.
|
|
"git cat-file --batch" seems expensive for big repos and
loading 70K+ tree objects in git isn't all that fast.
Ideas are cheap, time, code, and testing are not :P
|
|
It would be too much of a burden for caching system when
user-supplied CSS is more powerful.
|
|
Some readers will want to use "HTTPS Everywhere" conveniently;
and I will support it.
|
|
Unfortunately, most users still prefer their mail delivered
over SMTP; so we'll at least document mlmmj integration for now
until we can popularize pull-based reading over POP3/NNTP/ssoma.
|
|
Email addresses get out-of-date, so make sure they're mapped
properly for future readers. git and linux-kernel already have
an established convention for this, so we will follow it.
|
|
|
|
Sometimes I contribute to projects with centralization-inducing
things like reply-to-list and bug trackers.
I dislike those things myself, but most of the time I can deal with
them... for now.
|
|
Strongly emphasize decentralization, as that was actually the
main impetus for my interest in git.
|
|
Of course, we need to figure out if RFC 4685 is supported anywhere,
first.
|
|
Because some folks will want to receive email.
|
|
While we're at it, fix up a typo.
|
|
Screen space is precious, and we do not need it in the abbreviated
view.
|
|
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.
|