<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_11_18_1943209</id>
	<title>Bizarre Droid Auto-Focus Bug Revealed</title>
	<author>timothy</author>
	<datestamp>1258574340000</datestamp>
	<htmltext>itwbennett writes <i>"Pity the poor engineer who had to find this one. One of the more interesting of the handful of bugs that have appeared since the launch of Verizon's Droid smartphone has to do with <a href="http://www.itworld.com/offbeat/85183/bizarre-droid-auto-focus-bug-revealed">the on-board camera's auto-focus</a>. Apparently it just didn't work. And then suddenly it did. Naturally, this off-again, on-again made the theories fly. But the real reason for the bug was <a href="http://www.engadget.com/2009/11/17/motorola-droid-camera-autofocus-fixed-in-secrecy/">revealed in a comment on an Engadget post</a> by someone claiming to be Google engineer Dan Morrill: 'There's a rounding-error bug in the camera driver's autofocus routine (which uses a timestamp) that causes autofocus to behave poorly on a 24.5-day cycle,' said Morrill. 'That is, it'll work for 24.5 days, then have poor performance for 24.5 days, then work again. The 17th is the start of a new 'works correctly' cycle, so the devices will be fine for a while. A permanent fix is in the works.'"</i></htmltext>
<tokenext>itwbennett writes " Pity the poor engineer who had to find this one .
One of the more interesting of the handful of bugs that have appeared since the launch of Verizon 's Droid smartphone has to do with the on-board camera 's auto-focus .
Apparently it just did n't work .
And then suddenly it did .
Naturally , this off-again , on-again made the theories fly .
But the real reason for the bug was revealed in a comment on an Engadget post by someone claiming to be Google engineer Dan Morrill : 'There 's a rounding-error bug in the camera driver 's autofocus routine ( which uses a timestamp ) that causes autofocus to behave poorly on a 24.5-day cycle, ' said Morrill .
'That is , it 'll work for 24.5 days , then have poor performance for 24.5 days , then work again .
The 17th is the start of a new 'works correctly ' cycle , so the devices will be fine for a while .
A permanent fix is in the works .
' "</tokentext>
<sentencetext>itwbennett writes "Pity the poor engineer who had to find this one.
One of the more interesting of the handful of bugs that have appeared since the launch of Verizon's Droid smartphone has to do with the on-board camera's auto-focus.
Apparently it just didn't work.
And then suddenly it did.
Naturally, this off-again, on-again made the theories fly.
But the real reason for the bug was revealed in a comment on an Engadget post by someone claiming to be Google engineer Dan Morrill: 'There's a rounding-error bug in the camera driver's autofocus routine (which uses a timestamp) that causes autofocus to behave poorly on a 24.5-day cycle,' said Morrill.
'That is, it'll work for 24.5 days, then have poor performance for 24.5 days, then work again.
The 17th is the start of a new 'works correctly' cycle, so the devices will be fine for a while.
A permanent fix is in the works.
'"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148194</id>
	<title>New Moon?</title>
	<author>Anonymous</author>
	<datestamp>1257067920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I am so sick of all this Twilight crap...</htmltext>
<tokenext>I am so sick of all this Twilight crap.. .</tokentext>
<sentencetext>I am so sick of all this Twilight crap...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148066</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149544</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257074340000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Really?</p><p>For some reason, this calibre of comment is surprising from a sub-5k uid.</p></htmltext>
<tokenext>Really ? For some reason , this calibre of comment is surprising from a sub-5k uid .</tokentext>
<sentencetext>Really?For some reason, this calibre of comment is surprising from a sub-5k uid.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148200</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148794</id>
	<title>Sounds to me...</title>
	<author>DarthVain</author>
	<datestamp>1257070620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...like a bad motivator.</p></htmltext>
<tokenext>...like a bad motivator .</tokentext>
<sentencetext>...like a bad motivator.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148562</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257069540000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>The support for the camera in the Droid was developed by Motorolla, not Google.</p></htmltext>
<tokenext>The support for the camera in the Droid was developed by Motorolla , not Google .</tokentext>
<sentencetext>The support for the camera in the Droid was developed by Motorolla, not Google.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148160</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>msauve</author>
	<datestamp>1257067680000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Probably not measuring the times per sampling, but measuring the time the focus mechanism is moving. To keep costs down, I suspect the mechanism has no feedback mechanism, so to focus you move one way for a set amount of time (guaranteed to hit a mechanical stop). Then the software might keep track of focus position by how long it's driven the lens in one direction or the other starting at that known position (oops, I moved "out" 100 ms, but overshoot, so now I'll move "in" 50 ms). Or it might be that the bug makes it so the lens never gets properly reset to it's starting position.</htmltext>
<tokenext>Probably not measuring the times per sampling , but measuring the time the focus mechanism is moving .
To keep costs down , I suspect the mechanism has no feedback mechanism , so to focus you move one way for a set amount of time ( guaranteed to hit a mechanical stop ) .
Then the software might keep track of focus position by how long it 's driven the lens in one direction or the other starting at that known position ( oops , I moved " out " 100 ms , but overshoot , so now I 'll move " in " 50 ms ) .
Or it might be that the bug makes it so the lens never gets properly reset to it 's starting position .</tokentext>
<sentencetext>Probably not measuring the times per sampling, but measuring the time the focus mechanism is moving.
To keep costs down, I suspect the mechanism has no feedback mechanism, so to focus you move one way for a set amount of time (guaranteed to hit a mechanical stop).
Then the software might keep track of focus position by how long it's driven the lens in one direction or the other starting at that known position (oops, I moved "out" 100 ms, but overshoot, so now I'll move "in" 50 ms).
Or it might be that the bug makes it so the lens never gets properly reset to it's starting position.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148738</id>
	<title>I must have the same bug...</title>
	<author>Gavin Scott</author>
	<datestamp>1257070320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>After about 42 years my auto-focus suddenly stopped working as well.</p><p>You think if I live to 84 or so it will suddenly get better again?</p><p>I sure hope there's a patch...</p><p>G.</p></htmltext>
<tokenext>After about 42 years my auto-focus suddenly stopped working as well.You think if I live to 84 or so it will suddenly get better again ? I sure hope there 's a patch...G .</tokentext>
<sentencetext>After about 42 years my auto-focus suddenly stopped working as well.You think if I live to 84 or so it will suddenly get better again?I sure hope there's a patch...G.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174</id>
	<title>Rounding error?</title>
	<author>Anonymous</author>
	<datestamp>1257067800000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>In excusable. The industry is too mature for that type of shit.</p></htmltext>
<tokenext>In excusable .
The industry is too mature for that type of shit .</tokentext>
<sentencetext>In excusable.
The industry is too mature for that type of shit.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148306</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>BitZtream</author>
	<datestamp>1257068460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Seems like having a system timer trigger the auto focus update event would be a far better method of dealing with it rather than polling to check if its time to update again in some sort of loop.</p><p>Android DOES have timers usable by drivers doesn't it?  Requiring drivers to poll would be very shitty indeed, especially on devices with lower CPU power..</p></htmltext>
<tokenext>Seems like having a system timer trigger the auto focus update event would be a far better method of dealing with it rather than polling to check if its time to update again in some sort of loop.Android DOES have timers usable by drivers does n't it ?
Requiring drivers to poll would be very shitty indeed , especially on devices with lower CPU power. .</tokentext>
<sentencetext>Seems like having a system timer trigger the auto focus update event would be a far better method of dealing with it rather than polling to check if its time to update again in some sort of loop.Android DOES have timers usable by drivers doesn't it?
Requiring drivers to poll would be very shitty indeed, especially on devices with lower CPU power..</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149292</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>cream wobbly</author>
	<datestamp>1257073080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>This is what I hate about "smart" programmers at Google. They come up with the cleverest algo's, and they demand from their tests the ability to develop these algo's. Then they release something and along comes this sort of bug that simply does not need to happen!</p></div><p>It <em>is</em> a smart algorithm -- it's just a slightly poor <em>implementation</em>. As someone else mentions, it's probably a miscast to a signed 32-bit integer. The <em>algorithm</em>, on the other hand, is sound.</p><p>Your rant says more about you than it does about Google. You're intimidated by their ability to think of something elegant, and then do it right (unfortunately in this case only half the time).</p></div>
	</htmltext>
<tokenext>This is what I hate about " smart " programmers at Google .
They come up with the cleverest algo 's , and they demand from their tests the ability to develop these algo 's .
Then they release something and along comes this sort of bug that simply does not need to happen ! It is a smart algorithm -- it 's just a slightly poor implementation .
As someone else mentions , it 's probably a miscast to a signed 32-bit integer .
The algorithm , on the other hand , is sound.Your rant says more about you than it does about Google .
You 're intimidated by their ability to think of something elegant , and then do it right ( unfortunately in this case only half the time ) .</tokentext>
<sentencetext>This is what I hate about "smart" programmers at Google.
They come up with the cleverest algo's, and they demand from their tests the ability to develop these algo's.
Then they release something and along comes this sort of bug that simply does not need to happen!It is a smart algorithm -- it's just a slightly poor implementation.
As someone else mentions, it's probably a miscast to a signed 32-bit integer.
The algorithm, on the other hand, is sound.Your rant says more about you than it does about Google.
You're intimidated by their ability to think of something elegant, and then do it right (unfortunately in this case only half the time).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152112</id>
	<title>Re:iFocus ... NOT</title>
	<author>ajs</author>
	<datestamp>1257087900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>This is definitely NOT the Droid you are looking for</p></div><p>While this is a funny bug, I have to disagree.</p><p>The Droid has served me well as an iPhone upgrade for the past week and a half, and the fact that its camera was for shit for most of that was barely an inconvenience. Navigation, Google Voice, file transfers and a host of other features means that this most certainly was the Droid I was looking for.</p></div>
	</htmltext>
<tokenext>This is definitely NOT the Droid you are looking forWhile this is a funny bug , I have to disagree.The Droid has served me well as an iPhone upgrade for the past week and a half , and the fact that its camera was for shit for most of that was barely an inconvenience .
Navigation , Google Voice , file transfers and a host of other features means that this most certainly was the Droid I was looking for .</tokentext>
<sentencetext>This is definitely NOT the Droid you are looking forWhile this is a funny bug, I have to disagree.The Droid has served me well as an iPhone upgrade for the past week and a half, and the fact that its camera was for shit for most of that was barely an inconvenience.
Navigation, Google Voice, file transfers and a host of other features means that this most certainly was the Droid I was looking for.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148028</id>
	<title>Restraining Bolt</title>
	<author>Anonymous</author>
	<datestamp>1257066840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>They just need to take the restraining bolt off! Luke Skywalker had the same problem!</p></htmltext>
<tokenext>They just need to take the restraining bolt off !
Luke Skywalker had the same problem !</tokentext>
<sentencetext>They just need to take the restraining bolt off!
Luke Skywalker had the same problem!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148356</id>
	<title>Re:Auto-Focus</title>
	<author>hippo\_of\_knowledge</author>
	<datestamp>1257068700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>I would have expected a Schrodinger's camera joke by now.  Step up your game, Slashdot.</htmltext>
<tokenext>I would have expected a Schrodinger 's camera joke by now .
Step up your game , Slashdot .</tokentext>
<sentencetext>I would have expected a Schrodinger's camera joke by now.
Step up your game, Slashdot.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147990</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148528</id>
	<title>Bizarre Bug??... exploit it!</title>
	<author>FunkyELF</author>
	<datestamp>1257069420000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>.... and get r00t.<br>Then install Cyanogen to get wired tethering and give the middle finger to Verizon.</p></htmltext>
<tokenext>.... and get r00t.Then install Cyanogen to get wired tethering and give the middle finger to Verizon .</tokentext>
<sentencetext>.... and get r00t.Then install Cyanogen to get wired tethering and give the middle finger to Verizon.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155590</id>
	<title>Auto Focus?</title>
	<author>Anonymous</author>
	<datestamp>1258643220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I've not seen an Android phone, but I am having a hard time wrapping my mind around the concept that a cell phone has a lens large enough to bother with a focusing mechanism in the first place. Just about very phone camera I've ever seen has tiny fixed focus lens, and they usually work fine...</p></htmltext>
<tokenext>I 've not seen an Android phone , but I am having a hard time wrapping my mind around the concept that a cell phone has a lens large enough to bother with a focusing mechanism in the first place .
Just about very phone camera I 've ever seen has tiny fixed focus lens , and they usually work fine.. .</tokentext>
<sentencetext>I've not seen an Android phone, but I am having a hard time wrapping my mind around the concept that a cell phone has a lens large enough to bother with a focusing mechanism in the first place.
Just about very phone camera I've ever seen has tiny fixed focus lens, and they usually work fine...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148468</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Zero\_\_Kelvin</author>
	<datestamp>1257069180000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext>Oh, yeah!  Well we've been waiting an <i>unsigned <a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html" title="gnu.org" rel="nofollow">long long</a> [gnu.org] </i> time!</htmltext>
<tokenext>Oh , yeah !
Well we 've been waiting an unsigned long long [ gnu.org ] time !</tokentext>
<sentencetext>Oh, yeah!
Well we've been waiting an unsigned long long [gnu.org]  time!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149930</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257075840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What a timely fortune:</p><p>
&nbsp; &nbsp; &nbsp; C is quirky, flawed, and an enormous success -- Dennis M. Ritchie</p></htmltext>
<tokenext>What a timely fortune :       C is quirky , flawed , and an enormous success -- Dennis M. Ritchie</tokentext>
<sentencetext>What a timely fortune:
      C is quirky, flawed, and an enormous success -- Dennis M. Ritchie</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148430</id>
	<title>Kudos to Google for being so open about the bug</title>
	<author>cryfreedomlove</author>
	<datestamp>1257069000000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>It is gratifying for Google to be so open about the fact that it is a bug, the details of the bug, and a promise to fix it.  Most consumer electronics companies are much more cagey about this sort of thing.  I suspect Google will win some important trust because they are treating their customers like adults.</htmltext>
