True---I keep a list on my Palm Pilot of those clocks around the house that need resetting. The current count is nineteen, not including the ones that handle the transition themselves, and I need it to avoid gaslighting myself. (There was that year I took my daughter to Sunday school an hour early....)

Exactly this situation arose in the Feist case. Rural Telephone Service compiled a list of its subscribers, Feist incorporated it into their book, and RTS sued. And lost. You can't copyright facts (thank God---imagine a world in which you could). There has to be some creative element, no matter how much ``sweat of the brow'' was expended. An alphabetic list of phone subscribers contains no creativity.

During WW II, Britain adopted Double Summer Time, skipping ahead two hours. It reverted to one hour after the war (modulo some funkiness a year or so later).

The above comment should have been in reply to the first comment, asking about Y2K-like problems.

Unix & friends use a file or set of files with daylight-saving time changes; it's updated everytime somebody changes things. In Debian, it's in the tzdata package, described thus:

This package contains data required for the implementation of standard local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules.

Every time (*ahem*) some gov't tweaks the rules, the new info is encoded, and the updated package is sent out. Note that the superseded info is retained, so that if you ask about a time in 1974 in New York City, it'll adjust correctly for the idiotic Nixonian ``let's all go to work in the dark'' time.

Debian's files live under /usr/share/zoneinfo, and amount to a bit over 6MB of data.

From the article:

HyperSolar's next step will be to produce an actual physical prototype, and see if it works as envisioned.

Wake me when they have something resembling results.

Which says it's a trade secret only if you do your best to keep it a secret. Since Sony's now published the info themselves, the judge should throw out the suit against Geohot et al. (Who's Al, by the way?)

Now I'm waiting impatiently for my hardware store to get in a new supply of snow rakes, nervously listening for the sound of water dripping into the attic.

True—there is literally no limit[1] to how much you can be in debt by shorting; you can only lose everything you own, less what the bankruptcy court leaves you.
—————
[1] Yeah, there's a limit to the double-precision variable holding the account's value, but let's not go there.

That's why I don't recommend people short.

To be more detailed, there is literally no limit to how much you can lose by shorting.

When you simply buy a stock, the most you can lose is what you paid for it. If the company goes bankrupt, the stock price can't go below $0.00.

If you short a stock, you're borrowing shares to sell now, betting that the replacements you need to return later will be cheaper, and you get to keep the difference. But, if the price goes up, there's no limit. You still need to buy the replacement shares, at whatever they cost then—there is no way to know how much you might lose if you bet wrong.