Well, if they really mess up Thunderbird, I can always switch back to Seamonkey.

It would it harder to send a phishing email if you can't use a href tag to hide the real URL, and the user was forced to copy the url and open it in another browser tab.

I've always thought that client side filtering was sufficient to handle spam. That is, the reader decides what articles to filter out rather than relying on a central authority.

In this case, the headlamps are aimed too low. Had they been aimed properly, the pedestrian would have come into view 5 seconds before a possible collision, not 1.5 seconds before.

It also shows that the headlamps are aimed way too low. Properly aimed headlamps should light up an area about 285 feet in front of the vehicle. At 38 mph, the pedestrian would have come into view 5 seconds before a collision instead of the 1.5 seconds shown in the video.

Had the headlamps been aimed properly, they could have. In the video, when the car is traveling at 38 mph (56 feet/second), it takes about 1.5 seconds between the time the pedestrian came into view and when the collision occurred. That means that the headlamps are only lighting up an area 84 feet in front of the vehicle. If the vehicle's headlamps are about 2 feet off the ground, then when they're properly aiimed, they should be lighting up an area about 285 feet in front of the car (VOL headlamps where the left half of the horizontal beam cutoff is 2.1 inches below headlamp height at a distance of 25 feet from the front of the vehicle).

If the pedestrian was visible at 285 feet, it would have taken 5 seconds from the time the pedestrian came into view till when a collision could occur. That would have given the driver a second to react and 4 more seconds to slow down and/or change direction to avoid a collision.

I found that using the XMPP gateway would effectively lock up my client for minutes at a time whenever it reconnected. But it worked fine after it finally managed to connect. I ended up switching to the IRC gateway to avoid the connection issues.

An internally hosted NNTP server would work better than a mailing list.

Usenet also had moderated groups. For a discussion list, moderation may be necessary if there's too much spam or spew directed at the group. But if they were to set up an NNTP server instead and limited who they peer with to limit the spam, then they probably could get away without having to moderate the group at all.

How does that differ from using NNTP to access mailing list archives through a service like gmane? My local email and news client has no problems searching through past messages and is faster than an online forum is.

Usually forums have a subset of markup that's available and it seems to differ from platform to platform (i.e., how do I use bold, italic, or underlined text). For a text based mailing list or newsgroup, the standard was *bold*, /italic/, and _underline_. Some clients would even support that type of informal markup when rendering plain text.

It would be nice if they could set up a NNTP server with an email to NNTP gateway for those who want to continue using email and allow for participants to register for accounts to post to the group. It could peer with gmane for archival purposes.

At least we have gmane for that.

If websites would support the client side TLS certificate for authentication, then you could get 2FA by combining that with a username and password. Browsers have natively supported it for decades.

When you register to vote, you go through the process of generating a client certificate that's used as your registration. The client certificate need not carry any information that identifies you other than the fact that you're a registered voter. When you vote online, you use that client certificate to connect to the server and vote.

Each vote is counted and associated with a certificate. You can look up your record by providing your certificate to check how your votes were counted.

IIRC, the 486 sx processors were clocked at either 25 MHz or 33 MHz (the wikipedia page mentions 16 MHz and 20 MHz versions, but I never had either of those). The math co-processors that you could add on came in either a DX2 or DX4 variety. The DX2 doubled the clock speed (50 MHz or 66 MHz) and the DX4 tripled the clock speed (75 MHz or 100 MHz).

IIRC, it's actually called a Royal burger without reference to the weight in countries that use SI units.

With regards to soft drinks, they've done this for quite a long time (2 L size). Interestingly enough, convenience stores used to sell 20 fl oz size soft drinks, but a couple of years ago, they changed it to 500 mL (20 fl oz is about 591 mL). But they print 16.9 oz on the package rather than 500 mL for some odd reason.