<?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 for leŭksman</title>
	<atom:link href="http://leuksman.com/log/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://leuksman.com/log</link>
	<description>reticula, electronica, &#38; oddities</description>
	<lastBuildDate>Sun, 07 Mar 2010 14:34:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Printing from Mac to Linux: the cheat sheet by John Russell</title>
		<link>http://leuksman.com/log/2010/02/26/printing-from-mac-to-linux-the-cheat-sheet/comment-page-1/#comment-44709</link>
		<dc:creator>John Russell</dc:creator>
		<pubDate>Sun, 07 Mar 2010 14:34:04 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=705#comment-44709</guid>
		<description>Thanks for the excellent guide!  It also works perfectly for printing Linux-to-Linux!</description>
		<content:encoded><![CDATA[<p>Thanks for the excellent guide!  It also works perfectly for printing Linux-to-Linux!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Printing from Mac to Linux: the cheat sheet by Sage</title>
		<link>http://leuksman.com/log/2010/02/26/printing-from-mac-to-linux-the-cheat-sheet/comment-page-1/#comment-44238</link>
		<dc:creator>Sage</dc:creator>
		<pubDate>Fri, 26 Feb 2010 22:17:56 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=705#comment-44238</guid>
		<description>Printing has been our one major headache (aside from OpenOffice Impress) since switching to Linux for all our computers a few months back.  Network printing works sometimes, but it&#039;s really hard to predict when it will quit and why.</description>
		<content:encoded><![CDATA[<p>Printing has been our one major headache (aside from OpenOffice Impress) since switching to Linux for all our computers a few months back.  Network printing works sometimes, but it&#8217;s really hard to predict when it will quit and why.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Time zones: do we really need them? 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>Comment on Time zones: do we really need them? 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>Comment on Time zones: do we really need them? 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>Comment on Time zones: do we really need them? 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>
	<item>
		<title>Comment on Location fuzzing in StatusNet by brion</title>
		<link>http://leuksman.com/log/2009/12/19/location-fuzzing-in-statusnet/comment-page-1/#comment-40699</link>
		<dc:creator>brion</dc:creator>
		<pubDate>Sat, 26 Dec 2009 21:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=674#comment-40699</guid>
		<description>There&#039;s some talk of that, yes...</description>
		<content:encoded><![CDATA[<p>There&#8217;s some talk of that, yes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Location fuzzing in StatusNet by Arjun Ram</title>
		<link>http://leuksman.com/log/2009/12/19/location-fuzzing-in-statusnet/comment-page-1/#comment-40483</link>
		<dc:creator>Arjun Ram</dc:creator>
		<pubDate>Sun, 20 Dec 2009 01:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=674#comment-40483</guid>
		<description>Why not allow fire eagle integration? Fire eagle handles location accuracy by default. It already is a location broker. Thoughts? My 2p.</description>
		<content:encoded><![CDATA[<p>Why not allow fire eagle integration? Fire eagle handles location accuracy by default. It already is a location broker. Thoughts? My 2p.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Confusing Twitter settings by brion</title>
		<link>http://leuksman.com/log/2009/12/03/confusing-twitter-settings/comment-page-1/#comment-39587</link>
		<dc:creator>brion</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:47:29 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=651#comment-39587</guid>
		<description>The system we&#039;ve currently got can only pull updates by polling Twitter&#039;s API, user by user. Ok for a small site but not very pleasant for a larger one; it&#039;d just take too long and might end up tripping too many requests from Twitter. ;) We hope to do this more cleanly with real-time push updates if we can get something working cleanly...</description>
		<content:encoded><![CDATA[<p>The system we&#8217;ve currently got can only pull updates by polling Twitter&#8217;s API, user by user. Ok for a small site but not very pleasant for a larger one; it&#8217;d just take too long and might end up tripping too many requests from Twitter. <img src='http://leuksman.com/log/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  We hope to do this more cleanly with real-time push updates if we can get something working cleanly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Confusing Twitter settings by derschreckliche</title>
		<link>http://leuksman.com/log/2009/12/03/confusing-twitter-settings/comment-page-1/#comment-39586</link>
		<dc:creator>derschreckliche</dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://leuksman.com/log/?p=651#comment-39586</guid>
		<description>Good suggestions.
I would probably add an &quot;if they have an account on %%site.name%%&quot; to the first, but your idea is still much better than the one used now.

BTW: Do you know why &quot;Import my friends timeline.&quot; is disabled on identi.ca ?</description>
		<content:encoded><![CDATA[<p>Good suggestions.<br />
I would probably add an &#8220;if they have an account on %%site.name%%&#8221; to the first, but your idea is still much better than the one used now.</p>
<p>BTW: Do you know why &#8220;Import my friends timeline.&#8221; is disabled on identi.ca ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