<tokenext>It is gratifying for Google to be so open about the fact that it is a bug , the details of the bug , and a promise to fix it .
Most consumer electronics companies are much more cagey about this sort of thing .
I suspect Google will win some important trust because they are treating their customers like adults .</tokentext>
<sentencetext>It is gratifying for Google to be so open about the fact that it is a bug, the details of the bug, and a promise to fix it.
Most consumer electronics companies are much more cagey about this sort of thing.
I suspect Google will win some important trust because they are treating their customers like adults.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150766</id>
	<title>Re:Time-related bugs</title>
	<author>DoctorFrog</author>
	<datestamp>1257079680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Be durned, I had an almost identical bug! Mine would always print on Wednesdays even if hard copy was deselected, because the y in Wednesday overflowed. The month and date weren't involved though, your bug is even cooler.</p></htmltext>
<tokenext>Be durned , I had an almost identical bug !
Mine would always print on Wednesdays even if hard copy was deselected , because the y in Wednesday overflowed .
The month and date were n't involved though , your bug is even cooler .</tokentext>
<sentencetext>Be durned, I had an almost identical bug!
Mine would always print on Wednesdays even if hard copy was deselected, because the y in Wednesday overflowed.
The month and date weren't involved though, your bug is even cooler.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149220</id>
	<title>Re:Time-releated bugs</title>
	<author>Anonymous</author>
	<datestamp>1257072780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>I got a "bug report" that our Oracle Forms app would give an undefined error message after you "type in a first name, push tab twice, and click save 17 times." I didn't debug it, but I did offer a workaround. </i> <br> <br>

Was the workaround something like "Don't click save more than 16 times?"</htmltext>
<tokenext>I got a " bug report " that our Oracle Forms app would give an undefined error message after you " type in a first name , push tab twice , and click save 17 times .
" I did n't debug it , but I did offer a workaround .
Was the workaround something like " Do n't click save more than 16 times ?
"</tokentext>
<sentencetext>I got a "bug report" that our Oracle Forms app would give an undefined error message after you "type in a first name, push tab twice, and click save 17 times.
" I didn't debug it, but I did offer a workaround.
Was the workaround something like "Don't click save more than 16 times?
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148326</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30166904</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>Schafer</author>
	<datestamp>1258639560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Voice Dialer HF" resolves each of the "Can't hands-free voice dial" issues listed above.</p><p>Disclaimer: After getting a Droid and being very, very annoyed at the same thing, I was involved in the development of this app.</p></htmltext>
<tokenext>" Voice Dialer HF " resolves each of the " Ca n't hands-free voice dial " issues listed above.Disclaimer : After getting a Droid and being very , very annoyed at the same thing , I was involved in the development of this app .</tokentext>
<sentencetext>"Voice Dialer HF" resolves each of the "Can't hands-free voice dial" issues listed above.Disclaimer: After getting a Droid and being very, very annoyed at the same thing, I was involved in the development of this app.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148742</id>
	<title>Re:So they tested it for less than 24.5 hours ...</title>
	<author>osu-neko</author>
	<datestamp>1257070320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>No, they would have discovered their are focus problems.  They would not necessarily know the cause.  They may even implement a fix or two, and at some point, the problem went away, so they marked the bug "fixed".  They could easily have been testing for 90 days or more without discovering the exact nature of the bug, with multiple false positives indicating that it had been fixed.</htmltext>
<tokenext>No , they would have discovered their are focus problems .
They would not necessarily know the cause .
They may even implement a fix or two , and at some point , the problem went away , so they marked the bug " fixed " .
They could easily have been testing for 90 days or more without discovering the exact nature of the bug , with multiple false positives indicating that it had been fixed .</tokentext>
<sentencetext>No, they would have discovered their are focus problems.
They would not necessarily know the cause.
They may even implement a fix or two, and at some point, the problem went away, so they marked the bug "fixed".
They could easily have been testing for 90 days or more without discovering the exact nature of the bug, with multiple false positives indicating that it had been fixed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148492</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148210</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Brian Gordon</author>
	<datestamp>1257067980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sounds like something to add to <a href="http://catb.org/jargon/html/P/phase-of-the-moon.html" title="catb.org">the jargon file</a> [catb.org]<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>Sounds like something to add to the jargon file [ catb.org ] : )</tokentext>
<sentencetext>Sounds like something to add to the jargon file [catb.org] :)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147894</id>
	<title>In case you were worried....</title>
	<author>Anonymous</author>
	<datestamp>1257066300000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Spring Break, the biggest part of it, occurs within a <i>working cycle</i>.</p></htmltext>
<tokenext>Spring Break , the biggest part of it , occurs within a working cycle .</tokentext>
<sentencetext>Spring Break, the biggest part of it, occurs within a working cycle.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149034</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>Mike Buddha</author>
	<datestamp>1257071760000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><ul> <li>Can't sync with Outlook (the phone doesn't have on-device encryption that would satisfy Exchange policies).</li></ul> </div><p>They should've just made it to lie about its policy enforcement to Exchange server like the iPhone did. That way it'd be banned from my corporate network like my iPhone was. Thanks Steve, you're such a smart guy.</p></div>
	</htmltext>
<tokenext>Ca n't sync with Outlook ( the phone does n't have on-device encryption that would satisfy Exchange policies ) .
They should 've just made it to lie about its policy enforcement to Exchange server like the iPhone did .
That way it 'd be banned from my corporate network like my iPhone was .
Thanks Steve , you 're such a smart guy .</tokentext>
<sentencetext> Can't sync with Outlook (the phone doesn't have on-device encryption that would satisfy Exchange policies).
They should've just made it to lie about its policy enforcement to Exchange server like the iPhone did.
That way it'd be banned from my corporate network like my iPhone was.
Thanks Steve, you're such a smart guy.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148134</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257067500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Waiting long? Hopefully we're not waiting double!</p></htmltext>
<tokenext>Waiting long ?
Hopefully we 're not waiting double !</tokentext>
<sentencetext>Waiting long?
Hopefully we're not waiting double!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150228</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>slicerwizard</author>
	<datestamp>1257076920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This is so typical for Motorola - back in the day when we had to interface their r750+ handsets to Baker consoles, we soon discovered that the handsets would lock up if they were powered/running for 24.5 days straight, thus making them unsuitable as interface devices.
<br> <br>
So we substituted i305 handsets - whose out of control audio AGC made them unsuitable as interface devices.
<br> <br>
So we got to support the customer by showing up at 2am every two weeks to manually power cycle their sixteen r750+ handsets.  Thanks for nothing Moto.</htmltext>
<tokenext>This is so typical for Motorola - back in the day when we had to interface their r750 + handsets to Baker consoles , we soon discovered that the handsets would lock up if they were powered/running for 24.5 days straight , thus making them unsuitable as interface devices .
So we substituted i305 handsets - whose out of control audio AGC made them unsuitable as interface devices .
So we got to support the customer by showing up at 2am every two weeks to manually power cycle their sixteen r750 + handsets .
Thanks for nothing Moto .</tokentext>
<sentencetext>This is so typical for Motorola - back in the day when we had to interface their r750+ handsets to Baker consoles, we soon discovered that the handsets would lock up if they were powered/running for 24.5 days straight, thus making them unsuitable as interface devices.
So we substituted i305 handsets - whose out of control audio AGC made them unsuitable as interface devices.
So we got to support the customer by showing up at 2am every two weeks to manually power cycle their sixteen r750+ handsets.
Thanks for nothing Moto.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149060</id>
	<title>Re:In case you were worried....</title>
	<author>spruce</author>
	<datestamp>1257071880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Right, like the camera is going to be the most common cause of out of focus pictures during spring break.</p><p>"OMG EVERYBODY LISTEN - DO 6 JELLO SHOTS WITH ME, THEN SAY CHEEZ.  *burp*, *snap*  AWW, THE CAMERA DIN'T WORK GUD"</p></htmltext>
<tokenext>Right , like the camera is going to be the most common cause of out of focus pictures during spring break .
" OMG EVERYBODY LISTEN - DO 6 JELLO SHOTS WITH ME , THEN SAY CHEEZ .
* burp * , * snap * AWW , THE CAMERA DI N'T WORK GUD "</tokentext>
<sentencetext>Right, like the camera is going to be the most common cause of out of focus pictures during spring break.
"OMG EVERYBODY LISTEN - DO 6 JELLO SHOTS WITH ME, THEN SAY CHEEZ.
*burp*, *snap*  AWW, THE CAMERA DIN'T WORK GUD"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147894</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148232</id>
	<title>Verizon's Droid?</title>
	<author>Anonymous</author>
	<datestamp>1257068100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I thought it was Motorola's Droid, but I guess because Verizon bundles it with contracts, it's "theirs"?</p></htmltext>
<tokenext>I thought it was Motorola 's Droid , but I guess because Verizon bundles it with contracts , it 's " theirs " ?</tokentext>
<sentencetext>I thought it was Motorola's Droid, but I guess because Verizon bundles it with contracts, it's "theirs"?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147926</id>
	<title>A timestamping overflow error</title>
	<author>Anonymous</author>
	<datestamp>1257066480000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>hoses up the camera autofocus?</p><p>Is this Slashdot, or <a href="http://thedailywtf.com/" title="thedailywtf.com" rel="nofollow">The Daily WTF</a> [thedailywtf.com]?</p></htmltext>
<tokenext>hoses up the camera autofocus ? Is this Slashdot , or The Daily WTF [ thedailywtf.com ] ?</tokentext>
<sentencetext>hoses up the camera autofocus?Is this Slashdot, or The Daily WTF [thedailywtf.com]?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149388</id>
	<title>Re:iPhone 3G/3GS GPS bug</title>
	<author>pz</author>
	<datestamp>1257073620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I had a similarly frustrating experience with T-Mobile's customer service in the Boston area.  My cell phone was set to auto-upate time.  It would always select the correct time and hour, but the wrong timezone, specifically, Pacific Time, instead of Eastern Time.  I didn't bother trying to figure it out, since it only affected me when I returned from a flight to another time zone and powered up the phone for the first time, and that was somewhat rare.</p><p>Then, through a series of coincidences, I noticed that when I power cycled my phone at my then girlfriend's house about 10 miles away, the time zone was set correctly.  After verifying this by testing at my apartment (incorrect time zone) and then at her place (correct time zone) again, I called T-Mobile customer service.</p><p>Yep, I was told to power cycle my phone.  To set the auto time update option.  Ad nauseum.  I called many times.  It was universally assumed that the fault was with my operation of the phone.  The CS reps I spoke to were unable to grasp that there must be separate time servers for different parts of the Boston area, and that the one my home was served by WAS WRONG.  I begged to have tickets put in, but eventually, I gave up.  CS reps are idiots because the general population is a bunh of idiots, and it is often impossible to get around this fact.</p><p>But, someone, somewhere, noticed because some weeks later, the time zone in my home cell was fixed.</p></htmltext>
<tokenext>I had a similarly frustrating experience with T-Mobile 's customer service in the Boston area .
My cell phone was set to auto-upate time .
It would always select the correct time and hour , but the wrong timezone , specifically , Pacific Time , instead of Eastern Time .
I did n't bother trying to figure it out , since it only affected me when I returned from a flight to another time zone and powered up the phone for the first time , and that was somewhat rare.Then , through a series of coincidences , I noticed that when I power cycled my phone at my then girlfriend 's house about 10 miles away , the time zone was set correctly .
After verifying this by testing at my apartment ( incorrect time zone ) and then at her place ( correct time zone ) again , I called T-Mobile customer service.Yep , I was told to power cycle my phone .
To set the auto time update option .
Ad nauseum .
I called many times .
It was universally assumed that the fault was with my operation of the phone .
The CS reps I spoke to were unable to grasp that there must be separate time servers for different parts of the Boston area , and that the one my home was served by WAS WRONG .
I begged to have tickets put in , but eventually , I gave up .
CS reps are idiots because the general population is a bunh of idiots , and it is often impossible to get around this fact.But , someone , somewhere , noticed because some weeks later , the time zone in my home cell was fixed .</tokentext>
<sentencetext>I had a similarly frustrating experience with T-Mobile's customer service in the Boston area.
My cell phone was set to auto-upate time.
It would always select the correct time and hour, but the wrong timezone, specifically, Pacific Time, instead of Eastern Time.
I didn't bother trying to figure it out, since it only affected me when I returned from a flight to another time zone and powered up the phone for the first time, and that was somewhat rare.Then, through a series of coincidences, I noticed that when I power cycled my phone at my then girlfriend's house about 10 miles away, the time zone was set correctly.
After verifying this by testing at my apartment (incorrect time zone) and then at her place (correct time zone) again, I called T-Mobile customer service.Yep, I was told to power cycle my phone.
To set the auto time update option.
Ad nauseum.
I called many times.
It was universally assumed that the fault was with my operation of the phone.
The CS reps I spoke to were unable to grasp that there must be separate time servers for different parts of the Boston area, and that the one my home was served by WAS WRONG.
I begged to have tickets put in, but eventually, I gave up.
CS reps are idiots because the general population is a bunh of idiots, and it is often impossible to get around this fact.But, someone, somewhere, noticed because some weeks later, the time zone in my home cell was fixed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870</id>
	<title>Auto-Focus</title>
	<author>Anonymous</author>
	<datestamp>1257066120000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>... Droid doesn't</htmltext>
<tokenext>... Droid does n't</tokentext>
<sentencetext>... Droid doesn't</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148200</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Jeff DeMaagd</author>
	<datestamp>1257067980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What I don't get is why a time stamp is needed to focus.  Most cameras don't seem to need to know what time it is in order to do that.</p></htmltext>
