Date | Commit message (Collapse) |
|
IO::Kqueue seems unmaintained, so workaround a long-standing
bug where it falls over on signals:
https://rt.cpan.org/Ticket/Display.html?id=116615
|
|
Since our listen sockets are non-blocking and we may run
multiple httpd|nntpd processes; we need a way to avoid
thundering herds when there are multiple httpd|nntpd worker
processes.
EPOLLEXCLUSIVE was added just for that in Linux 4.5
|
|
These modules are unmaintained upstream at the moment, but I'll
be able to help with the intended maintainer once/if CPAN
ownership is transferred. OTOH, we've been waiting for that
transfer for several years, now...
Changes I intend to make:
* EPOLLEXCLUSIVE for Linux
* remove unused fields wasting memory
* kqueue bugfixes e.g. https://rt.cpan.org/Ticket/Display.html?id=116615
* accept4 support
And some lower priority experiments:
* switch to EV_ONESHOT / EPOLLONESHOT (incompatible changes)
* nginx-style buffering to tmpfile instead of string array
* sendfile off tmpfile buffers
* io_uring maybe?
|
|
and add a note for grokmirror support/integration, too
|
|
The git-users mailing list is on Google Groups with obfuscated
addresses and censored archives. We should allow users to
import them soon, as obfuscated/censored archives are better
than not having archives at all when Google decides to shut down
yet-another-service.
There's also some mangling that (most) instances of Mailman do
(e.g. cgit), but being able to follow such groups over NNTP
and use our search functionality is still useful and better
than what typical Mailman installations provide.
|
|
I'd like to move https://public-inbox.org/git/ to v2; but
cronjobs using "git fetch" to following should not break.
|
|
|
|
Since we now support more CSS classes for coloring,
give this feature more visibility.
|
|
Old and new versions of Mozilla-based browsers seem to support
userContent.css just fine.
cf. https://www-archive.mozilla.org/unix/customizing.html#usercss
http://kb.mozillazine.org/index.php?title=UserContent.css
|
|
We support searching on blob identifiers for a reason :>
|
|
|
|
|
|
And maybe I or somebody else interested will implement it, since
fusedav is abandoned upstream and removed from Debian testing:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840388
Yes, I have fusedav patches at https://bogomips.org/fusedav.git
as noted in the above bug report, but I think davfs2 has more
momentum at the moment.
|
|
Threads are generally discouraged in Perl5, so I won't be using
a dedicated blocking accept4() thread like I would in other
languages.
|
|
Mainly, v2 stuff is done
|
|
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.
|