On the other hand, cell phone providers may find it profitable that their users have to pay for all the spam they receive... I believe Docomo can do better in limiting the amount of spam that comes into their system, if they really wanted to.
That is generally correct, but it's like saying every bank robbery starts with somebody walking into a bank.
Sometimes a portscan may be a precursor to an attack, but a few connections to your FTP port, etc. do not necessarily mean you are under attack.
Unicode was originally designed as a pure 16-bit encoding, aimed at representing all modern scripts. (From the FAQ at www.unicode.org.)
Support of characters outside the primary 16-bit plane was added merely an afterthought.
UTF-16 is not limited to 16 bits/char, but it won't work unless many programs properly support surrogate pairs.
Which I think is unlikely, since it would be a rarely used feature.
How about this?
On the other hand, cell phone providers may find it profitable that their users have to pay for all the spam they receive... I believe Docomo can do better in limiting the amount of spam that comes into their system, if they really wanted to.
Hmm... According to the OpenBSD FAQ, www.openbsd.org is running on Solaris.
If you install something like Linux, FreeBSD, or Mach-running-under-VMware-under-OpenBSD, *you are assumed to be able to take care of yourself*.
People doing that most likely will be able to (talking about viruses, not security in general).
Every hack starts with a portscan.
That is generally correct, but it's like saying every bank robbery starts with somebody walking into a bank. Sometimes a portscan may be a precursor to an attack, but a few connections to your FTP port, etc. do not necessarily mean you are under attack.
Unicode was originally designed as a pure 16-bit encoding, aimed at representing all modern scripts. (From the FAQ at www.unicode.org.)
Support of characters outside the primary 16-bit plane was added merely an afterthought. UTF-16 is not limited to 16 bits/char, but it won't work unless many programs properly support surrogate pairs. Which I think is unlikely, since it would be a rarely used feature.
So you propose we write everyithing in HTML 4? (Everyone likes HTML formatted email, I know.)
I could be wrong, but isn't it 'karoshi?' "Work death" would be the translation, I think.
Death from overwork.
(Dying in an accident at work would not be called 'karoshi'.)
Really? There is such a thing as a persistent current. Not that this has anything to do with the story...