<tokenext>What I do n't get is why a time stamp is needed to focus .
Most cameras do n't seem to need to know what time it is in order to do that .</tokentext>
<sentencetext>What I don't get is why a time stamp is needed to focus.
Most cameras don't seem to need to know what time it is in order to do that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30172672</id>
	<title>Re:iPhone 3G/3GS GPS bug</title>
	<author>Alizarin Erythrosin</author>
	<datestamp>1258739160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Obviously this means the triangulation computations go horribly wrong and rather than reporting something absurd, the chipset just pretends it couldn't get a fix.</p></div></blockquote><p>Actually, the GPS is looking for a specific set of satellites that should be in view (based on the time and the orbit calculations) and can't find them where they should be. That's why it can't get a fix.</p></div>
	</htmltext>
<tokenext>Obviously this means the triangulation computations go horribly wrong and rather than reporting something absurd , the chipset just pretends it could n't get a fix.Actually , the GPS is looking for a specific set of satellites that should be in view ( based on the time and the orbit calculations ) and ca n't find them where they should be .
That 's why it ca n't get a fix .</tokentext>
<sentencetext>Obviously this means the triangulation computations go horribly wrong and rather than reporting something absurd, the chipset just pretends it couldn't get a fix.Actually, the GPS is looking for a specific set of satellites that should be in view (based on the time and the orbit calculations) and can't find them where they should be.
That's why it can't get a fix.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151440</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>hey!</author>
	<datestamp>1257083520000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>What I've seen is that some chargers power any USB powered equipment (including those on my PCs and laptops) and other wall and car chargers only power *some* USB powered equipment.  I'm guessing what's going on here is that some equipment (usually expensive thingies) refuse to run off an unregulated supply.  I've seen the same thing happen with a battery powered USB charger I whipped up.   Some equipment won't recognize it until the batteries are drained a bit.  That includes my new droid phone.</p><p>With respect to turn-by-turn navigation, I find the GPS is right on, but your mileage may vary with the accuracy of base maps in some locales.  The big problem is that the software, while useful, is not really all that polished for car navigation, compared to your basic, cheap sub $100 car GPS unit.  That's fine with me, because I *have* a cheap car unit that works well for me, so having one on my phone is just a nice-to-have.</p><p>As for Outlook, after years of having a phone that would work beautifully if I wanted to set up an Exchange server, I now have usable integration with my desktop computers via Google plugins to my Linux PIM software. So I'm happy.</p><p>As far as the contact sorting business is concerned, I agree this should be last name first, but it hardly matters if you have more than a couple dozen contacts.  I second  the call for HCI support.  I haven't had problem with my Bluetooth headset, and as far as hands-free dialing is concerned it's not an issue for me, as I don't use the phone while I'm driving.</p><p>Overall, I'm very happy with this phone, although it could be  better.  I think the IPhone onscreen keyboard works better, and I miss multi-touch, but I like the openness of the platform.  It wouldn't be hard at all to write your own contact application if you wanted to.  Thus far I haven't had to struggle with the phone because the manufacturer or the carrier wants me to do things a certain way or to buy or use certain services.  That's the way I like it. *It's my damn phone* so I want to use it the way I want.  The only other complaint is having to upgrade to a wireless data service when I'd prefer to use only WiFi, but that's pretty standard for now.</p></htmltext>
<tokenext>What I 've seen is that some chargers power any USB powered equipment ( including those on my PCs and laptops ) and other wall and car chargers only power * some * USB powered equipment .
I 'm guessing what 's going on here is that some equipment ( usually expensive thingies ) refuse to run off an unregulated supply .
I 've seen the same thing happen with a battery powered USB charger I whipped up .
Some equipment wo n't recognize it until the batteries are drained a bit .
That includes my new droid phone.With respect to turn-by-turn navigation , I find the GPS is right on , but your mileage may vary with the accuracy of base maps in some locales .
The big problem is that the software , while useful , is not really all that polished for car navigation , compared to your basic , cheap sub $ 100 car GPS unit .
That 's fine with me , because I * have * a cheap car unit that works well for me , so having one on my phone is just a nice-to-have.As for Outlook , after years of having a phone that would work beautifully if I wanted to set up an Exchange server , I now have usable integration with my desktop computers via Google plugins to my Linux PIM software .
So I 'm happy.As far as the contact sorting business is concerned , I agree this should be last name first , but it hardly matters if you have more than a couple dozen contacts .
I second the call for HCI support .
I have n't had problem with my Bluetooth headset , and as far as hands-free dialing is concerned it 's not an issue for me , as I do n't use the phone while I 'm driving.Overall , I 'm very happy with this phone , although it could be better .
I think the IPhone onscreen keyboard works better , and I miss multi-touch , but I like the openness of the platform .
It would n't be hard at all to write your own contact application if you wanted to .
Thus far I have n't had to struggle with the phone because the manufacturer or the carrier wants me to do things a certain way or to buy or use certain services .
That 's the way I like it .
* It 's my damn phone * so I want to use it the way I want .
The only other complaint is having to upgrade to a wireless data service when I 'd prefer to use only WiFi , but that 's pretty standard for now .</tokentext>
<sentencetext>What I've seen is that some chargers power any USB powered equipment (including those on my PCs and laptops) and other wall and car chargers only power *some* USB powered equipment.
I'm guessing what's going on here is that some equipment (usually expensive thingies) refuse to run off an unregulated supply.
I've seen the same thing happen with a battery powered USB charger I whipped up.
Some equipment won't recognize it until the batteries are drained a bit.
That includes my new droid phone.With respect to turn-by-turn navigation, I find the GPS is right on, but your mileage may vary with the accuracy of base maps in some locales.
The big problem is that the software, while useful, is not really all that polished for car navigation, compared to your basic, cheap sub $100 car GPS unit.
That's fine with me, because I *have* a cheap car unit that works well for me, so having one on my phone is just a nice-to-have.As for Outlook, after years of having a phone that would work beautifully if I wanted to set up an Exchange server, I now have usable integration with my desktop computers via Google plugins to my Linux PIM software.
So I'm happy.As far as the contact sorting business is concerned, I agree this should be last name first, but it hardly matters if you have more than a couple dozen contacts.
I second  the call for HCI support.
I haven't had problem with my Bluetooth headset, and as far as hands-free dialing is concerned it's not an issue for me, as I don't use the phone while I'm driving.Overall, I'm very happy with this phone, although it could be  better.
I think the IPhone onscreen keyboard works better, and I miss multi-touch, but I like the openness of the platform.
It wouldn't be hard at all to write your own contact application if you wanted to.
Thus far I haven't had to struggle with the phone because the manufacturer or the carrier wants me to do things a certain way or to buy or use certain services.
That's the way I like it.
*It's my damn phone* so I want to use it the way I want.
The only other complaint is having to upgrade to a wireless data service when I'd prefer to use only WiFi, but that's pretty standard for now.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148574</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>osu-neko</author>
	<datestamp>1257069540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yeah... only "clever" programming causes bugs.<nobr> <wbr></nobr>/eyeroll</htmltext>
<tokenext>Yeah... only " clever " programming causes bugs .
/eyeroll</tokentext>
<sentencetext>Yeah... only "clever" programming causes bugs.
/eyeroll</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150230</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>pwagland</author>
	<datestamp>1257076920000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p><div class="quote"><ul> <li>Can't sync with Outlook (the phone doesn't have on-device encryption that would satisfy Exchange policies).</li></ul></div><p>They should've just made it to lie about its policy enforcement to Exchange server like the iPhone did. That way it'd be banned from my corporate network like my iPhone was. Thanks Steve, you're such a smart guy.</p></div><p>Just as an aside, that bug is <a href="http://www.goip.com/2009/09/iphone-3-1-encryption-enforcement-fix-causing-problems-for-iphone-3g-2g-exchange-2007-users/" title="goip.com">now fixed</a> [goip.com]. To cut the story short, the 3GS does support it properly, earlier models do not, and iPhone 3.1 properly reports this to the server now.</p></div>
	</htmltext>
<tokenext>Ca n't sync with Outlook ( the phone does n't have on-device encryption that would satisfy Exchange policies ) .They should 've just made it to lie about its policy enforcement to Exchange server like the iPhone did .
That way it 'd be banned from my corporate network like my iPhone was .
Thanks Steve , you 're such a smart guy.Just as an aside , that bug is now fixed [ goip.com ] .
To cut the story short , the 3GS does support it properly , earlier models do not , and iPhone 3.1 properly reports this to the server now .</tokentext>
<sentencetext> Can't sync with Outlook (the phone doesn't have on-device encryption that would satisfy Exchange policies).They should've just made it to lie about its policy enforcement to Exchange server like the iPhone did.
That way it'd be banned from my corporate network like my iPhone was.
Thanks Steve, you're such a smart guy.Just as an aside, that bug is now fixed [goip.com].
To cut the story short, the 3GS does support it properly, earlier models do not, and iPhone 3.1 properly reports this to the server now.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149034</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</id>
	<title>Bigger bugs afoot...</title>
	<author>jddj</author>
	<datestamp>1257070740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>Honestly, autofocus on the just-so-so camera is the last of my worries:</p><ul> <li>Can't sync with Outlook (the phone doesn't have on-device encryption that would satisfy Exchange policies). Only calendar works, not contacts or email.</li><li>Can't hands-free voice dial (have to touch the phone to unlock it, touch to turn on voice dial, speak your choice, touch the choice from the menu of likely suspected contacts).</li><li>Locked phone's touch-screen comes on in pocket when answering with a headset, causing much mute/disconnect/speakerphone hilarity.</li><li>Turn-by-turn navigation is way off, literally by miles. Wrong 4 of 4 tries so far (in metro Atlanta and DC).</li><li>Immature bluetooth won't support HCI (portable bluetooth keyboards).</li><li>Rotating the phone after checking email checkboxes unchecks everything</li><li>Can't order contact list by last name (fixed in first name order)</li><li>Can't charge it with ANYTHING but the included AC adaptor (over-draws USB power from my old USB car and wall chargers)</li></ul><p>Really, fix the camera sometime down the line. But make the phone dial hands-free. Make email work. Make the navigation something other than worthless. Make "lock the screen" really lock the screen.</p><p>Someone at Google should use one of their own phones for a while and see how (s)he likes it.</p><p>It's a wonderfully powerful platform, but clearly not as well-thought-out or fluid to work as iPhone/iPod Touch</p></htmltext>
<tokenext>Honestly , autofocus on the just-so-so camera is the last of my worries : Ca n't sync with Outlook ( the phone does n't have on-device encryption that would satisfy Exchange policies ) .
Only calendar works , not contacts or email.Ca n't hands-free voice dial ( have to touch the phone to unlock it , touch to turn on voice dial , speak your choice , touch the choice from the menu of likely suspected contacts ) .Locked phone 's touch-screen comes on in pocket when answering with a headset , causing much mute/disconnect/speakerphone hilarity.Turn-by-turn navigation is way off , literally by miles .
Wrong 4 of 4 tries so far ( in metro Atlanta and DC ) .Immature bluetooth wo n't support HCI ( portable bluetooth keyboards ) .Rotating the phone after checking email checkboxes unchecks everythingCa n't order contact list by last name ( fixed in first name order ) Ca n't charge it with ANYTHING but the included AC adaptor ( over-draws USB power from my old USB car and wall chargers ) Really , fix the camera sometime down the line .
But make the phone dial hands-free .
Make email work .
Make the navigation something other than worthless .
Make " lock the screen " really lock the screen.Someone at Google should use one of their own phones for a while and see how ( s ) he likes it.It 's a wonderfully powerful platform , but clearly not as well-thought-out or fluid to work as iPhone/iPod Touch</tokentext>
<sentencetext>Honestly, autofocus on the just-so-so camera is the last of my worries: Can't sync with Outlook (the phone doesn't have on-device encryption that would satisfy Exchange policies).
Only calendar works, not contacts or email.Can't hands-free voice dial (have to touch the phone to unlock it, touch to turn on voice dial, speak your choice, touch the choice from the menu of likely suspected contacts).Locked phone's touch-screen comes on in pocket when answering with a headset, causing much mute/disconnect/speakerphone hilarity.Turn-by-turn navigation is way off, literally by miles.
Wrong 4 of 4 tries so far (in metro Atlanta and DC).Immature bluetooth won't support HCI (portable bluetooth keyboards).Rotating the phone after checking email checkboxes unchecks everythingCan't order contact list by last name (fixed in first name order)Can't charge it with ANYTHING but the included AC adaptor (over-draws USB power from my old USB car and wall chargers)Really, fix the camera sometime down the line.
But make the phone dial hands-free.
Make email work.
Make the navigation something other than worthless.
Make "lock the screen" really lock the screen.Someone at Google should use one of their own phones for a while and see how (s)he likes it.It's a wonderfully powerful platform, but clearly not as well-thought-out or fluid to work as iPhone/iPod Touch</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257066840000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><blockquote><div><p>Hopefully we're not waiting long.</p></div></blockquote><p>
We're waiting <em>unsigned long</em>.</p></div>
	</htmltext>
<tokenext>Hopefully we 're not waiting long .
We 're waiting unsigned long .</tokentext>
<sentencetext>Hopefully we're not waiting long.
We're waiting unsigned long.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148318</id>
	<title>Re:Rounding error?</title>
	<author>Anonymous</author>
	<datestamp>1257068580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Didn't you know the unwritten rule of Slashdot? It's only cool if you say this kind of thing about Microsoft.</htmltext>
<tokenext>Did n't you know the unwritten rule of Slashdot ?
It 's only cool if you say this kind of thing about Microsoft .</tokentext>
<sentencetext>Didn't you know the unwritten rule of Slashdot?
It's only cool if you say this kind of thing about Microsoft.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155190</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>Anonymous</author>
	<datestamp>1258640940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It seems like everybody at Google uses Macs and iPhones -- why would they use a Droid?</p></htmltext>
