<?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"
	>
<channel>
	<title>Comments for Rimantas' murmurs</title>
	<atom:link href="http://rimantas.com/en/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://rimantas.com/en</link>
	<description>ImCat online</description>
	<pubDate>Fri, 05 Sep 2008 22:29:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>Comment on The Way the .mobi Died by Develops.mobi &#187; What does the iPhone mean for dotMobi?</title>
		<link>http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2756</link>
		<dc:creator>Develops.mobi &#187; What does the iPhone mean for dotMobi?</dc:creator>
		<pubDate>Sat, 13 Jan 2007 03:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2756</guid>
		<description>[...] A number of people have discussed the impact of Apple&#8217;s iPhone announcement on the purpose of the .mobi top-level domain. For my first post, I thought it would be an intriguing topic to tackle. [...]</description>
		<content:encoded><![CDATA[<p>[...] A number of people have discussed the impact of Apple&#8217;s iPhone announcement on the purpose of the .mobi top-level domain. For my first post, I thought it would be an intriguing topic to tackle. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Way the .mobi Died by dotMobi</title>
		<link>http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2755</link>
		<dc:creator>dotMobi</dc:creator>
		<pubDate>Fri, 12 Jan 2007 16:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2755</guid>
		<description>&lt;strong&gt;What does the iPhone mean for dotMobi?...&lt;/strong&gt;

A quick word of introduction: I'm James Pearce, the new dotMobi CTO. I've been working with the mobile web for over seven years now, and I'm excited about this. 2007 feels like it really could be the year that the...</description>
		<content:encoded><![CDATA[<p><strong>What does the iPhone mean for dotMobi?&#8230;</strong></p>
<p>A quick word of introduction: I&#8217;m James Pearce, the new dotMobi CTO. I&#8217;ve been working with the mobile web for over seven years now, and I&#8217;m excited about this. 2007 feels like it really could be the year that the&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Way the .mobi Died by Rimantas</title>
		<link>http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2754</link>
		<dc:creator>Rimantas</dc:creator>
		<pubDate>Thu, 11 Jan 2007 16:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2754</guid>
		<description>If I got it right this only becomes a problem for extremely wide content. Text columns in fixed width layouts are typically about 400-600px. iPhone's screen is 480px wide (landscape orientation) so you will be able to read this blog without downscaling - content column is 450px wide. Given that at  50% zoom text is still readable you should be able to deal even insanely long lines.</description>
		<content:encoded><![CDATA[<p>If I got it right this only becomes a problem for extremely wide content. Text columns in fixed width layouts are typically about 400-600px. iPhone&#8217;s screen is 480px wide (landscape orientation) so you will be able to read this blog without downscaling - content column is 450px wide. Given that at  50% zoom text is still readable you should be able to deal even insanely long lines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Way the .mobi Died by Chionsas</title>
		<link>http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2753</link>
		<dc:creator>Chionsas</dc:creator>
		<pubDate>Thu, 11 Jan 2007 09:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2007/01/11/the-way-the-mobi-died/#comment-2753</guid>
		<description>Though the iPhone is great, I see a problem with the web page zooming feature. When you get closer to the text (so it is readable), you only see some limited area of the page. When the paragraphs are wide and the text lines are long, you'll need to scroll horizontally in order to read the content. And even worse - you'll need to scroll back in order to get to the begining of the next line :)
I get this all the time on my native SE browser (which renders XHTML quite properly, byt the way). And that is the main reason I use Opera mini (and the bandwidth consumption is the other reason, naturally :)

just my .02</description>
		<content:encoded><![CDATA[<p>Though the iPhone is great, I see a problem with the web page zooming feature. When you get closer to the text (so it is readable), you only see some limited area of the page. When the paragraphs are wide and the text lines are long, you&#8217;ll need to scroll horizontally in order to read the content. And even worse - you&#8217;ll need to scroll back in order to get to the begining of the next line :)<br />
I get this all the time on my native SE browser (which renders XHTML quite properly, byt the way). And that is the main reason I use Opera mini (and the bandwidth consumption is the other reason, naturally :)</p>
<p>just my .02</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google does not follow by windows</title>
		<link>http://rimantas.com/en/archives/2005/01/21/google-does-not-follow/#comment-95</link>
		<dc:creator>windows</dc:creator>
		<pubDate>Sun, 13 Feb 2005 16:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2005/01/21/google-does-not-follow/#comment-95</guid>
		<description>Three rules for the spam game:

1) you can not win.  
2) you can not draw.  
3) you can not leave the play.  

Greetings,

Antonio, from Malaga (Spain)</description>
		<content:encoded><![CDATA[<p>Three rules for the spam game:</p>
<p>1) you can not win.<br />
2) you can not draw.<br />
3) you can not leave the play.  </p>
<p>Greetings,</p>
<p>Antonio, from Malaga (Spain)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google does not follow by Aidas Kasparas</title>
		<link>http://rimantas.com/en/archives/2005/01/21/google-does-not-follow/#comment-76</link>
		<dc:creator>Aidas Kasparas</dc:creator>
		<pubDate>Fri, 21 Jan 2005 12:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2005/01/21/google-does-not-follow/#comment-76</guid>
		<description>Rimantas,

for what problem do you want a solution?
a) make your blog spam free;
b) do (a) effortlessly;
c) do (b) for every blog site;
d) achieve (c) once and forever;
e) achieve (d) for every form of communication, not just blog.

