Breaking: it's valid
The latest news, according to this mozilla.dev news group thread, is that the certificate is valid:
13 publicly visible posts • joined 1 Jun 2008
Oh hay, armchair admin!
Fancy posting the addresses of all the systems you're responsible for online, so that interested parties can check you're following all the "best practice"?
No? Didn't think so.
Apache are to be commended for coming clean, making amends, and explaining their policy in the way that they have.
Well, pretty clearly there's no need for them to return if they can send the information they need home.
I read an interesting comment on a Wired article on this subject from an attendee who suggested there was a legitimate machine directly adjacent that was reporting a network fault. He suspected that the dodgy ATM might have been ferrying back the details over a network connection stolen from the other machine, which seems perfectly reasonable.
In the process of trying to make OFDM more palatable to a non-comms audience, you seem to have missed the real advantage of the technique. The real beauty of OFDM is the flexibility given by so many orthogonal low-bandwidth sub-carriers: you can avoid the problem of frequency-selective fading for one user (mitigating their bad channel) by moving their allocation in the spectrum. This leads to much more efficient usage of spectrum, and better channels for all. It is excellent at adapting to nasty channel conditions in slowly-changing channels*.
I'm not really sure what you're getting at with regards to "solving" the problem of "timing". If you're referring to inter-symbol interference, which is indeed a concern, then OFDM doesn't directly solve this by "putting [chunks] in different frequencies" - but what it does do is ensure that the symbol rate on each individual component frequency is low enough that ISI can be mitigated easily. But if you're referring to interleaving, which does indeed spread "chunks" of data amongst frequencies, then that helps solve a different problem: the issue of losing bursts of data in frequency-specific fades.
On the down side, OFDM really isn't good in channels with a great deal of doppler shift (since it breaks the orthogonality between the sub-carriers) - making it non-ideal for use in fast-moving vehicles, for instance, without specific counter-measures.
Oh please, it's quite clear from context that it refers to an SPL ratio. But yes, it should be a capital 'B'.
In a circumstance where there might be some ambiguity between the units in use (in radio emissions, for instance), then your "concern" might be justified. But in this case it's sound, and failing some conspiracy to confuse you, that means it's SPL.
"When they typed bankofamerica.com into their browser, they'd have no way of knowing whether they were being directed to the real site or one designed to steal their money."
No way of knowing? Try SSL.
If your bank is relying on DNS to prove their identity for online banking, then it's time to take your cash somewhere else.
It's pretty clear O2 didn't do their sums at all, or they would've gone for something other than a totally overkill AJAX RIA and all the server-side state handling those entail.
I'd gladly have stared at the world's most boring, CSS-free, table-ridden Web 1.0 form if it actually let me place an order or, at the very least, use my browser "back" button.