<tokenext>It seems like everybody at Google uses Macs and iPhones -- why would they use a Droid ?</tokentext>
<sentencetext>It seems like everybody at Google uses Macs and iPhones -- why would they use a Droid?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148848</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>DeadCatX2</author>
	<datestamp>1257070860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The engadget poster mentions a <i>rounding</i> bug, not a sign-extension bug.  (and for it to be a sign-extension bug, they would need to be extending from 32-bit timestamps to 64-bit timestamps).</p><p>That doesn't mean it's not the 2^31 ms ~= 24.5 days.  It could be that the platform "rounds toward zero", and the developers anticipated that to mean "round down" in the context of numbers that are always positive...and when the numbers become negative, it rounds up instead, and screws them.</p><p>The best theory I've heard so far was that a timestamp is being used to figure out where to move the lens.  Other than that, perhaps it's being used in some GUID-like fashion and the rounding causes a violation of the uniqueness requirement?</p></htmltext>
<tokenext>The engadget poster mentions a rounding bug , not a sign-extension bug .
( and for it to be a sign-extension bug , they would need to be extending from 32-bit timestamps to 64-bit timestamps ) .That does n't mean it 's not the 2 ^ 31 ms ~ = 24.5 days .
It could be that the platform " rounds toward zero " , and the developers anticipated that to mean " round down " in the context of numbers that are always positive...and when the numbers become negative , it rounds up instead , and screws them.The best theory I 've heard so far was that a timestamp is being used to figure out where to move the lens .
Other than that , perhaps it 's being used in some GUID-like fashion and the rounding causes a violation of the uniqueness requirement ?</tokentext>
<sentencetext>The engadget poster mentions a rounding bug, not a sign-extension bug.
(and for it to be a sign-extension bug, they would need to be extending from 32-bit timestamps to 64-bit timestamps).That doesn't mean it's not the 2^31 ms ~= 24.5 days.
It could be that the platform "rounds toward zero", and the developers anticipated that to mean "round down" in the context of numbers that are always positive...and when the numbers become negative, it rounds up instead, and screws them.The best theory I've heard so far was that a timestamp is being used to figure out where to move the lens.
Other than that, perhaps it's being used in some GUID-like fashion and the rounding causes a violation of the uniqueness requirement?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148998</id>
	<title>Re:Kudos to Google for being so open about the bug</title>
	<author>Anonymous</author>
	<datestamp>1257071640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I hate to say it, but most adults act like spoiled children...</p><p>This will only end badly...<nobr> <wbr></nobr>:-(</p></htmltext>
<tokenext>I hate to say it , but most adults act like spoiled children...This will only end badly... : - (</tokentext>
<sentencetext>I hate to say it, but most adults act like spoiled children...This will only end badly... :-(</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148430</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148634</id>
	<title>Re:Rounding error?</title>
	<author>Anonymous</author>
	<datestamp>1257069780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Inside of what? Or do you mean inexcusable as one word?</p><p>Typos happen, bugs happen.</p><p>Life's to short to waste on you.</p></htmltext>
<tokenext>Inside of what ?
Or do you mean inexcusable as one word ? Typos happen , bugs happen.Life 's to short to waste on you .</tokentext>
<sentencetext>Inside of what?
Or do you mean inexcusable as one word?Typos happen, bugs happen.Life's to short to waste on you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154336</id>
	<title>This is just great</title>
	<author>PassiveAggressive</author>
	<datestamp>1258629360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This is exactly what we need - cameras with mood swings.
What's next? Phones with a short attention span?</htmltext>
<tokenext>This is exactly what we need - cameras with mood swings .
What 's next ?
Phones with a short attention span ?</tokentext>
<sentencetext>This is exactly what we need - cameras with mood swings.
What's next?
Phones with a short attention span?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30153468</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257103260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well, if you want to be pedantic, yet actually do the math, based upon the actual nature of the bug...</p><p>It works out to a period of 49 days 17 hours 2 minutes 47 seconds and 296 milliseconds.</p></htmltext>
<tokenext>Well , if you want to be pedantic , yet actually do the math , based upon the actual nature of the bug...It works out to a period of 49 days 17 hours 2 minutes 47 seconds and 296 milliseconds .</tokentext>
<sentencetext>Well, if you want to be pedantic, yet actually do the math, based upon the actual nature of the bug...It works out to a period of 49 days 17 hours 2 minutes 47 seconds and 296 milliseconds.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149142</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>SerpentMage</author>
	<datestamp>1257067560000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>This is what I hate about "smart" programmers at Google. They come up with the cleverest algo's, and they demand from their tests the ability to develop these algo's. Then they release something and along comes this sort of bug that simply does not need to happen!</p><p>So why does it happen, because their programmers are "clever"...</p><p>And the worst part this is the sort of bug that consumers will laugh their head off about. The reason why Apple sells so well is not because they are rocket scientists, but because when people use their products people say, "hey this is pretty cool..." Whereas techie's say, "hey this is pretty cool..." WRONG FOCUS...</p></htmltext>
<tokenext>This is what I hate about " smart " programmers at Google .
They come up with the cleverest algo 's , and they demand from their tests the ability to develop these algo 's .
Then they release something and along comes this sort of bug that simply does not need to happen ! So why does it happen , because their programmers are " clever " ...And the worst part this is the sort of bug that consumers will laugh their head off about .
The reason why Apple sells so well is not because they are rocket scientists , but because when people use their products people say , " hey this is pretty cool... " Whereas techie 's say , " hey this is pretty cool... " WRONG FOCUS.. .</tokentext>
<sentencetext>This is what I hate about "smart" programmers at Google.
They come up with the cleverest algo's, and they demand from their tests the ability to develop these algo's.
Then they release something and along comes this sort of bug that simply does not need to happen!So why does it happen, because their programmers are "clever"...And the worst part this is the sort of bug that consumers will laugh their head off about.
The reason why Apple sells so well is not because they are rocket scientists, but because when people use their products people say, "hey this is pretty cool..." Whereas techie's say, "hey this is pretty cool..." WRONG FOCUS...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148764</id>
	<title>Re:IIRC, this is the same sort of bug</title>
	<author>Zero\_\_Kelvin</author>
	<datestamp>1257070440000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>I don't believe that one was ever seen in the wild, since Windows 95 also had several bugs that caused it to require a reboot approximately every 24.5 <b> <i>minutes</i></b> <nobr> <wbr></nobr>;-)</htmltext>
<tokenext>I do n't believe that one was ever seen in the wild , since Windows 95 also had several bugs that caused it to require a reboot approximately every 24.5 minutes ; - )</tokentext>
<sentencetext>I don't believe that one was ever seen in the wild, since Windows 95 also had several bugs that caused it to require a reboot approximately every 24.5  minutes  ;-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148060</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149142</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257072420000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>"causes autofocus to behave poorly on a 24.5-day cycle [...] That is, it'll work for 24.5 days, then have poor performance for 24.5 days, then work again"</p><p>Except if it works for 24.5 days, then doesn't work for 24.5 days, then works again, it's a 49 day cycle. Sorry to be pedantic, but someone abbreviating that statement might mislead someone else to believe they have a different problem when they see they have a 49 day, and not a 24.5 day, cycle of inoperability.</p></htmltext>
<tokenext>" causes autofocus to behave poorly on a 24.5-day cycle [ ... ] That is , it 'll work for 24.5 days , then have poor performance for 24.5 days , then work again " Except if it works for 24.5 days , then does n't work for 24.5 days , then works again , it 's a 49 day cycle .
Sorry to be pedantic , but someone abbreviating that statement might mislead someone else to believe they have a different problem when they see they have a 49 day , and not a 24.5 day , cycle of inoperability .</tokentext>
<sentencetext>"causes autofocus to behave poorly on a 24.5-day cycle [...] That is, it'll work for 24.5 days, then have poor performance for 24.5 days, then work again"Except if it works for 24.5 days, then doesn't work for 24.5 days, then works again, it's a 49 day cycle.
Sorry to be pedantic, but someone abbreviating that statement might mislead someone else to believe they have a different problem when they see they have a 49 day, and not a 24.5 day, cycle of inoperability.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149056</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>microbee</author>
	<datestamp>1257071880000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Hopefully we're not waiting long.</p></div><p>You meant 'signed long'.</p></div>
	</htmltext>
<tokenext>Hopefully we 're not waiting long.You meant 'signed long' .</tokentext>
<sentencetext>Hopefully we're not waiting long.You meant 'signed long'.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</id>
	<title>Time-releated bugs</title>
	<author>Iphtashu Fitz</author>
	<datestamp>1257066960000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>15+ years ago I had to debug some code in a report printing app for OS/2 (remember that OS?).  The bug would cause the app to crash when a report was printed out.  But the bug would only happen on certain days.  Certain days in September.  Only on Wednesdays in September.  Only when it was a Wednesday in September after the 9th.</p><p>The bug?  The original programmer had tried to optimize memory usage as much as possible and was off by a count of one.  With "September" being the longest month spelled out, "Wednesday" the longest day spelled out, and a 2 digit date, the header that the program put together to send to the printer would overflow its buffer by one character.</p></htmltext>
<tokenext>15 + years ago I had to debug some code in a report printing app for OS/2 ( remember that OS ? ) .
The bug would cause the app to crash when a report was printed out .
But the bug would only happen on certain days .
Certain days in September .
Only on Wednesdays in September .
Only when it was a Wednesday in September after the 9th.The bug ?
The original programmer had tried to optimize memory usage as much as possible and was off by a count of one .
With " September " being the longest month spelled out , " Wednesday " the longest day spelled out , and a 2 digit date , the header that the program put together to send to the printer would overflow its buffer by one character .</tokentext>
<sentencetext>15+ years ago I had to debug some code in a report printing app for OS/2 (remember that OS?).
The bug would cause the app to crash when a report was printed out.
But the bug would only happen on certain days.
Certain days in September.
Only on Wednesdays in September.
Only when it was a Wednesday in September after the 9th.The bug?
The original programmer had tried to optimize memory usage as much as possible and was off by a count of one.
With "September" being the longest month spelled out, "Wednesday" the longest day spelled out, and a 2 digit date, the header that the program put together to send to the printer would overflow its buffer by one character.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148254</id>
	<title>Will they remember at review/raise time?</title>
	<author>dltaylor</author>
	<datestamp>1257068220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Tasks accomplished: fixed timestamp rounding error in autofocus subroutine"</p><p>vs.</p><p>"Tasks accomplished: designed/implemented autofocus subroutine"</p></htmltext>
<tokenext>" Tasks accomplished : fixed timestamp rounding error in autofocus subroutine " vs. " Tasks accomplished : designed/implemented autofocus subroutine "</tokentext>
<sentencetext>"Tasks accomplished: fixed timestamp rounding error in autofocus subroutine"vs."Tasks accomplished: designed/implemented autofocus subroutine"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152680</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257093300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So its just not MS who makes mistakes - <a href="http://it.slashdot.org/article.pl?sid=08/12/31/1428254&amp;tid=128" title="slashdot.org" rel="nofollow">Microsoft Zunes Committing Mass Suicide</a> [slashdot.org]</p></htmltext>
<tokenext>So its just not MS who makes mistakes - Microsoft Zunes Committing Mass Suicide [ slashdot.org ]</tokentext>
<sentencetext>So its just not MS who makes mistakes - Microsoft Zunes Committing Mass Suicide [slashdot.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148754</id>
	<title>Not printing on tuesdays.</title>
	<author>gehrehmee</author>
	<datestamp>1257070380000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>There was a wonderful bug in ubuntu where it wouldn't print on tuesdays. It would generate a postscript file, which includes the date, but a faulty entry for file-type detection caused postscript on tuesday to be interpreted as some kind of erlang file... which obviously didn't print very well<nobr> <wbr></nobr>:)</p><p><a href="http://bugs.launchpad.net/ubuntu/+source/file/+bug/248619" title="launchpad.net">http://bugs.launchpad.net/ubuntu/+source/file/+bug/248619</a> [launchpad.net]</p></htmltext>
<tokenext>There was a wonderful bug in ubuntu where it would n't print on tuesdays .
It would generate a postscript file , which includes the date , but a faulty entry for file-type detection caused postscript on tuesday to be interpreted as some kind of erlang file... which obviously did n't print very well : ) http : //bugs.launchpad.net/ubuntu/ + source/file/ + bug/248619 [ launchpad.net ]</tokentext>
<sentencetext>There was a wonderful bug in ubuntu where it wouldn't print on tuesdays.
It would generate a postscript file, which includes the date, but a faulty entry for file-type detection caused postscript on tuesday to be interpreted as some kind of erlang file... which obviously didn't print very well :)http://bugs.launchpad.net/ubuntu/+source/file/+bug/248619 [launchpad.net]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154384</id>
	<title>Re:Wow</title>
	<author>Anonymous</author>
	<datestamp>1258630140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Saying that 24.5 approximates a lunar cycle of 29.5 days is much like saying that you can approximate the value of pi by just using the number 3.  If you ask me, it'd take an act of congress to get something like that accepted...</p></htmltext>
<tokenext>Saying that 24.5 approximates a lunar cycle of 29.5 days is much like saying that you can approximate the value of pi by just using the number 3 .
If you ask me , it 'd take an act of congress to get something like that accepted.. .</tokentext>
<sentencetext>Saying that 24.5 approximates a lunar cycle of 29.5 days is much like saying that you can approximate the value of pi by just using the number 3.
If you ask me, it'd take an act of congress to get something like that accepted...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148066</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150426</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Jarik C-Bol</author>
	<datestamp>1257077880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>notwithstanding the actual cause and what not, i find this to be truly hilarious. seems that coding some sort of timer into it, that did not use the system time stamp, would have been easier to begin with. But hey, I'm not a camera phone software developer.</htmltext>
<tokenext>notwithstanding the actual cause and what not , i find this to be truly hilarious .
seems that coding some sort of timer into it , that did not use the system time stamp , would have been easier to begin with .
But hey , I 'm not a camera phone software developer .</tokentext>
<sentencetext>notwithstanding the actual cause and what not, i find this to be truly hilarious.
seems that coding some sort of timer into it, that did not use the system time stamp, would have been easier to begin with.
But hey, I'm not a camera phone software developer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148326</id>
	<title>Re:Time-releated bugs</title>
	<author>Anonymous</author>
	<datestamp>1257068580000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>I got a "bug report" that our Oracle Forms app would give an undefined error message after you "type in a first name, push tab twice, and click save 17 times." I didn't debug it, but I did offer a workaround.

<br> <br>I also had a bug report for when you tried to add a prerequisite that didn't exist to a training task (the system tracked flight Air Force crew training and experience), an error would pop up that said "All this time and it still doesn't work..." In that case, apparently debugging was as far as anyone ever got.</htmltext>
<tokenext>I got a " bug report " that our Oracle Forms app would give an undefined error message after you " type in a first name , push tab twice , and click save 17 times .
" I did n't debug it , but I did offer a workaround .
I also had a bug report for when you tried to add a prerequisite that did n't exist to a training task ( the system tracked flight Air Force crew training and experience ) , an error would pop up that said " All this time and it still does n't work... " In that case , apparently debugging was as far as anyone ever got .</tokentext>
<sentencetext>I got a "bug report" that our Oracle Forms app would give an undefined error message after you "type in a first name, push tab twice, and click save 17 times.
" I didn't debug it, but I did offer a workaround.
I also had a bug report for when you tried to add a prerequisite that didn't exist to a training task (the system tracked flight Air Force crew training and experience), an error would pop up that said "All this time and it still doesn't work..." In that case, apparently debugging was as far as anyone ever got.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148734</id>
	<title>iDon't Focus properly</title>
	<author>93 Escort Wagon</author>
	<datestamp>1257070320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>... but the iPhone does.</p></htmltext>
<tokenext>... but the iPhone does .</tokentext>
<sentencetext>... but the iPhone does.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148302</id>
	<title>Be symphatetic...</title>
	<author>Anonymous</author>
	<datestamp>1257068460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>... come on... phones are like woman... they just have those bad days!</p></htmltext>
<tokenext>... come on... phones are like woman... they just have those bad days !</tokentext>
<sentencetext>... come on... phones are like woman... they just have those bad days!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148982</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>sega01</author>
	<datestamp>1257071580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That was awesome. You need more than 5 points for that comment<nobr> <wbr></nobr>:-).</p></htmltext>
<tokenext>That was awesome .
You need more than 5 points for that comment : - ) .</tokentext>
<sentencetext>That was awesome.
You need more than 5 points for that comment :-).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30153416</id>
	<title>I don't understand...</title>
	<author>jonaskoelker</author>
	<datestamp>1257102120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Can't hands-free voice dial [...]</p></div><p>This one I have never understood.</p><p>Whenever I have the time and attention answering or making a phone call requires, I also have my hands available, or I can make them available in a few seconds.</p><p>So why is this an important feature?</p></div>
	</htmltext>