Also, would you consider solving a problem 90% victory or defeat?
If you want (e) and 100%+, then I'm afraid there is no silver bulet. But if you think that every step which makes spammers extra problem without harm to the good guy, it's worth doing, then read on I have few [teoretical] thought.

First, (a) is achievable by allowing only proofread and approved comments. I don't know is that acceptable according to moral codex of blogger. But goal is achievable 100%. If 90% solution is acceptable, then maybe you can let your readers to help your other readers to avoid visiting spammers by implementing some vote system.

Granted, this requires resources to implement. Can you automate that? Of course, it requires testing, but how about checking comment and contents of the links in it against SA's database which you use for e-mail? After some training I think good portion of spam would be filtered out. Remaining could be dealt using manual methods.

Goals (c)-(e) are somethere beyound horizon, but to aproach to them I don't see any other way than methodically cutting opportunities for spammers and lowering their revenue:expences rate.

And if all your post is about yet another case where marketoids won over techies, then I'm saddened by that fact no less than you. Do you have solution for this problem? :-)</description>
		<content:encoded><![CDATA[<p>Rimantas,</p>
<p>for what problem do you want a solution?<br />
a) make your blog spam free;<br />
b) do (a) effortlessly;<br />
c) do (b) for every blog site;<br />
d) achieve (c) once and forever;<br />
e) achieve (d) for every form of communication, not just blog.</p>
<p>Also, would you consider solving a problem 90% victory or defeat?<br />
If you want (e) and 100%+, then I&#8217;m afraid there is no silver bulet. But if you think that every step which makes spammers extra problem without harm to the good guy, it&#8217;s worth doing, then read on I have few [teoretical] thought.</p>
<p>First, (a) is achievable by allowing only proofread and approved comments. I don&#8217;t know is that acceptable according to moral codex of blogger. But goal is achievable 100%. If 90% solution is acceptable, then maybe you can let your readers to help your other readers to avoid visiting spammers by implementing some vote system.</p>
<p>Granted, this requires resources to implement. Can you automate that? Of course, it requires testing, but how about checking comment and contents of the links in it against SA&#8217;s database which you use for e-mail? After some training I think good portion of spam would be filtered out. Remaining could be dealt using manual methods.</p>
<p>Goals (c)-(e) are somethere beyound horizon, but to aproach to them I don&#8217;t see any other way than methodically cutting opportunities for spammers and lowering their revenue:expences rate.</p>
<p>And if all your post is about yet another case where marketoids won over techies, then I&#8217;m saddened by that fact no less than you. Do you have solution for this problem? :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Got a blog? by Richard@Home</title>
		<link>http://rimantas.com/en/archives/2004/10/13/got-a-blog/#comment-75</link>
		<dc:creator>Richard@Home</dc:creator>
		<pubDate>Thu, 20 Jan 2005 18:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2004/10/13/got-a-blog/#comment-75</guid>
		<description>Looking good so far :-) I've added you to my RSS feed list...</description>
		<content:encoded><![CDATA[<p>Looking good so far :-) I&#8217;ve added you to my RSS feed list&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Who cares about ampersands? by pkmk</title>
		<link>http://rimantas.com/en/archives/2004/10/18/who-cares-about-ampersands/#comment-46</link>
		<dc:creator>pkmk</dc:creator>
		<pubDate>Fri, 10 Dec 2004 22:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2004/10/18/who-cares-about-ampersands/#comment-46</guid>
		<description>i also hate this requirement for ampersends,
but most of the time my site is valid ;]</description>
		<content:encoded><![CDATA[<p>i also hate this requirement for ampersends,<br />
but most of the time my site is valid ;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Invalid Standards by Rimantas</title>
		<link>http://rimantas.com/en/archives/2004/10/14/invalid-standards/#comment-5</link>
		<dc:creator>Rimantas</dc:creator>
		<pubDate>Sun, 17 Oct 2004 17:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2004/10/14/invalid-standards/#comment-5</guid>
		<description>Oh, this is tough and saddening :(

Invalid code does not conform to standards -- that's the way it is, wise or not.

"Not mention standards" is very different from saying that invalid code conforms to standards.
It does not matter if your blog is 1% invalid -- it is still better than 1000 valid ones, including this. And you should absolutely talk about standards -- you have best web-oriented blog and thousands are listening (reading, I mean).

And that's why you should be careful with what you say. You say "It is invalid now but I am working on it" -- it is OK. But when someone says "It is not valid, and will never be, so f*** the W3C" -- that's bad. It makes developers comfortable with a thought that invalid code is OK. "Keith said it, Mike said it, ... said it" -- so let's move on.
There is the limit of invalidity? How bad code should be when you will say, "no, that's not acceptable"? Are majority of the web is based on web standards now, cause their code looks much like HTML?
How are we going to have CMS that produce valid code if nobody cares?

Do you agree, that getting valid code is the easiest part of developing the site (I am not talking about maintenance here)? Design, IA or usability is much more difficult to get done right.

And not every site will be a blog with comments system. So if you done it right from the start you shouldn't have much problems later.

If one leaves code cleaning for the better times, that are the chances those times will ever come?

Call me whatever you want. Calling names will not change anything. It will not improve anything. And we are on the same side anyway. Only you choose to emphasize what user sees and interacts, I am trying to say that code is important too.

Or is it? Is Anne right: &lt;a href="http://annevankesteren.nl/archives/2004/10/standards"&gt;there is no point&lt;/a&gt;?</description>
		<content:encoded><![CDATA[<p>Oh, this is tough and saddening :(</p>
<p>Invalid code does not conform to standards &#8212; that&#8217;s the way it is, wise or not.</p>
<p>&#8220;Not mention standards&#8221; is very different from saying that invalid code conforms to standards.<br />
It does not matter if your blog is 1% invalid &#8212; it is still better than 1000 valid ones, including this. And you should absolutely talk about standards &#8212; you have best web-oriented blog and thousands are listening (reading, I mean).</p>
<p>And that&#8217;s why you should be careful with what you say. You say &#8220;It is invalid now but I am working on it&#8221; &#8212; it is OK. But when someone says &#8220;It is not valid, and will never be, so f*** the W3C&#8221; &#8212; that&#8217;s bad. It makes developers comfortable with a thought that invalid code is OK. &#8220;Keith said it, Mike said it, &#8230; said it&#8221; &#8212; so let&#8217;s move on.<br />
There is the limit of invalidity? How bad code should be when you will say, &#8220;no, that&#8217;s not acceptable&#8221;? Are majority of the web is based on web standards now, cause their code looks much like HTML?<br />
How are we going to have CMS that produce valid code if nobody cares?</p>
<p>Do you agree, that getting valid code is the easiest part of developing the site (I am not talking about maintenance here)? Design, IA or usability is much more difficult to get done right.</p>
<p>And not every site will be a blog with comments system. So if you done it right from the start you shouldn&#8217;t have much problems later.</p>
<p>If one leaves code cleaning for the better times, that are the chances those times will ever come?</p>
<p>Call me whatever you want. Calling names will not change anything. It will not improve anything. And we are on the same side anyway. Only you choose to emphasize what user sees and interacts, I am trying to say that code is important too.</p>
<p>Or is it? Is Anne right: <a href="http://annevankesteren.nl/archives/2004/10/standards">there is no point</a>?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Invalid Standards by Keith</title>
		<link>http://rimantas.com/en/archives/2004/10/14/invalid-standards/#comment-4</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Sun, 17 Oct 2004 04:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://rimantas.com/en/archives/2004/10/14/invalid-standards/#comment-4</guid>
		<description>You say "Only do me a favour – do not say that invalid code conforms to standards."

Is that wise?  I mean my site is 99% valid.  I've got a problem with my comments, which are essential to my site and I've actually spent quite a bit of time trying to sort that out.  It's not possible without sacrificing functionality.  Period.  So I've got to choose between validity and functionality.  I chose functionality.

Now, back to your favor.  Should I now not mention standards on my site because I have a few valid pages?  Fine by me, but I don't see how this HELPS the cause of Web standards.  If anything by alientating folks like me and Mike (and many, many more) all you're doing is hurting the "cause."

As of now, I've removed my validation links.  I've got absolutley no problem not supporting Web standards.  I'll leave that to the Zealots.</description>
		<content:encoded><![CDATA[<p>You say &#8220;Only do me a favour – do not say that invalid code conforms to standards.&#8221;</p>
<p>Is that wise?  I mean my site is 99% valid.  I&#8217;ve got a problem with my comments, which are essential to my site and I&#8217;ve actually spent quite a bit of time trying to sort that out.  It&#8217;s not possible without sacrificing functionality.  Period.  So I&#8217;ve got to choose between validity and functionality.  I chose functionality.</p>
<p>Now, back to your favor.  Should I now not mention standards on my site because I have a few valid pages?  Fine by me, but I don&#8217;t see how this HELPS the cause of Web standards.  If anything by alientating folks like me and Mike (and many, many more) all you&#8217;re doing is hurting the &#8220;cause.&#8221;</p>
<p>As of now, I&#8217;ve removed my validation links.  I&#8217;ve got absolutley no problem not supporting Web standards.  I&#8217;ll leave that to the Zealots.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
