Do you know that kid who seems to be persisting in adolescence far beyond previously known limits?

His name was Constantine.

As they say, archery has a lot of draw backs. 😆

If I were forced to use systemd in a collaborative project, I'd probably put it in a QEMU sandbox and blast it to smithereens afterwards.

The weather forecast predicted a major storm, but it turned out to be only a tempest in a teapot. It was a brew-tea-ful day!

Once, someone walked under an old tree and suddenly a branch broke off and knocked him unconscious.

Tree strikes and you're out!

A chicken and an egg walked into a bar. The bartender asked, Which of you is first?

Unfortunately, the question is unanswered. 😜

Well, the problem is that I only know 25 letters of the alphabet. I don't know Y.

Tree-structured threads are not perfect, but are miles better than linear threads.  I'm subscribed to several high-volume mailing lists, and if I hadn't used Mutt, which has threading, it would have been completely unmanageable. Threading often alleviates the need to overquote, because it's clear from its position within the tree which post it's replying to.  (Try imagining Usenet without threads. The resulting chaos would be several orders of magnitude worse than all the flame wars!)

The ideal structure is a DAG (directed acyclic graph), but it's too complex to be practical, both in terms of presentation, navigation, and usage (nobody is as obsessive as I am in tagging individual posts to respond to within a single reply ), so it's unlikely to work well in practice.  Trees are a good compromise between usability and manageability.

What has this web forum got to do with HTML emails?  (I don't use HTML emails either.)

Unless storage space was a concern, I don't see why the software couldn't be modified such that only the first n lines of a large quoted block are shown by default, and you have to click on some button to display the rest of it. Then it won't clutter the page, and when you need to you can still dig into the quotation to figure out the context of the discussion. The HTML <details> tag is ideal for this sort of thing (you don't even need JS for it to work).

How much bandwidth is required to be a distro release mirror? And what's the average mirror size in terms of disk space?

I have some spare bandwidth I could donate for this purpose. As long as it doesn't use up too much bandwidth and/or disk space.  I'm expecting the disk space requirements are pretty reasonable, since most of the packages would be redirected to the Debian repos, right?

After driving past an accident and getting my tires damaged by glass shards, I now need to replace my car tires.

Fortunately, I have been contributing to my re-tire-ment plan, so I should be covered.