<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Time zones: do we really need them?</title>
	<atom:link href="http://leuksman.com/log/2009/12/29/time-zones-do-we-really-need-them/feed/" rel="self" type="application/rss+xml" />
	<link>http://leuksman.com/log/2009/12/29/time-zones-do-we-really-need-them/</link>
	<description>reticula, electronica, &#38; oddities</description>
	<lastBuildDate>Tue, 13 Jul 2010 23:40:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Sean Whitton</title>
		<link>http://leuksman.com/log/2009/12/29/time-zones-do-we-really-need-them/comment-page-1/#comment-41192</link>
		<dc:creator>Sean Whitton</dc:creator>
		<pubDate>Mon, 04 Jan 2010 22:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=683#comment-41192</guid>
		<description>You could still have the selection box, but an onLoad hook or somesuch that, if JS is enabled, changes it from &#039;please select&#039; to &#039;auto-detect&#039; and then you satisfy every browser (and those who might want to manually set a timezone) and make it easy for others.</description>
		<content:encoded><![CDATA[<p>You could still have the selection box, but an onLoad hook or somesuch that, if JS is enabled, changes it from &#8216;please select&#8217; to &#8216;auto-detect&#8217; and then you satisfy every browser (and those who might want to manually set a timezone) and make it easy for others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dami</title>
		<link>http://leuksman.com/log/2009/12/29/time-zones-do-we-really-need-them/comment-page-1/#comment-40892</link>
		<dc:creator>Dami</dc:creator>
		<pubDate>Wed, 30 Dec 2009 02:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=683#comment-40892</guid>
		<description>While this might not work for everyone, I&#039;m fairly certain that you could correlate geo-IP data with time-zone data of the notices. 
(The slight extra information this would result in in addition to the UTC time is that you could see if someone was &quot;denting&quot;, for example, in the middle of the night...)</description>
		<content:encoded><![CDATA[<p>While this might not work for everyone, I&#8217;m fairly certain that you could correlate geo-IP data with time-zone data of the notices.<br />
(The slight extra information this would result in in addition to the UTC time is that you could see if someone was &#8220;denting&#8221;, for example, in the middle of the night&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aryeh Gregor</title>
		<link>http://leuksman.com/log/2009/12/29/time-zones-do-we-really-need-them/comment-page-1/#comment-40891</link>
		<dc:creator>Aryeh Gregor</dc:creator>
		<pubDate>Wed, 30 Dec 2009 01:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=683#comment-40891</guid>
		<description>I think the best way to do it is have a server-side preference, but keep it updated via JS.  On registration, have JavaScript autodetect the right setting and submit it.  Thereafter, maybe even on every page load, you could check the user&#039;s preferred timezone and compare via JS against the current system timezone, and update the preference automatically (via AJAX or whatnot) if there&#039;s a mismatch.  Should be a simple variable compare in the common case, no noticeable client-side overhead, and requires no more JS than necessary.

For people whose system time is wrong, or who don&#039;t use JS, you could have a preference somewhere out of the way, with the default being &quot;Autodetect using JavaScript&quot;.</description>
		<content:encoded><![CDATA[<p>I think the best way to do it is have a server-side preference, but keep it updated via JS.  On registration, have JavaScript autodetect the right setting and submit it.  Thereafter, maybe even on every page load, you could check the user&#8217;s preferred timezone and compare via JS against the current system timezone, and update the preference automatically (via AJAX or whatnot) if there&#8217;s a mismatch.  Should be a simple variable compare in the common case, no noticeable client-side overhead, and requires no more JS than necessary.</p>
<p>For people whose system time is wrong, or who don&#8217;t use JS, you could have a preference somewhere out of the way, with the default being &#8220;Autodetect using JavaScript&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://leuksman.com/log/2009/12/29/time-zones-do-we-really-need-them/comment-page-1/#comment-40882</link>
		<dc:creator>David Gerard</dc:creator>
		<pubDate>Tue, 29 Dec 2009 23:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=683#comment-40882</guid>
		<description>UTC Forever! If it&#039;s good enough for Wikimedia, it&#039;s good enough for everybody! The mere detail that I live in UTC+0 is neither here nor there.</description>
		<content:encoded><![CDATA[<p>UTC Forever! If it&#8217;s good enough for Wikimedia, it&#8217;s good enough for everybody! The mere detail that I live in UTC+0 is neither here nor there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
