alanback: And what should I do with that? Our time is not the US time. We have own rules for DST.

alanback: The time is currently displayed correctly according to your settings. For example, if you live in the Pacific time zone, Pacific Standard Time (PST) is GMT-8 and Pacific Daylight Time (PDT) is GMT-7. So if you want BrainKing to display PDT, you should have your time zone set to GMT-7.

The bug will appear this coming weekend, when the Czech Republic shifts to summer time and Fencer attempts to redefine Greenwich Mean Time.

KotDB:  I assumed that the bug would disappear this weekend, when the US would have gone on DST if the Congress had not lost its mind, and Europe also goes on DST (if I am not mistaken).  For this reason I did not attempt to reset the time to GMT -7, since that would introduce a new error at the weekend.

I hope Fencer will not be burdened with the task of redefining GMT, which seems pretty well defined as it stands.

I wouldn't waste time trying to change the way the time displays for the remainder of this week.  I just wanted to point out that, due to a change in US DST, whatever algorithms were in place to fix the time display were not displaying the time correctly. 

As a further note, the US government is required to produce a report on whether the early switch to DST (and the late switch back to Standard Time) actually saves energy.  If it does not, then we will revert to normal DST in the future.

alanback: Actually, the US has never switched to DST on the last Sunday of March. From 1987 to 2006, the US switched to DST on the first Sunday of April; from 1966 to 1986, the switch happened on the last Sunday of April (with the exception of 1974 and 1975 when the US switched in January and February).

So even under the old rules, there would still have been a week where just one side of the pond would be on DST.

Having said that, it's a pity that all you can choose from for a timezone is a fixed offset of GMT (although if it would really be a fixed offset of GMT, everyone would have to switch their timezone twice a year as GMT is a fixed timezone without DST). There are publicly available databases with rules for all timezones (the Olson database for instance). But that would lead to a huge drop down list, and many people would get confused and start complaining.

AbigailII: I agree that including DST conventions in the time zone setting would be a nice feature. And it's probably true that some users would be confused and complain. But then some users are already confused and complaining.

But as I see it, the absence of this feature is not the main problem. The main problem is the mismatch between the interface and the functionality of BK's time zone setting. The various options on the Settings page are all described as fixed offsets from GMT, but they are implemented</a> as fixed offsets from Czech time. Thus, whenever the Czech Republic is on summer time, what you set is not what you get.

KotDB: Oops. Sorry about the runaway italics.

Here's an interesting thought: If pawns were allowed to edit their posts, then all the paying members wouldn't have to suffer through my incorrect formatting.