<tokenext>Ca n't hands-free voice dial [ ... ] This one I have never understood.Whenever I have the time and attention answering or making a phone call requires , I also have my hands available , or I can make them available in a few seconds.So why is this an important feature ?</tokentext>
<sentencetext>Can't hands-free voice dial [...]This one I have never understood.Whenever I have the time and attention answering or making a phone call requires, I also have my hands available, or I can make them available in a few seconds.So why is this an important feature?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149756</id>
	<title>LOL/WTF/Meh</title>
	<author>Anonymous</author>
	<datestamp>1257075120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>LOL...while I didn't by my Droid for its camera capability, I can see others being put off by the issue.  I actually have had an attitude somewhere between "wtf" and "meh".  After reading the article, I quickly picked up my Droid, and...GREAT MYSTERY OF LIFE...it works! (thankfully it's the 18th of Nov.)  Well in spite of my laissez faire attitude, I am looking forward to my phone getting the appropriate therapy to rid it of it's multiple personality disorder.  Regardless of the focusing issue I still find the pictures to be pretty crappy but I'll hold out hope that they'll improve picture contrast/levels with some software update or another.</p></htmltext>
<tokenext>LOL...while I did n't by my Droid for its camera capability , I can see others being put off by the issue .
I actually have had an attitude somewhere between " wtf " and " meh " .
After reading the article , I quickly picked up my Droid , and...GREAT MYSTERY OF LIFE...it works !
( thankfully it 's the 18th of Nov. ) Well in spite of my laissez faire attitude , I am looking forward to my phone getting the appropriate therapy to rid it of it 's multiple personality disorder .
Regardless of the focusing issue I still find the pictures to be pretty crappy but I 'll hold out hope that they 'll improve picture contrast/levels with some software update or another .</tokentext>
<sentencetext>LOL...while I didn't by my Droid for its camera capability, I can see others being put off by the issue.
I actually have had an attitude somewhere between "wtf" and "meh".
After reading the article, I quickly picked up my Droid, and...GREAT MYSTERY OF LIFE...it works!
(thankfully it's the 18th of Nov.)  Well in spite of my laissez faire attitude, I am looking forward to my phone getting the appropriate therapy to rid it of it's multiple personality disorder.
Regardless of the focusing issue I still find the pictures to be pretty crappy but I'll hold out hope that they'll improve picture contrast/levels with some software update or another.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154624</id>
	<title>Re:So they tested it for less than 24.5 hours ...</title>
	<author>SharpFang</author>
	<datestamp>1258634160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They might have tested it for 49 days, then after halfway through heavy testing and debugging, the bug just "vanished by itself" and they couldn't reproduce it.</p></htmltext>
<tokenext>They might have tested it for 49 days , then after halfway through heavy testing and debugging , the bug just " vanished by itself " and they could n't reproduce it .</tokentext>
<sentencetext>They might have tested it for 49 days, then after halfway through heavy testing and debugging, the bug just "vanished by itself" and they couldn't reproduce it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148492</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149838</id>
	<title>Re:I must have the same bug...</title>
	<author>BitZtream</author>
	<datestamp>1257075480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The patch is already available, see your doctor.</p></htmltext>
<tokenext>The patch is already available , see your doctor .</tokentext>
<sentencetext>The patch is already available, see your doctor.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148738</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148104</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257067260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I was just about to post, asking "Why does the autofocus need to know what time it is?" Thanks for the info.</p></htmltext>
<tokenext>I was just about to post , asking " Why does the autofocus need to know what time it is ?
" Thanks for the info .</tokentext>
<sentencetext>I was just about to post, asking "Why does the autofocus need to know what time it is?
" Thanks for the info.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148940</id>
	<title>Re:Auto-Focus</title>
	<author>Mike Buddha</author>
	<datestamp>1257071400000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>"Sporadically bugs: iDoesn't. Droid does."</p></div><p>Yeah, tell that to the iPhone browser next time it shits out without warning. iDoes, too.</p></div>
	</htmltext>
<tokenext>" Sporadically bugs : iDoes n't .
Droid does .
" Yeah , tell that to the iPhone browser next time it shits out without warning .
iDoes , too .</tokentext>
<sentencetext>"Sporadically bugs: iDoesn't.
Droid does.
"Yeah, tell that to the iPhone browser next time it shits out without warning.
iDoes, too.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147944</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149512</id>
	<title>4.3BSD had a bug like that</title>
	<author>Animats</author>
	<datestamp>1257074220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>
The initial release of 4.3BSD had a bug like that.  It wouldn't interoperate with implementations that chose TCP sequence numbers in the upper half of the 32-bit address space.  BSD itself didn't do this until it had been up for 2^31 seconds, so it got through testing.  Other implementations cycled faster.  We were losing network connections for two hours out of every four.
</p><p>
It took a 1-line fix, after three days of looking at the generated machine code to figure out exactly how the sequence number arithmetic worked.  Too many casts in the source.</p></htmltext>
<tokenext>The initial release of 4.3BSD had a bug like that .
It would n't interoperate with implementations that chose TCP sequence numbers in the upper half of the 32-bit address space .
BSD itself did n't do this until it had been up for 2 ^ 31 seconds , so it got through testing .
Other implementations cycled faster .
We were losing network connections for two hours out of every four .
It took a 1-line fix , after three days of looking at the generated machine code to figure out exactly how the sequence number arithmetic worked .
Too many casts in the source .</tokentext>
<sentencetext>
The initial release of 4.3BSD had a bug like that.
It wouldn't interoperate with implementations that chose TCP sequence numbers in the upper half of the 32-bit address space.
BSD itself didn't do this until it had been up for 2^31 seconds, so it got through testing.
Other implementations cycled faster.
We were losing network connections for two hours out of every four.
It took a 1-line fix, after three days of looking at the generated machine code to figure out exactly how the sequence number arithmetic worked.
Too many casts in the source.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148762</id>
	<title>Sounds like my wife.</title>
	<author>Anonymous</author>
	<datestamp>1257070440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Though she's on a 28 day cycle.</htmltext>
<tokenext>Though she 's on a 28 day cycle .</tokentext>
<sentencetext>Though she's on a 28 day cycle.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152226</id>
	<title>Rookie mistake</title>
	<author>plopez</author>
	<datestamp>1257088740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Enough said. But may be worse these days as people don't seem to actually think about the hardware. There seems to be an attitude of: "Java/.Net/Python etc. will do everything! Why worry about hardware!"</p></htmltext>
<tokenext>Enough said .
But may be worse these days as people do n't seem to actually think about the hardware .
There seems to be an attitude of : " Java/.Net/Python etc .
will do everything !
Why worry about hardware !
"</tokentext>
<sentencetext>Enough said.
But may be worse these days as people don't seem to actually think about the hardware.
There seems to be an attitude of: "Java/.Net/Python etc.
will do everything!
Why worry about hardware!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152058</id>
	<title>Re:iFocus ... NOT</title>
	<author>Anonymous</author>
	<datestamp>1257087660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>... But it might be tomorrow.</p></htmltext>
<tokenext>... But it might be tomorrow .</tokentext>
<sentencetext>... But it might be tomorrow.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148030</id>
	<title>Just one more thing...</title>
	<author>Anonymous</author>
	<datestamp>1257066840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>...that iDon't</p></htmltext>
<tokenext>...that iDo n't</tokentext>
<sentencetext>...that iDon't</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30157276</id>
	<title>Re:iPhone 3G/3GS GPS bug</title>
	<author>Anonymous</author>
	<datestamp>1258649280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>My G1 rarely established a network connection when I left home (and wifi) so I called to see what was up.  "Have you tried rebooting your router?" was the only thing they could come up with.  I told the schmuck that I smashed the thing and I still didn't have connectivity.  Turns out a firmware update fixed that one.  Thanks T-Mobile!</p></htmltext>
<tokenext>My G1 rarely established a network connection when I left home ( and wifi ) so I called to see what was up .
" Have you tried rebooting your router ?
" was the only thing they could come up with .
I told the schmuck that I smashed the thing and I still did n't have connectivity .
Turns out a firmware update fixed that one .
Thanks T-Mobile !</tokentext>
<sentencetext>My G1 rarely established a network connection when I left home (and wifi) so I called to see what was up.
"Have you tried rebooting your router?
" was the only thing they could come up with.
I told the schmuck that I smashed the thing and I still didn't have connectivity.
Turns out a firmware update fixed that one.
Thanks T-Mobile!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149388</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148776</id>
	<title>BUG! That was supposed to be 29.5 not 24.5</title>
	<author>Tired and Emotional</author>
	<datestamp>1257070500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Half the focus group users did not want in-focus photos taken of them for a few days each month. Some idiot male programmer clearly mistyped the constant.</htmltext>
<tokenext>Half the focus group users did not want in-focus photos taken of them for a few days each month .
Some idiot male programmer clearly mistyped the constant .</tokentext>
<sentencetext>Half the focus group users did not want in-focus photos taken of them for a few days each month.
Some idiot male programmer clearly mistyped the constant.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148874</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>pedantic bore</author>
	<datestamp>1257071040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Well, if it's written in Java like the rest of Android, it could be a bit more work.  T'aint no "unsigned" in Java.</htmltext>
<tokenext>Well , if it 's written in Java like the rest of Android , it could be a bit more work .
T'aint no " unsigned " in Java .</tokentext>
<sentencetext>Well, if it's written in Java like the rest of Android, it could be a bit more work.
T'aint no "unsigned" in Java.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148066</id>
	<title>Wow</title>
	<author>QuoteMstr</author>
	<datestamp>1257067020000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Considering that a lunar cycle is 29.5 days long, we've actually found a bug that depends (approximately) on the phase of the moon!</p></htmltext>
<tokenext>Considering that a lunar cycle is 29.5 days long , we 've actually found a bug that depends ( approximately ) on the phase of the moon !</tokentext>
<sentencetext>Considering that a lunar cycle is 29.5 days long, we've actually found a bug that depends (approximately) on the phase of the moon!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149192</id>
	<title>Re:New Moon?</title>
	<author>AndersOSU</author>
	<datestamp>1257072660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>what, the autofocus doesn't crash, instead it sparkles?</p></htmltext>
<tokenext>what , the autofocus does n't crash , instead it sparkles ?</tokentext>
<sentencetext>what, the autofocus doesn't crash, instead it sparkles?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148194</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148020</id>
	<title>Simple solution</title>
	<author>Anonymous</author>
	<datestamp>1257066780000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Just buy two with opposing date stamps.</p></htmltext>
<tokenext>Just buy two with opposing date stamps .</tokentext>
<sentencetext>Just buy two with opposing date stamps.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149374</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>Anonymous</author>
	<datestamp>1257073560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Android is such bloody garbage. And everyone thinks it's the next Messiah.</p></htmltext>
<tokenext>Android is such bloody garbage .
And everyone thinks it 's the next Messiah .</tokentext>
<sentencetext>Android is such bloody garbage.
And everyone thinks it's the next Messiah.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154262</id>
	<title>Re:iPhone 3G/3GS GPS bug</title>
	<author>AaronLawrence</author>
	<datestamp>1258628100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have not yet figured out how actual bug reports get past customer support reps and get fixed. Maybe, consumer bug reports are effectively ignored and only business accounts with strong account managers get stuff fixed.</p></htmltext>
<tokenext>I have not yet figured out how actual bug reports get past customer support reps and get fixed .
Maybe , consumer bug reports are effectively ignored and only business accounts with strong account managers get stuff fixed .</tokentext>
<sentencetext>I have not yet figured out how actual bug reports get past customer support reps and get fixed.
Maybe, consumer bug reports are effectively ignored and only business accounts with strong account managers get stuff fixed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151386</id>
	<title>Re:Rounding error?</title>
	<author>geekoid</author>
	<datestamp>1257083160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yeahn yeah, mod me as troll, but I am right.</p><p>Too many times have I seen these kinds of stupid inexcusable error. It drives me up a wall. The 'it's going to have ' bugs mentality is out of hand, and inexcusably stuff is allow to get through testing.</p><p>If we could get half the pride and professionalism then engineers are supposed to have into the software industry, it would be a good thing.</p></htmltext>
<tokenext>Yeahn yeah , mod me as troll , but I am right.Too many times have I seen these kinds of stupid inexcusable error .
It drives me up a wall .
The 'it 's going to have ' bugs mentality is out of hand , and inexcusably stuff is allow to get through testing.If we could get half the pride and professionalism then engineers are supposed to have into the software industry , it would be a good thing .</tokentext>
<sentencetext>Yeahn yeah, mod me as troll, but I am right.Too many times have I seen these kinds of stupid inexcusable error.
It drives me up a wall.
The 'it's going to have ' bugs mentality is out of hand, and inexcusably stuff is allow to get through testing.If we could get half the pride and professionalism then engineers are supposed to have into the software industry, it would be a good thing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148492</id>
	<title>So they tested it for less than 24.5 hours ...</title>
	<author>VitaminB52</author>
	<datestamp>1257069300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>... because if they had tested it for more than 24.5 hours then they would have found the bug immediately.</htmltext>
<tokenext>... because if they had tested it for more than 24.5 hours then they would have found the bug immediately .</tokentext>
<sentencetext>... because if they had tested it for more than 24.5 hours then they would have found the bug immediately.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148460</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>AaronW</author>
	<datestamp>1257069180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>When I first read about this that was the first thing that came into my mind as well. Elsewhere I found another post where a permanent fix should be available on December 11th, which is the day that the bug will re-appear.</p></htmltext>
<tokenext>When I first read about this that was the first thing that came into my mind as well .
Elsewhere I found another post where a permanent fix should be available on December 11th , which is the day that the bug will re-appear .</tokentext>
<sentencetext>When I first read about this that was the first thing that came into my mind as well.
Elsewhere I found another post where a permanent fix should be available on December 11th, which is the day that the bug will re-appear.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155540</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>MemoryDragon</author>
	<datestamp>1258642920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually Copilot8 is available for Android and it is better than my old tomtom PNA...<br>Since I live in Europe I wont even have access to googles solution, neither do I really want it.<br>(roaming everyone)</p></htmltext>
<tokenext>Actually Copilot8 is available for Android and it is better than my old tomtom PNA...Since I live in Europe I wont even have access to googles solution , neither do I really want it .
( roaming everyone )</tokentext>
<sentencetext>Actually Copilot8 is available for Android and it is better than my old tomtom PNA...Since I live in Europe I wont even have access to googles solution, neither do I really want it.
(roaming everyone)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151440</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150780</id>
	<title>Re:Time-releated bugs</title>
	<author>Boldoran</author>
	<datestamp>1257079740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That's what I call nice debugging.</htmltext>
<tokenext>That 's what I call nice debugging .</tokentext>
<sentencetext>That's what I call nice debugging.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314</id>
	<title>iPhone 3G/3GS GPS bug</title>
	<author>Anonymous</author>
	<datestamp>1257068520000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>Since we're talking about phone bugs, here's one I had to fight with for a while...</p><p>Lots of users are having problems with the GPS functionality on the iPhone 3G/3GS (see e.g. <a href="http://discussions.apple.com/thread.jspa?threadID=2045075&amp;start=0&amp;tstart=0" title="apple.com">here</a> [apple.com]). No apparent pattern there, but in Brazil, lots of users from one specific carrier were having GPS problems, and the beginning of these problems coincided with the start of Daylight Savings Time in Brazil. My iPhone, as well as my girlfriend's, are with this carrier and were experiencing the problem. Those with unlocked phones report trying other carriers' SIM cards and had GPS working again, but once you popped back the problematic carrier's SIM card, the GPS was dead again.</p><p>This nearly drove me nuts as I paid an obscene amount of money for the TomTom app and couldn't get it to work, so keeping up with the engineer spirit, I tried to debug the problem myself. I observed an interesting fact: there's a Clock app on the iPhone with a World Clock pane, and if I added a clock from any time zone, including my own, it was off by one hour. However the iPhone's main clock, shown on the top of the screen, was showing the right time. Eventually I discovered that if I restored my phone as a brand new phone (not restoring from backup) the GPS would work fine and world clocks would be fine... until you reboot the phone. After rebooting, the GPS is gone again and the world clock is off by one hour again.</p><p>Now you might ask what the time has to do with GPS. A lot, it turns out. GPS works by triangulating your distance from the satellites in the GPS constellation, which depends on knowing the exact position of the satellites. Since their orbits are corrected every so often, you must rely on so-called ephemeris data from each satellite, which is the required information to compute fairly exact orbits, and is updated fairly often (Wikipedia says GPS receivers should update ephemeris data every 4 hours). Originally this data is broadcast by the satellites themselves in their navigation message, at an awfully slow rate of 50 bits/s. You read it right, bits, not bytes or KB or MB, that's bits. As the navigation message is 1500 bits long, it takes at least 30 seconds to download it, which is about the time most standalone GPS receivers take to get a fix from a cold start (i.e. with stale ephemeris data). To work around this delay, most phones with GPS use the assisted-GPS variety, which downloads ephemeris data from a faster channel such as the cellular network. My theory is that some WTF-worthy excuse for an engineer at the carrier decided that, rather than doing time zone updates the right way, by updating configuration files to point to the new time zone, he'd just rather adjust the clock forward by one hour. The GPS chipset probably works with time zone neutral clocks so it asks for (say) UTC time and gets it off by one hour, and then computes the satellite orbits as though it were one hour later than it actually is. Obviously this means the triangulation computations go horribly wrong and rather than reporting something absurd, the chipset just pretends it couldn't get a fix.</p><p>It took a lot of complaining from a lot of people (to the carrier and to the government agencies responsible for telecommunications), but the carrier finally fixed the problem. However, it was a nightmare trying to deal with clueless customer support representatives who didn't try in the least to help (and probably were thinking all along `what does this wacko think GPS has to do with DST?'), just blindly suggesting that we restore the phone, or even try to uninstall the built-in Maps app, or blaming it on Apple and saying they weren't responsible -- and never mind that unlocked phones with SIM cards from other carriers worked fine, and that the iPhone support situation is unique in Brazil as Apple outsourced support to the carriers themselves. In the end, the customer support WTFs would be worth another post of its own, at least twice the size of this one.</p><p>But</p></htmltext>
<tokenext>Since we 're talking about phone bugs , here 's one I had to fight with for a while...Lots of users are having problems with the GPS functionality on the iPhone 3G/3GS ( see e.g .
here [ apple.com ] ) .
No apparent pattern there , but in Brazil , lots of users from one specific carrier were having GPS problems , and the beginning of these problems coincided with the start of Daylight Savings Time in Brazil .
My iPhone , as well as my girlfriend 's , are with this carrier and were experiencing the problem .
Those with unlocked phones report trying other carriers ' SIM cards and had GPS working again , but once you popped back the problematic carrier 's SIM card , the GPS was dead again.This nearly drove me nuts as I paid an obscene amount of money for the TomTom app and could n't get it to work , so keeping up with the engineer spirit , I tried to debug the problem myself .
I observed an interesting fact : there 's a Clock app on the iPhone with a World Clock pane , and if I added a clock from any time zone , including my own , it was off by one hour .
However the iPhone 's main clock , shown on the top of the screen , was showing the right time .
Eventually I discovered that if I restored my phone as a brand new phone ( not restoring from backup ) the GPS would work fine and world clocks would be fine... until you reboot the phone .
After rebooting , the GPS is gone again and the world clock is off by one hour again.Now you might ask what the time has to do with GPS .
A lot , it turns out .
GPS works by triangulating your distance from the satellites in the GPS constellation , which depends on knowing the exact position of the satellites .
Since their orbits are corrected every so often , you must rely on so-called ephemeris data from each satellite , which is the required information to compute fairly exact orbits , and is updated fairly often ( Wikipedia says GPS receivers should update ephemeris data every 4 hours ) .
Originally this data is broadcast by the satellites themselves in their navigation message , at an awfully slow rate of 50 bits/s .
You read it right , bits , not bytes or KB or MB , that 's bits .
As the navigation message is 1500 bits long , it takes at least 30 seconds to download it , which is about the time most standalone GPS receivers take to get a fix from a cold start ( i.e .
with stale ephemeris data ) .
To work around this delay , most phones with GPS use the assisted-GPS variety , which downloads ephemeris data from a faster channel such as the cellular network .
My theory is that some WTF-worthy excuse for an engineer at the carrier decided that , rather than doing time zone updates the right way , by updating configuration files to point to the new time zone , he 'd just rather adjust the clock forward by one hour .
The GPS chipset probably works with time zone neutral clocks so it asks for ( say ) UTC time and gets it off by one hour , and then computes the satellite orbits as though it were one hour later than it actually is .
Obviously this means the triangulation computations go horribly wrong and rather than reporting something absurd , the chipset just pretends it could n't get a fix.It took a lot of complaining from a lot of people ( to the carrier and to the government agencies responsible for telecommunications ) , but the carrier finally fixed the problem .
However , it was a nightmare trying to deal with clueless customer support representatives who did n't try in the least to help ( and probably were thinking all along ` what does this wacko think GPS has to do with DST ?
' ) , just blindly suggesting that we restore the phone , or even try to uninstall the built-in Maps app , or blaming it on Apple and saying they were n't responsible -- and never mind that unlocked phones with SIM cards from other carriers worked fine , and that the iPhone support situation is unique in Brazil as Apple outsourced support to the carriers themselves .
In the end , the customer support WTFs would be worth another post of its own , at least twice the size of this one.But</tokentext>
<sentencetext>Since we're talking about phone bugs, here's one I had to fight with for a while...Lots of users are having problems with the GPS functionality on the iPhone 3G/3GS (see e.g.
here [apple.com]).
No apparent pattern there, but in Brazil, lots of users from one specific carrier were having GPS problems, and the beginning of these problems coincided with the start of Daylight Savings Time in Brazil.
My iPhone, as well as my girlfriend's, are with this carrier and were experiencing the problem.
Those with unlocked phones report trying other carriers' SIM cards and had GPS working again, but once you popped back the problematic carrier's SIM card, the GPS was dead again.This nearly drove me nuts as I paid an obscene amount of money for the TomTom app and couldn't get it to work, so keeping up with the engineer spirit, I tried to debug the problem myself.
I observed an interesting fact: there's a Clock app on the iPhone with a World Clock pane, and if I added a clock from any time zone, including my own, it was off by one hour.
However the iPhone's main clock, shown on the top of the screen, was showing the right time.
Eventually I discovered that if I restored my phone as a brand new phone (not restoring from backup) the GPS would work fine and world clocks would be fine... until you reboot the phone.
After rebooting, the GPS is gone again and the world clock is off by one hour again.Now you might ask what the time has to do with GPS.
A lot, it turns out.
GPS works by triangulating your distance from the satellites in the GPS constellation, which depends on knowing the exact position of the satellites.
Since their orbits are corrected every so often, you must rely on so-called ephemeris data from each satellite, which is the required information to compute fairly exact orbits, and is updated fairly often (Wikipedia says GPS receivers should update ephemeris data every 4 hours).
Originally this data is broadcast by the satellites themselves in their navigation message, at an awfully slow rate of 50 bits/s.
You read it right, bits, not bytes or KB or MB, that's bits.
As the navigation message is 1500 bits long, it takes at least 30 seconds to download it, which is about the time most standalone GPS receivers take to get a fix from a cold start (i.e.
with stale ephemeris data).
To work around this delay, most phones with GPS use the assisted-GPS variety, which downloads ephemeris data from a faster channel such as the cellular network.
My theory is that some WTF-worthy excuse for an engineer at the carrier decided that, rather than doing time zone updates the right way, by updating configuration files to point to the new time zone, he'd just rather adjust the clock forward by one hour.
The GPS chipset probably works with time zone neutral clocks so it asks for (say) UTC time and gets it off by one hour, and then computes the satellite orbits as though it were one hour later than it actually is.
Obviously this means the triangulation computations go horribly wrong and rather than reporting something absurd, the chipset just pretends it couldn't get a fix.It took a lot of complaining from a lot of people (to the carrier and to the government agencies responsible for telecommunications), but the carrier finally fixed the problem.
However, it was a nightmare trying to deal with clueless customer support representatives who didn't try in the least to help (and probably were thinking all along `what does this wacko think GPS has to do with DST?
'), just blindly suggesting that we restore the phone, or even try to uninstall the built-in Maps app, or blaming it on Apple and saying they weren't responsible -- and never mind that unlocked phones with SIM cards from other carriers worked fine, and that the iPhone support situation is unique in Brazil as Apple outsourced support to the carriers themselves.
In the end, the customer support WTFs would be worth another post of its own, at least twice the size of this one.But</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30164514</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>BikeHelmet</author>
	<datestamp>1258628520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>It's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number, thus breaking the algorithm when it measures time deltas and causing it to mis focus before snapping the picture.</p></div><p>How do programmers make these mistakes? Hell, I wrote an FPS counter for a game that was aware of signed ints suddenly going negative, and accounted for it.</p></div>
	</htmltext>
<tokenext>It 's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number , thus breaking the algorithm when it measures time deltas and causing it to mis focus before snapping the picture.How do programmers make these mistakes ?
Hell , I wrote an FPS counter for a game that was aware of signed ints suddenly going negative , and accounted for it .</tokentext>
<sentencetext>It's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number, thus breaking the algorithm when it measures time deltas and causing it to mis focus before snapping the picture.How do programmers make these mistakes?
Hell, I wrote an FPS counter for a game that was aware of signed ints suddenly going negative, and accounted for it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148916</id>
	<title>Far more serious bugs</title>
	<author>Anonymous</author>
	<datestamp>1257071280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm still waiting for an acknowledgement that a fix is in the works for a <a href="http://code.google.com/p/android/issues/detail?id=4653" title="google.com" rel="nofollow">bug causing the speaker to stop working (no phone ring, no alarm)</a> [google.com]<br>and for <a href="http://code.google.com/p/android/issues/detail?id=1181" title="google.com" rel="nofollow">hands-free support</a> [google.com]</p><p>As far as I can tell, there has been no comment on Verizon/Google/Motorola on these serious issues.</p><p>I love the phone, but the software was clearly rushed to market.</p></htmltext>
<tokenext>I 'm still waiting for an acknowledgement that a fix is in the works for a bug causing the speaker to stop working ( no phone ring , no alarm ) [ google.com ] and for hands-free support [ google.com ] As far as I can tell , there has been no comment on Verizon/Google/Motorola on these serious issues.I love the phone , but the software was clearly rushed to market .</tokentext>
<sentencetext>I'm still waiting for an acknowledgement that a fix is in the works for a bug causing the speaker to stop working (no phone ring, no alarm) [google.com]and for hands-free support [google.com]As far as I can tell, there has been no comment on Verizon/Google/Motorola on these serious issues.I love the phone, but the software was clearly rushed to market.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149646</id>
	<title>Obviously related to</title>
	<author>Anonymous</author>
	<datestamp>1257074760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>solar rotation:</p><blockquote><div><p>The solar rotation period, by the way, is about 24.5 days at its equator</p></div></blockquote><p> <i> <a href="http://en.fairmormon.org/Book\_of\_Abraham/Astronomy/Revolution\_Time" title="fairmormon.org" rel="nofollow">according to the Mormons</a> [fairmormon.org] </i></p></div>
	</htmltext>
<tokenext>solar rotation : The solar rotation period , by the way , is about 24.5 days at its equator according to the Mormons [ fairmormon.org ]</tokentext>
<sentencetext>solar rotation:The solar rotation period, by the way, is about 24.5 days at its equator  according to the Mormons [fairmormon.org] 
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152238</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>Falconhell</author>
	<datestamp>1257088860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"What I've seen is that some chargers power any USB powered equipment (including those on my PCs and laptops) and other wall and car chargers only power *some* USB powered equipment"</p><p>Quite so. We glider pilots have been using IPAQ<br>31X navigators which also use the mini USB, and have found they will not charge at a rate sufficient to run the unit without feeding 3.3v on each of the USB data lines, it seems these are used to tell the unit to switch to a fast charge.</p><p>The slow charge mode flattens the battery if charging and operating simultaneously is required.</p><p>Damn pest!</p></htmltext>
<tokenext>" What I 've seen is that some chargers power any USB powered equipment ( including those on my PCs and laptops ) and other wall and car chargers only power * some * USB powered equipment " Quite so .
We glider pilots have been using IPAQ31X navigators which also use the mini USB , and have found they will not charge at a rate sufficient to run the unit without feeding 3.3v on each of the USB data lines , it seems these are used to tell the unit to switch to a fast charge.The slow charge mode flattens the battery if charging and operating simultaneously is required.Damn pest !</tokentext>
<sentencetext>"What I've seen is that some chargers power any USB powered equipment (including those on my PCs and laptops) and other wall and car chargers only power *some* USB powered equipment"Quite so.
We glider pilots have been using IPAQ31X navigators which also use the mini USB, and have found they will not charge at a rate sufficient to run the unit without feeding 3.3v on each of the USB data lines, it seems these are used to tell the unit to switch to a fast charge.The slow charge mode flattens the battery if charging and operating simultaneously is required.Damn pest!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151440</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151066</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Renegrade</author>
	<datestamp>1257081300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Ah if it's a continual focus/ai-servo it will definitely need a delta-time to figure out the rate that the subject is moving towards or away from the film plane.

</p><p>I'm not sure that a cameraphone would have ai-servo mode though....

</p><p>Other processes in the focusing system would require delays or such as well, and they <i>might</i> not have a convenient sleep() type call available to them for a variety of reasons (the execution context may prevent calling it, it may not be available, performance of said call might be poor, etcetc)..</p></htmltext>
<tokenext>Ah if it 's a continual focus/ai-servo it will definitely need a delta-time to figure out the rate that the subject is moving towards or away from the film plane .
I 'm not sure that a cameraphone would have ai-servo mode though... . Other processes in the focusing system would require delays or such as well , and they might not have a convenient sleep ( ) type call available to them for a variety of reasons ( the execution context may prevent calling it , it may not be available , performance of said call might be poor , etcetc ) . .</tokentext>
<sentencetext>Ah if it's a continual focus/ai-servo it will definitely need a delta-time to figure out the rate that the subject is moving towards or away from the film plane.
I'm not sure that a cameraphone would have ai-servo mode though....

Other processes in the focusing system would require delays or such as well, and they might not have a convenient sleep() type call available to them for a variety of reasons (the execution context may prevent calling it, it may not be available, performance of said call might be poor, etcetc)..</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148200</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147944</id>
	<title>Re:Auto-Focus</title>
	<author>Anonymous</author>
	<datestamp>1257066480000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext>Erm. Actually, Droid DOES. Just not all the time... I suppose that's not as funny, though, so may I recommend:<br>
<br>
"Sporadically bugs: iDoesn't. Droid does."</htmltext>
<tokenext>Erm .
Actually , Droid DOES .
Just not all the time... I suppose that 's not as funny , though , so may I recommend : " Sporadically bugs : iDoes n't .
Droid does .
"</tokentext>
<sentencetext>Erm.
Actually, Droid DOES.
Just not all the time... I suppose that's not as funny, though, so may I recommend:

"Sporadically bugs: iDoesn't.
Droid does.
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155438</id>
	<title>How many more?</title>
	<author>Anonymous</author>
	<datestamp>1258642320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is the kind of bug other operating systems can only dream of!</p></htmltext>
<tokenext>This is the kind of bug other operating systems can only dream of !</tokentext>
<sentencetext>This is the kind of bug other operating systems can only dream of!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</id>
	<title>When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257109140000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>

It's all over the comments on the engadget page but since 2^31 milliseconds is about 24.5 days, it's highly probably we're dealing with <a href="http://en.wikipedia.org/wiki/Sign\_extension" title="wikipedia.org">a very classic not so funny sign extension bug here</a> [wikipedia.org].  So if I may presume the real problem, it's that autofocusing depends on catching timestamps from the system to know how long it's been since the last sampling in order to adjust the lens and check for accuracy.  It's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number, thus breaking the algorithm when it measures time deltas and causing it to mis focus before snapping the picture.  <br> <br>The patch is simple, make that signed int something like an unsigned long or truncate it properly.  Hopefully we're not waiting long.</htmltext>
<tokenext>It 's all over the comments on the engadget page but since 2 ^ 31 milliseconds is about 24.5 days , it 's highly probably we 're dealing with a very classic not so funny sign extension bug here [ wikipedia.org ] .
So if I may presume the real problem , it 's that autofocusing depends on catching timestamps from the system to know how long it 's been since the last sampling in order to adjust the lens and check for accuracy .
It 's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number , thus breaking the algorithm when it measures time deltas and causing it to mis focus before snapping the picture .
The patch is simple , make that signed int something like an unsigned long or truncate it properly .
Hopefully we 're not waiting long .</tokentext>
<sentencetext>

It's all over the comments on the engadget page but since 2^31 milliseconds is about 24.5 days, it's highly probably we're dealing with a very classic not so funny sign extension bug here [wikipedia.org].
So if I may presume the real problem, it's that autofocusing depends on catching timestamps from the system to know how long it's been since the last sampling in order to adjust the lens and check for accuracy.
It's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number, thus breaking the algorithm when it measures time deltas and causing it to mis focus before snapping the picture.
The patch is simple, make that signed int something like an unsigned long or truncate it properly.
Hopefully we're not waiting long.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150158</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>AaronW</author>
	<datestamp>1257076560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>On mine, the turn by turn navigation is right-on. Charging works just fine plugging it into my desktop computer's USB port. My biggest beef so far is that the PPTP VPN won't stay up more than a few minutes.</p><p>I imagine that the rough edges will be fixed since it's a major new release.</p></htmltext>
<tokenext>On mine , the turn by turn navigation is right-on .
Charging works just fine plugging it into my desktop computer 's USB port .
My biggest beef so far is that the PPTP VPN wo n't stay up more than a few minutes.I imagine that the rough edges will be fixed since it 's a major new release .</tokentext>
<sentencetext>On mine, the turn by turn navigation is right-on.
Charging works just fine plugging it into my desktop computer's USB port.
My biggest beef so far is that the PPTP VPN won't stay up more than a few minutes.I imagine that the rough edges will be fixed since it's a major new release.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149448</id>
	<title>Re:Time-releated bugs</title>
	<author>Anonymous</author>
	<datestamp>1257073860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>There are many of these bugs caused by translations. My favorite is the title bar of non-responding programs in the Dutch Windows XP: it drops the last letters from "Dit programma reageerd niet."  I guess they never tested a locked up program.</p></htmltext>
<tokenext>There are many of these bugs caused by translations .
My favorite is the title bar of non-responding programs in the Dutch Windows XP : it drops the last letters from " Dit programma reageerd niet .
" I guess they never tested a locked up program .</tokentext>
<sentencetext>There are many of these bugs caused by translations.
My favorite is the title bar of non-responding programs in the Dutch Windows XP: it drops the last letters from "Dit programma reageerd niet.
"  I guess they never tested a locked up program.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149112</id>
	<title>Re:IIRC, this is the same sort of bug</title>
	<author>Anonymous</author>
	<datestamp>1257072300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Actually, 48. They used unsigned integers<nobr> <wbr></nobr>:D</p></htmltext>
<tokenext>Actually , 48 .
They used unsigned integers : D</tokentext>
<sentencetext>Actually, 48.
They used unsigned integers :D</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148382</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148970</id>
	<title>Re:Alleged...</title>
	<author>Artraze</author>
	<datestamp>1257071580000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>You kid, and I can appreciate the humor, but it was stated that way as a matter of journalistic integrity.  Rather than claiming the the true Dan Morrill posted this (which they have no proof of) they stated what they did know: the person that posted this says he's Dan Morrill.  That way if it turns out that Dan Morrill didn't actually post it, they've not put word into someone's mouth, as it were, and only need to release an update along the lines of "Bug discoverer really someone else".</p><p>It's sad that we've become so used to the modern media's 'report what you think happened and maybe correct yourself later if you're called on it' style that phrases like this are actually worthy of comment, humorous or otherwise....</p></htmltext>
<tokenext>You kid , and I can appreciate the humor , but it was stated that way as a matter of journalistic integrity .
Rather than claiming the the true Dan Morrill posted this ( which they have no proof of ) they stated what they did know : the person that posted this says he 's Dan Morrill .
That way if it turns out that Dan Morrill did n't actually post it , they 've not put word into someone 's mouth , as it were , and only need to release an update along the lines of " Bug discoverer really someone else " .It 's sad that we 've become so used to the modern media 's 'report what you think happened and maybe correct yourself later if you 're called on it ' style that phrases like this are actually worthy of comment , humorous or otherwise... .</tokentext>
<sentencetext>You kid, and I can appreciate the humor, but it was stated that way as a matter of journalistic integrity.
Rather than claiming the the true Dan Morrill posted this (which they have no proof of) they stated what they did know: the person that posted this says he's Dan Morrill.
That way if it turns out that Dan Morrill didn't actually post it, they've not put word into someone's mouth, as it were, and only need to release an update along the lines of "Bug discoverer really someone else".It's sad that we've become so used to the modern media's 'report what you think happened and maybe correct yourself later if you're called on it' style that phrases like this are actually worthy of comment, humorous or otherwise....</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147938</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148938</id>
	<title>Re:iFocus ... NOT</title>
	<author>NervousWreck</author>
	<datestamp>1257071340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>*hand pass* we can go about our business</htmltext>
<tokenext>* hand pass * we can go about our business</tokentext>
<sentencetext>*hand pass* we can go about our business</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148448</id>
	<title>So...only 24 days of testing?</title>
	<author>the\_Librarian</author>
	<datestamp>1257069060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Given that this bug made it out into the wild, does this mean that the Android team only did 24 days of beta testing of the product? Or that they thought they would release a patch within 24 days?</p><p>Not particularly smart or impressive, either way.</p></htmltext>
<tokenext>Given that this bug made it out into the wild , does this mean that the Android team only did 24 days of beta testing of the product ?
Or that they thought they would release a patch within 24 days ? Not particularly smart or impressive , either way .</tokentext>
<sentencetext>Given that this bug made it out into the wild, does this mean that the Android team only did 24 days of beta testing of the product?
Or that they thought they would release a patch within 24 days?Not particularly smart or impressive, either way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149766</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257075180000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Our jokes aren't like your jokes</p></div></div>
	</htmltext>
<tokenext>Our jokes are n't like your jokes</tokentext>
<sentencetext>Our jokes aren't like your jokes
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148060</id>
	<title>IIRC, this is the same sort of bug</title>
	<author>Anonymous</author>
	<datestamp>1257066960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>that caused Windows 95 to require a reboot in about the same timeframe.</p></htmltext>
<tokenext>that caused Windows 95 to require a reboot in about the same timeframe .</tokentext>
<sentencetext>that caused Windows 95 to require a reboot in about the same timeframe.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148236</id>
	<title>in Action...</title>
	<author>TrippTDF</author>
	<datestamp>1257068100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I can verify this-  I got a Droid on launch day, and one thing that drove me nuts was how long it took a barcode scanning app to focus and accquire the barcode... i just tried it again after writing off that ability, and sure enough, the time to focus is much, much shorter now.</htmltext>
<tokenext>I can verify this- I got a Droid on launch day , and one thing that drove me nuts was how long it took a barcode scanning app to focus and accquire the barcode... i just tried it again after writing off that ability , and sure enough , the time to focus is much , much shorter now .</tokentext>
<sentencetext>I can verify this-  I got a Droid on launch day, and one thing that drove me nuts was how long it took a barcode scanning app to focus and accquire the barcode... i just tried it again after writing off that ability, and sure enough, the time to focus is much, much shorter now.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149178</id>
	<title>Patriot's Ghost</title>
	<author>Tablizer</author>
	<datestamp>1257072540000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Hmmm, did the auto-focus programmer used to work on the Patriot anti-missile system?<br>
&nbsp; &nbsp;</p></htmltext>
<tokenext>Hmmm , did the auto-focus programmer used to work on the Patriot anti-missile system ?
   </tokentext>
<sentencetext>Hmmm, did the auto-focus programmer used to work on the Patriot anti-missile system?
   </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148382</id>
	<title>Re:IIRC, this is the same sort of bug</title>
	<author>kalirion</author>
	<datestamp>1257068760000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>Same timeframe? You could actually keep a Win 95 system up and running for 24 days?</p></htmltext>
<tokenext>Same timeframe ?
You could actually keep a Win 95 system up and running for 24 days ?</tokentext>
<sentencetext>Same timeframe?
You could actually keep a Win 95 system up and running for 24 days?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148060</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150478</id>
	<title>Re:Bigger bugs afoot...</title>
	<author>Darth\_brooks</author>
	<datestamp>1257078120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The charging issue is inherent to motorola phones. My old phone (motorola razr) refused to believe that a mini-usb cable could supply the needed power without a charger. Plugging into a PC woudn't charge it. My droid doesn't have that particular problem, but i haven't tried many 3rd party chargers yet.</p></htmltext>
<tokenext>The charging issue is inherent to motorola phones .
My old phone ( motorola razr ) refused to believe that a mini-usb cable could supply the needed power without a charger .
Plugging into a PC woud n't charge it .
My droid does n't have that particular problem , but i have n't tried many 3rd party chargers yet .</tokentext>
<sentencetext>The charging issue is inherent to motorola phones.
My old phone (motorola razr) refused to believe that a mini-usb cable could supply the needed power without a charger.
Plugging into a PC woudn't charge it.
My droid doesn't have that particular problem, but i haven't tried many 3rd party chargers yet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149340</id>
	<title>Great now your phone has a monthly cycle too.</title>
	<author>Anonymous</author>
	<datestamp>1257073380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Only the bad part of the cycle is as long as the good part of the cycle.</p></htmltext>
<tokenext>Only the bad part of the cycle is as long as the good part of the cycle .</tokentext>
<sentencetext>Only the bad part of the cycle is as long as the good part of the cycle.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147864</id>
	<title>Does it use an Intel CPU?</title>
	<author>Anonymous</author>
	<datestamp>1257066060000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Just curious.....</p></htmltext>
<tokenext>Just curious.... .</tokentext>
<sentencetext>Just curious.....</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148578</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>noidentity</author>
	<datestamp>1257069600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>it's highly probably we're dealing with a very classic not so funny sign extension bug here [...] It's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number</p></div>
</blockquote><p>This involves truncation, not sign-extension, actually. Sign-extension occurs when widening a value, not narrowing it. A value outside the range representable by a two's complement 32-bit integer is being cast to one, and apparently this platform simply truncates to 32 bits and treats the highest bit as having the value -2^31, rather than 2^31 as it had in the input value. This isn't the only way to handle such a situation; common alternatives are raising an exception or saturating (i.e. anything &gt;= 2^31 converts to 2^31-1, and anything less than -2^31 converts to -2^31).</p></div>
	</htmltext>
<tokenext>it 's highly probably we 're dealing with a very classic not so funny sign extension bug here [ ... ] It 's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number This involves truncation , not sign-extension , actually .
Sign-extension occurs when widening a value , not narrowing it .
A value outside the range representable by a two 's complement 32-bit integer is being cast to one , and apparently this platform simply truncates to 32 bits and treats the highest bit as having the value -2 ^ 31 , rather than 2 ^ 31 as it had in the input value .
This is n't the only way to handle such a situation ; common alternatives are raising an exception or saturating ( i.e .
anything &gt; = 2 ^ 31 converts to 2 ^ 31-1 , and anything less than -2 ^ 31 converts to -2 ^ 31 ) .</tokentext>
<sentencetext>it's highly probably we're dealing with a very classic not so funny sign extension bug here [...] It's casting this to a signed 32 bit variable which means that during the 24.5 days it is miscast to a negative number
This involves truncation, not sign-extension, actually.
Sign-extension occurs when widening a value, not narrowing it.
A value outside the range representable by a two's complement 32-bit integer is being cast to one, and apparently this platform simply truncates to 32 bits and treats the highest bit as having the value -2^31, rather than 2^31 as it had in the input value.
This isn't the only way to handle such a situation; common alternatives are raising an exception or saturating (i.e.
anything &gt;= 2^31 converts to 2^31-1, and anything less than -2^31 converts to -2^31).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148816</id>
	<title>I was suspecting something like...</title>
	<author>Hymer</author>
	<datestamp>1257070680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...camera will only focus on breast/nippels due to testing only done on this item.<br>...and it shows up as a simple rounding bug, how disapointing.</p></htmltext>
<tokenext>...camera will only focus on breast/nippels due to testing only done on this item....and it shows up as a simple rounding bug , how disapointing .</tokentext>
<sentencetext>...camera will only focus on breast/nippels due to testing only done on this item....and it shows up as a simple rounding bug, how disapointing.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147990</id>
	<title>Re:Auto-Focus</title>
	<author>josteos</author>
	<datestamp>1257066600000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>... Droid might</htmltext>
<tokenext>... Droid might</tokentext>
<sentencetext>... Droid might</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30159950</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Thuktun</author>
	<datestamp>1258657320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>2^31 milliseconds is about 24.5 days</p></div><p>This is exactly what I thought on reading the headline.  It's closer to 24.85 days.</p></div>
	</htmltext>
<tokenext>2 ^ 31 milliseconds is about 24.5 daysThis is exactly what I thought on reading the headline .
It 's closer to 24.85 days .</tokentext>
<sentencetext>2^31 milliseconds is about 24.5 daysThis is exactly what I thought on reading the headline.
It's closer to 24.85 days.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149270</id>
	<title>Re:Auto-Focus</title>
	<author>Anonymous</author>
	<datestamp>1257073020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Sorry. Focusing based on calendar - Droid Does, Bitches.</htmltext>
<tokenext>Sorry .
Focusing based on calendar - Droid Does , Bitches .</tokentext>
<sentencetext>Sorry.
Focusing based on calendar - Droid Does, Bitches.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154680</id>
	<title>Motorola</title>
	<author>Fotograf</author>
	<datestamp>1258634940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>yea and soon they will discover that it is not only signed, but also byte inverted.</htmltext>
<tokenext>yea and soon they will discover that it is not only signed , but also byte inverted .</tokentext>
<sentencetext>yea and soon they will discover that it is not only signed, but also byte inverted.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151098</id>
	<title>Re:Auto-Focus</title>
	<author>Anonymous</author>
	<datestamp>1257081540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>its that Droid of the month...</p></htmltext>
<tokenext>its that Droid of the month.. .</tokentext>
<sentencetext>its that Droid of the month...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147990</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980</id>
	<title>iFocus ... NOT</title>
	<author>OzPeter</author>
	<datestamp>1257066600000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>This is definitely NOT the Droid you are looking for</htmltext>
<tokenext>This is definitely NOT the Droid you are looking for</tokentext>
<sentencetext>This is definitely NOT the Droid you are looking for</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148946</id>
	<title>Re:Time-releated bugs</title>
	<author>Anonymous</author>
	<datestamp>1257071460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>sorry, please see [[phase of the sun]]</p></htmltext>
<tokenext>sorry , please see [ [ phase of the sun ] ]</tokentext>
<sentencetext>sorry, please see [[phase of the sun]]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148506</id>
	<title>Re:When Signed/Unsigned Strikes</title>
	<author>Anonymous</author>
	<datestamp>1257069300000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>Wish I had mod points, this entire thread is one of the funniest ever on<nobr> <wbr></nobr>/.</p></htmltext>
<tokenext>Wish I had mod points , this entire thread is one of the funniest ever on / .</tokentext>
<sentencetext>Wish I had mod points, this entire thread is one of the funniest ever on /.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147938</id>
	<title>Alleged...</title>
	<author>Anonymous</author>
	<datestamp>1257066480000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p><i>by someone claiming to be Google engineer Dan Morrill</i></p><p>Yeah, it could also be one of those lame Dan Morrill impersonators who solve perplexing engineering/programming issues, then post the solution under his name.  MAN that's annoying..</p></htmltext>
<tokenext>by someone claiming to be Google engineer Dan MorrillYeah , it could also be one of those lame Dan Morrill impersonators who solve perplexing engineering/programming issues , then post the solution under his name .
MAN that 's annoying. .</tokentext>
<sentencetext>by someone claiming to be Google engineer Dan MorrillYeah, it could also be one of those lame Dan Morrill impersonators who solve perplexing engineering/programming issues, then post the solution under his name.
MAN that's annoying..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149750</id>
	<title>Pfff...</title>
	<author>Hurricane78</author>
	<datestamp>1257075120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I thought it was about <strong>Androids</strong>. Maybe military ones. Or at least ones with auto-focusing cameras as eyes.<br>And them behaving bizarrely human-like.</p><p>Now <em>that</em> would be a real story!</p><p>Who cares about some crappy niche phone?</p><p>I want my &ldquo;drone wars&rdquo;! <em>Now!</em><br>That would also solve the problem of people caring about unimportant shit like this. ^^</p></htmltext>
<tokenext>I thought it was about Androids .
Maybe military ones .
Or at least ones with auto-focusing cameras as eyes.And them behaving bizarrely human-like.Now that would be a real story ! Who cares about some crappy niche phone ? I want my    drone wars    !
Now ! That would also solve the problem of people caring about unimportant shit like this .
^ ^</tokentext>
<sentencetext>I thought it was about Androids.
Maybe military ones.
Or at least ones with auto-focusing cameras as eyes.And them behaving bizarrely human-like.Now that would be a real story!Who cares about some crappy niche phone?I want my “drone wars”!
Now!That would also solve the problem of people caring about unimportant shit like this.
^^</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30153416
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148134
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30172672
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148318
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148210
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155190
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148982
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150426
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149056
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30166904
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148946
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147990
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148356
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147938
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148970
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148634
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148754
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148938
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148326
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149220
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150228
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147894
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149060
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148738
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149838
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30159950
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152680
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150780
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148574
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148430
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148998
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148060
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148764
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148104
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148492
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154624
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154262
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148874
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148160
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149930
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30164514
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148200
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151066
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152226
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148848
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149766
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149292
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150158
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152112
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149448
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149178
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147944
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148940
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151440
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152238
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148060
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149112
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150478
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151440
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155540
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148066
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154384
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149142
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30153468
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148492
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148742
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149034
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150230
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149270
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149388
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30157276
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148066
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148194
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149192
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148200
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147990
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151098
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151386
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148306
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148506
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148562
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148460
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148468
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_18_1943209_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148578
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148738
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149838
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148314
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30172672
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154262
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149388
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30157276
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148492
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148742
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154624
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148060
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148382
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149112
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148764
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147926
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148066
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148194
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149192
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30154384
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147870
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147944
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148940
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147990
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148356
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151098
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149270
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147842
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148142
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149292
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148562
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148574
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30164514
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150228
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148134
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152226
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152680
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148982
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148460
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148306
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30159950
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148874
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148210
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148848
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149142
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30153468
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148160
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148578
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148104
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149178
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148200
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151066
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149544
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149930
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148026
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148468
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148506
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149766
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149056
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150426
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149750
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147864
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147938
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148970
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149512
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148826
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149374
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149034
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150230
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30153416
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150478
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150158
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151440
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155540
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152238
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30155190
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30166904
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148916
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147980
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152058
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148938
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30152112
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148232
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148430
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148998
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148174
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148634
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30151386
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148318
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148794
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148054
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148946
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150780
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149448
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148754
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30148326
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149220
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30150766
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_18_1943209.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30147894
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_18_1943209.30149060
</commentlist>
</conversation>
