tag:blogger.com,1999:blog-43734187204208798592024-02-06T23:37:34.000-05:00Error ProcessingA discussion of how software handles errors. Send your screenshots!<br>A <a href="http://bit.ly/2lyh9a"> Knowlengr</a> siteknowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.comBlogger24125tag:blogger.com,1999:blog-4373418720420879859.post-84930190686407359412016-03-14T10:37:00.001-04:002016-03-14T10:42:55.299-04:00Cybersecurity Vendor Error Message: Taking Heat in UC Campus Big Data Surveillance Dispute?<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvDRPsveIdr7ncWXRNNC5HtaScd5AXFkX0tkDtsWRnD8VoHmnZK9J62hhaDqV4i5JfpJ6SVPsKeoQp-8dallFqfXYuWX9YiCnhUZeAUonENxBwHSbbjOw1qx5J9rd8BdZ9ktbPyNFxiplS/s1600/fidelis-xps-page-20160314-ucsystem-surveillance.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="233" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvDRPsveIdr7ncWXRNNC5HtaScd5AXFkX0tkDtsWRnD8VoHmnZK9J62hhaDqV4i5JfpJ6SVPsKeoQp-8dallFqfXYuWX9YiCnhUZeAUonENxBwHSbbjOw1qx5J9rd8BdZ9ktbPyNFxiplS/s400/fidelis-xps-page-20160314-ucsystem-surveillance.png" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Screenshot from Fidelis XPS web page </td></tr>
</tbody></table>
<div style="text-align: justify;">
The handling of a cybersecurity appliance manufactured by Fidelis is at the center of a <a href="http://bit.ly/1pj87IB" target="_blank">dispute between University of California cybersec experts and UC administrators</a> working to contain recent breaches. </div>
<br />
<div style="text-align: justify;">
Whether by design or by accident, the vendor's web page describing the particular model involved is throwing this inelegant error.</div>
<br />
<div style="text-align: justify;">
<b>SNIP</b> According to a Univ of California faculty expert, . . .'These appliances, depending on how they are configured, can be privacy doomsday machines.'"</div>
<br />
<div style="text-align: justify;">
Full packet inspection = #BigData threatening #privacy | @academeblog @FidelisCyber #governance #standards http://bit.ly/1pj87IB @bigdatastandards #computersecurity #cybersecurity</div>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com1tag:blogger.com,1999:blog-4373418720420879859.post-18342123546942645392016-01-18T14:48:00.001-05:002016-01-18T14:48:33.911-05:00FooPlugins - Internal Server Error<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><img border="0" height="111" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6MBV9JVldK3gX0PTcE4EEwQh782cVNVi7jlMuGpD-HgcPPW4gb3VJjsuTg7ZL5KYgKZWPmCrtw4QYrxCOrVboh-XWOhkfqzPcQDdrw9sXESIMH4w3VmFhXg8xQOFAa6GmvuYkJzkNTr_D/s400/fooplugins-postflow-page-internal-server-201601181444.png" style="margin-left: auto; margin-right: auto;" width="400" /></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Webserver error at Fooplugins.com</td></tr>
</tbody></table>
<br />
Today this Apache webserver <a href="http://fooplugins.com/plugins/postflow/" target="_blank">error is being thrown at Fooplugins</a>. Will this ubiquitous error still be with us twenty years hence?<br />
<br />
<br />
<br />
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-84209762380531444372015-09-21T11:44:00.001-04:002015-09-21T11:44:20.139-04:00Skype Network Issue - Except for Business Users Skype is currently unusable in our East Coast USA location over the Verizon FIOS network. The symptom is a failure to connect, even if already logged in.<br />
<br />
The Windows client does not suggest the Heartbeat site for status, but here it is anyway. Nor does it send a notification of the outage to users by email or text.<br />
<br />
Skype Heartbeat reports:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8KilIaLfXK8BIwpSbOBnUGPYDQKjBD4oYeZb6zTEgANG7LCMLdaoEmXnIQivgJtuow0eRG7pYMu9Kkgk2rmS5-Nh1bRKQRcluHdQwJuM8mdR-pk-PtwI-3YO0FLvFyf_5ya3M0Wp6V88J/s1600/skype-cannot-connect-20150921-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="225" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8KilIaLfXK8BIwpSbOBnUGPYDQKjBD4oYeZb6zTEgANG7LCMLdaoEmXnIQivgJtuow0eRG7pYMu9Kkgk2rmS5-Nh1bRKQRcluHdQwJuM8mdR-pk-PtwI-3YO0FLvFyf_5ya3M0Wp6V88J/s400/skype-cannot-connect-20150921-2.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
Skype Heartbeat Announcement</div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
The symptom in the Skype Windows client presents itself as:</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlzLgGBeRXMA9XmdN5Ka4iocemJR47L8lg74OtvcnLICeGYQlRkWhmmbtKVG8nlHF-ttDVQS5b391hS8bkSu4DXAdypbYz0LANBM0nab2X25RVkw_JV4XkTVwDlMgcRmnaE6sGUU3cBDu1/s1600/skype-cannot-connect-20150921.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="257" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlzLgGBeRXMA9XmdN5Ka4iocemJR47L8lg74OtvcnLICeGYQlRkWhmmbtKVG8nlHF-ttDVQS5b391hS8bkSu4DXAdypbYz0LANBM0nab2X25RVkw_JV4XkTVwDlMgcRmnaE6sGUU3cBDu1/s400/skype-cannot-connect-20150921.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
Skype Windows Connect Fail</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
Lastly, here's the information provided via Twitter:</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtrfmz03CxmH_TT5FK9rqHjbvslD190RMPgSSyXYNYH6MDJU5f67rix4Zm9kFOwUdcf5ygce1hfigm3cwzehG7BjWOtb29Apzy9NJrkeml9Dvg92LZMhrAVdjNi_pVfR4Gq556-E1Qx13l/s1600/skype-cannot-connect-twitter-status.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="238" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtrfmz03CxmH_TT5FK9rqHjbvslD190RMPgSSyXYNYH6MDJU5f67rix4Zm9kFOwUdcf5ygce1hfigm3cwzehG7BjWOtb29Apzy9NJrkeml9Dvg92LZMhrAVdjNi_pVfR4Gq556-E1Qx13l/s400/skype-cannot-connect-twitter-status.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com2tag:blogger.com,1999:blog-4373418720420879859.post-83825798901750861742015-07-14T18:02:00.002-04:002015-07-14T18:02:34.188-04:00Trust in 911 Information Provider Undermined by Expired Certificate<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBO4jFerHOhRRB4qjuSKdjcjWtxgQ74VndX_A5v0Ij-f1a04Qn0cX616tCHsQu8e3AmleBDMLrcEvI3ryq3afuEUEKIxBgbN23YL8xilIFpM_KSqaZX8yeG-hh6vldzKga-kvvqvyG245m/s1600/smart911-bad-cert-msg-20150713.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="379" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBO4jFerHOhRRB4qjuSKdjcjWtxgQ74VndX_A5v0Ij-f1a04Qn0cX616tCHsQu8e3AmleBDMLrcEvI3ryq3afuEUEKIxBgbN23YL8xilIFpM_KSqaZX8yeG-hh6vldzKga-kvvqvyG245m/s640/smart911-bad-cert-msg-20150713.png" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Smart911 SSL Credential Expired</td></tr>
</tbody></table>
<div style="text-align: justify;">
The local town of <a href="http://bit.ly/1V08O5i">North Hempstead NY has campaigned over the past year</a> to have its citizens register with a commercial service, Smart911. Smart911 connects additional personal information about households with local 911 services so that alternate means of communication, identification and other services can be enabled. During Superstorm Sandy, the need for a service like this was clearer -- even though some will choose to keep such information personal.</div>
<br />
<div style="text-align: justify;">
Unfortunately, using the service this week resulted in the standard expired SSL certificate warning -- which less browser-savvy users (as well as <a href="https://www.owasp.org/index.php/HTTP_Strict_Transport_Security">OWASP users</a>) will interpret as meaning the site is not safe. This is unfortunate given the sort of service involved, and the amount of personal information requested by the contractor. </div>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-49102025011249700052015-03-01T17:34:00.001-05:002015-03-01T17:34:28.039-05:00Technical Error, No ETA but Check Twitter<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhVJgAiKFjNH1ko05GO8WvliqAvKZAK4B_GyuOgMAGpqxnbGd4kdqfRlk_ttDoz8FCzWP5s1MJDcBJ5UKBWTF431-5KDAidKRzw0_i7Aj_MvjZ1PgQqICLU5gATaGuD07WG9VaMiYTbA_LI/s1600/socialoomph-outage-201503011723.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhVJgAiKFjNH1ko05GO8WvliqAvKZAK4B_GyuOgMAGpqxnbGd4kdqfRlk_ttDoz8FCzWP5s1MJDcBJ5UKBWTF431-5KDAidKRzw0_i7Aj_MvjZ1PgQqICLU5gATaGuD07WG9VaMiYTbA_LI/s1600/socialoomph-outage-201503011723.png" height="110" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Screenshot from SocialOomph</td></tr>
</tbody></table>
<div style="text-align: justify;">
A technical outage of some kind. ErrorProcessing says: (1) No ETA; (2) No suggested workarounds; (3) No links to help pages or status pages.
</div>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-75807139874743467962014-12-14T12:06:00.002-05:002014-12-14T12:06:20.727-05:00Looking Up a Zip Code? Not Online - At the MomentHere was the result when I tried to get a zip plus four zip code just now.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijln7lmYpFRayVTisFbJjw4nNIcF4ptb3MysQ6kOtN2Y29bc0cy1i_LViM6P7J2R2OuJkC1vc-KEGxZ8LSI876O7VO50gD00rD4SYYjdqq5C7cjZT6g4eRvrmAzaMs-_IWo01_Ku52_Nfn/s1600/usps-zip-finder-20141214.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijln7lmYpFRayVTisFbJjw4nNIcF4ptb3MysQ6kOtN2Y29bc0cy1i_LViM6P7J2R2OuJkC1vc-KEGxZ8LSI876O7VO50gD00rD4SYYjdqq5C7cjZT6g4eRvrmAzaMs-_IWo01_Ku52_Nfn/s1600/usps-zip-finder-20141214.jpg" height="287" width="400" /></a></div>
<br />
<br />
#softwareqcknowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-85426404994650511202014-08-24T10:43:00.000-04:002014-08-24T10:43:17.758-04:00Third Party / API Timeouts - Tweetchat ExampleCloud-to-cloud traffic is probably increasing, though it's unclear how to measure that directly. If so, the frequency of timeouts such as this one will probably increase. The error messages, as is the mantra here, should link to an FAQ or recommended action for users.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjy6Ni-4blruiRU3xcDpBTpoRlfS12nIUfK9mF-FGADdMtNAfbGoGCCcoAi9pSOtL23ZLW1gymt0vuSGz7gABj3h4iOhwFJuiXLvCgSAFLQA8juASl47jX2ZJZpBG2pyjS9Y7wMKYqOJXow/s1600/twitter-timeout-via-tweetchat-201408241038.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjy6Ni-4blruiRU3xcDpBTpoRlfS12nIUfK9mF-FGADdMtNAfbGoGCCcoAi9pSOtL23ZLW1gymt0vuSGz7gABj3h4iOhwFJuiXLvCgSAFLQA8juASl47jX2ZJZpBG2pyjS9Y7wMKYqOJXow/s1600/twitter-timeout-via-tweetchat-201408241038.jpg" height="70" width="400" /></a></div>
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-48848834432135073742014-06-24T21:24:00.000-04:002014-06-24T21:24:42.859-04:00The most recent screenshots for ErrorProcessing are usually posted to <a href="http://bit.ly/1v3I4RE">a Pinterest board</a> first.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4qEUdv8GaCHcxAKzaSLlSNlimJYYaQm4rpJyXAsI8Xe_nNS_umVSbswPpH-gYoSkrKUooowSq7VMKjXuTXntbPvRv0CFVgHfoqE7qCtKsaAtMnytxZJuwg9LjdSCC48fPn3mjzy_S837t/s1600/pinterest-errorprocessing-board-screenshot.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4qEUdv8GaCHcxAKzaSLlSNlimJYYaQm4rpJyXAsI8Xe_nNS_umVSbswPpH-gYoSkrKUooowSq7VMKjXuTXntbPvRv0CFVgHfoqE7qCtKsaAtMnytxZJuwg9LjdSCC48fPn3mjzy_S837t/s1600/pinterest-errorprocessing-board-screenshot.png" height="326" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Screenshot from ErrorProcessing Pinterest Board</td></tr>
</tbody></table>
<br />
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-3168705396372135502014-02-03T11:49:00.001-05:002014-02-03T11:49:13.429-05:00Obamacare computers not yet equipped to fix errors: report | Reuters<div style="text-align: justify;">Big Data involves four V's: Variety, Volume, Velocity and Veracity. Where Veracity is concerned, an emerging need is to provide data providers -- especially citizens -- with the means to correct errors in the data about themselves. Such portals are too often omitted when system requirements are developed. A Healthcare.gov deficiency noted by the <i>Washington Post</i> is a recent example.</div><br /><br />
<a href="http://www.reuters.com/article/2014/02/03/us-usa-healthcare-appeals-idUSBREA1203P20140203?feedType=RSS&feedName=domesticNews">Obamacare computers not yet equipped to fix errors: report | Reuters</a>: <br /><br />
<br /><br />
<a href="https://chrome.google.com/webstore/detail/pengoopmcjnbflcjbmoeodbmoflcgjlk" style="font-size: 13px;">'via Blog this'</a>knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-50226438260082323082013-12-03T12:17:00.000-05:002013-12-03T12:17:01.148-05:00Dropbox Dropped the BallToday's error message is from <a href="http://bit.ly/1bfkxTa" target="_blank">Dropbox</a>. The issue arose somewhere in the account setup or folder sharing process -- it is unclear where.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilo5SCIK35Yb1cVb2SKXViCdK09-lTGkHT1g8rUf_f-7gUFdNRJAEGhWUh3s3ZQlh07DKNn_csXM0xiTSIQ4a1bqKyaHSmH1yzItCEYcEG5xSajLVEfB30J_roIPR96GGl7TzAP6A71SqE/s1600/dropbox-error-201312031208-px633.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilo5SCIK35Yb1cVb2SKXViCdK09-lTGkHT1g8rUf_f-7gUFdNRJAEGhWUh3s3ZQlh07DKNn_csXM0xiTSIQ4a1bqKyaHSmH1yzItCEYcEG5xSajLVEfB30J_roIPR96GGl7TzAP6A71SqE/s1600/dropbox-error-201312031208-px633.jpg" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Error Message from Dropbox</td></tr>
</tbody></table>
<div style="text-align: justify;">
<b>Remarks: </b>The error message does not advise the user on what steps to take next, other than "Check our Help Center and forums." It is highly likely that more helpful information could have been disclosed.</div>
<div style="text-align: justify;">
<br /></div>
<blockquote class="tr_bq">
<b>Message Text: </b>Error: Something went wrong. Don't worry, your files are still safe and the Dropboxers have been notified. Check out our Help Center and forums for help, or head back to home.</blockquote>
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-75421273354083917802013-10-28T23:13:00.001-04:002013-10-28T23:13:40.560-04:00Pleasant Surprise: A Novel Error Handling Screen<br /><div font-size:="" normal="" style="text-align: justify;">
<span style="font-size: normal;">This fail screen from InsideAnalysis.com is noteworthy in a positive way. Unlike most of the screenshots at errorprocessing.com, here's one that makes an attempt to diagnose what happened. It is surprisingly effective because the standard of comparison is so low. Probably credit CloudFlare for this achievement.</span></div>
<div style="text-align: justify;">
<span style="font-size: normal;"><br /></span></div>
<div style="text-align: justify;">
<span style="font-size: normal;"><br /></span></div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh7MHBgsV5WDJ-OPV0sWmJHFSV3HMlx0a_HLSzmJslmJR0G1vbvdedJmAYkGidxyJkP2SxVFwsDc000HakUN494ARMpotpxT3pz4xMmD8mn7eb2NZR9t81daik00_vgIEYUmniF_rmrG3vx/s1600/insideanalysis-with-cloudflare-20131028-553px.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh7MHBgsV5WDJ-OPV0sWmJHFSV3HMlx0a_HLSzmJslmJR0G1vbvdedJmAYkGidxyJkP2SxVFwsDc000HakUN494ARMpotpxT3pz4xMmD8mn7eb2NZR9t81daik00_vgIEYUmniF_rmrG3vx/s1600/insideanalysis-with-cloudflare-20131028-553px.png" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">InsideAnalysis.com: A Surprising Error Processing Screen</td></tr>
</tbody></table>
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-39139763969024776892013-08-29T05:11:00.001-04:002013-08-29T05:20:37.305-04:00Google Drive Message for Mishandled File<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5emLvtJI8SIDjEWt74Pwk0hPrkVvFK06OWcEuXmsp4pHhq_uJRcChONZRTWjQ4atG7pJFI1nmBWTWTeNunTon2kjgoVoOVjZv481vOpGpJkpUo3pyhmT7jJhFkakf1WuTrVCUCxmft3vu/s1600/google-docs-file-inaccessible-201308281258-553px.JPG" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5emLvtJI8SIDjEWt74Pwk0hPrkVvFK06OWcEuXmsp4pHhq_uJRcChONZRTWjQ4atG7pJFI1nmBWTWTeNunTon2kjgoVoOVjZv481vOpGpJkpUo3pyhmT7jJhFkakf1WuTrVCUCxmft3vu/s1600/google-docs-file-inaccessible-201308281258-553px.JPG" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Google Drive Error During "Details" Editing</td></tr>
</tbody></table>
<br />
<br />
<div style="text-align: justify;">
This error was encountered during routine editing of the "details" on a Google Drive file. The reload resulted in a minor data loss.</div>
<br />
<h2>
Message text</h2>
"File unavailable. Sorry, there's a problem with this file. If this keeps happening, you can report this error. [Reload button]."<br />
<h2>
User Interaction at Time of Event</h2>
Editing a Google Docs document.<br />
<h2>
Recommendation</h2>
Reload<br />
<br />
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-84277215396297979362013-08-02T07:08:00.000-04:002013-08-02T07:08:13.790-04:00Unsubscribe: Why is it so hard?<div style="text-align: justify;">
At the foot of every email should be an unsubscribe link. Many messages have this feature. Surprisingly few have the option to change your email address. Worse, when you try to unsubscribe, you get the all-too-familiar "interrnal server error" instead.</div>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjroXyfgvlOQyMAcWwE9wZr3QfOgb4Fo1YoLSbsxgtiiLHpUp_-WJyF9h0V7m3Q6JeNSg5LrZyI4KzQbYnMIVMWvRQC_-9n0wKNS0kFIeP3LpwDy9fTnADe272pyQxhx4BdkGcZcFE3Malx/s1600/IDGA-unsubscribe-20130802.PNG" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjroXyfgvlOQyMAcWwE9wZr3QfOgb4Fo1YoLSbsxgtiiLHpUp_-WJyF9h0V7m3Q6JeNSg5LrZyI4KzQbYnMIVMWvRQC_-9n0wKNS0kFIeP3LpwDy9fTnADe272pyQxhx4BdkGcZcFE3Malx/s1600/IDGA-unsubscribe-20130802.PNG" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">IDGA Email Unsubscribe Attempt</td></tr>
</tbody></table>
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-39036113166721367922013-07-24T18:17:00.001-04:002013-07-24T18:17:47.922-04:00"No File" = USB Stick Failure<table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFxBvmhl8XzNiGHZyfbWFyjXttgjr6-NXhSiVSAZTratB5GvaCA9mCGDfLOaA1xMXlfkiqA-VUuXhmkE3ixEC8SV_E00gIorJ7F5UMYwaGY3pzlQAg_Nys8XKzfmzVFl6SQL2NXah1Hoco/s1600/alpine-no-file-error-201307241530.JPG" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFxBvmhl8XzNiGHZyfbWFyjXttgjr6-NXhSiVSAZTratB5GvaCA9mCGDfLOaA1xMXlfkiqA-VUuXhmkE3ixEC8SV_E00gIorJ7F5UMYwaGY3pzlQAg_Nys8XKzfmzVFl6SQL2NXah1Hoco/s1600/alpine-no-file-error-201307241530.JPG" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Alpine Auto Stereo Error Message</td></tr>
</tbody></table>
<div style="text-align: justify;">
Discussions periodically flare up about the lifetime of flash memory -- the sort of memory used in a flash drive. A 2010 <a href="http://zd.net/15gqNui">test by ZDNet</a> was optimistic. Claims made by manufacturers were generally exceeded, though some areas for concern were noted. </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
So it was with some surprise when -- in the middle of a song -- my Alpine CDE-102 car stereo stopped playing audio from a USB stick. The 16GB Sandisk SDC76016G was used almost exclusively as a write-once, play-many device. If my memory serves, there were only three distinct write sessions. In this scenario, the CDE-102 first threw an undocumented message that there was no USB attached. Then, when I removed the SDC76016G and reattached it, this message: "NO FILE."</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Testing of the USB stick on a Windows 7 desktop showed that the stick had failed, as Windows could not recognize it, either. Thus, a reformat would not possible.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
It's a small sample, but does give one pause about the long term reliability of USB Flash memory for backup purposes.</div>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-57983099351135266512011-09-13T17:58:00.000-04:002013-07-16T18:36:38.051-04:00JV16 Power Tools: "Please let us know"<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEguZV2sqgvfJsSZBhQm9ftMUbh87IdnF1eIQbCE0IdWYRXi_OdVXwXFeZ9R1tG9oKa7whuLYfgcqeDuEFs4NsLNGNMvxJY4J44LJTuX-0cnPQeBiNs1c5SVVDZ2bfIzQTz_IzIckav36Oik/s1600-h/jv16-powertools-error-capture-20090601.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5342480325217154114" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEguZV2sqgvfJsSZBhQm9ftMUbh87IdnF1eIQbCE0IdWYRXi_OdVXwXFeZ9R1tG9oKa7whuLYfgcqeDuEFs4NsLNGNMvxJY4J44LJTuX-0cnPQeBiNs1c5SVVDZ2bfIzQTz_IzIckav36Oik/s1600/jv16-powertools-error-capture-20090601.jpg" style="float: right; margin: 0px 0px 10px 10px;" /></a><br />
A release of the MaceCraft JV16 Power Tools application threw this error message:<br />
<blockquote class="tr_bq">
Something was about to go wrong and the internal safety mechanism SafetyNet stopped the program's execution. </blockquote>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-68965058910011650552011-05-05T20:18:00.000-04:002011-05-05T20:18:52.141-04:00"Sitting Tight" at LinkedIn<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiy8Tc0eWPfjCGNnqVmlCzjO-YTLRA9PtfXhwP2Fj_2bRY85qlUla3bnZh4amXdfc3yZ3oTaBeaRWtAX0Hy2j0YXgR_XfTLUOOYXYZGj8I5Qf5kZaquSoZH3iCt5E9z6R1Zo5zRYLR0ae-p/s1600/linkedin-sit-tight-msg-20110504.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="247" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiy8Tc0eWPfjCGNnqVmlCzjO-YTLRA9PtfXhwP2Fj_2bRY85qlUla3bnZh4amXdfc3yZ3oTaBeaRWtAX0Hy2j0YXgR_XfTLUOOYXYZGj8I5Qf5kZaquSoZH3iCt5E9z6R1Zo5zRYLR0ae-p/s400/linkedin-sit-tight-msg-20110504.png" width="400" /></a></div><div style="text-align: justify;">In the course of some routine site browsing at LinkedIn.com yesterday, the error shown above was thrown. It's polite, aesthetically acceptable (if not pleasing) -- even hopeful, but the message implies that one should take no action. Just "sit tight." </div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">I struggled to think of an error condition that had <i>visibly</i> recovered itself in a timely way with no interaction required from me. It's possible that some exist, though none came to mind, and my skepticism was rewarded by having this screen remain static for 90 minutes. An auto-refresh might have effected a change, but starting a new session seemed like a better plan. I did reproduce the situation on the same computer with a different browser (and obviously different session), and it too remained static after encountering the error.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Self-correcting errors -- even user-advised self-correcting errors -- are not unheard of, and this may have been one of them, but any correcting that took place was not visible to this visitor.</div>knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-6595732063374418332011-03-02T15:52:00.000-05:002011-03-02T15:53:22.944-05:00HTML5? Great. Now What About Webserver Error Handling?<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjd-fWdjCgUiuM9K7DaGxl3jj3OzMJZFjfVcEQCEAsJAO78STPggFw95rBGxgOx1ywhUkG6Hvkpar9VNXHLCQmKn5RDBsTTqWUmsygnxr5KdqCbEErgm0kU7x4fBS9TGlTQ2hZ7TRiXBMBq/s1600/irise-gateway-timeout-20110302.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><span class="Apple-style-span" style="font-family: Georgia, 'Times New Roman', serif;"><img border="0" height="116" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjd-fWdjCgUiuM9K7DaGxl3jj3OzMJZFjfVcEQCEAsJAO78STPggFw95rBGxgOx1ywhUkG6Hvkpar9VNXHLCQmKn5RDBsTTqWUmsygnxr5KdqCbEErgm0kU7x4fBS9TGlTQ2hZ7TRiXBMBq/s400/irise-gateway-timeout-20110302.png" width="400" /></span></a></div><div style="text-align: justify;"><span class="Apple-style-span" style="font-family: Georgia, 'Times New Roman', serif;">I just saw a <a href="http://bit.ly/dUoGHH">Google / Arcade Fire video</a> that has been widely viewed (fun stuff!), but this blog post isn't about the video. Rather I was thinking about the apparent status quo with messages and error notification in use for webservers (yes, even vaunted Apache). Sure, there's an API so web developers can intercept the message and put up something more elegant, but the default error processing approaches the unusable. Further, it's often the case that the developer has little control over the cause of such errors. All the more reason for the web server to offer up something sensible. Given the ubiquity of Wikipedia, maybe the user should be directed <a href="http://bit.ly/huWJpA">there</a>, where natural language content curation is held in higher regard than in developer communities. </span></div>knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-36093558521961325512010-07-01T18:43:00.000-04:002013-07-16T18:45:25.610-04:00"Ouch!" ???<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTfdnQ8vdCcKeQtCBsXqpRTc3p6j3Z9fvPGBD_gSFPb7fP2GWipS3PYepoz0C8jqSm1pLLJjVs-MhVXmzQKpwk1VamScYBjZUn1fyP_fjkMek7JPh8s-jSregWFZv0hpge7KEt47APl5dA/s1600-h/yahoo-mail-ouch-20090512.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" style="margin-left: auto; margin-right: auto;"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5335387051594369746" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTfdnQ8vdCcKeQtCBsXqpRTc3p6j3Z9fvPGBD_gSFPb7fP2GWipS3PYepoz0C8jqSm1pLLJjVs-MhVXmzQKpwk1VamScYBjZUn1fyP_fjkMek7JPh8s-jSregWFZv0hpge7KEt47APl5dA/s320/yahoo-mail-ouch-20090512.jpg" style="float: right; height: 134px; margin: 0pt 0pt 10px 10px; width: 320px;" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Yahoo Error Humor</td></tr>
</tbody></table>
<div style="text-align: justify;">
Sometimes levity is appropriate, but for a message that could be potentially thrown many times to the same user, the humor should be tempered with caution. This Yahoo error message started with "Ouch!" and then "The error, LaunchFFC-1, occurred when trying to connect to Yahoo! Mail." This tone leaves the user with the impression that the situation is not being taken seriously.</div>
<br />knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-70125396335061927842010-03-14T12:01:00.001-04:002013-07-16T17:53:10.041-04:00Assessing Error Message Effectiveness<div class="posterous_autopost">
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNVOo4w1uCQLm3J9_oj4Slz9jKWDhiKxNYLptQ6my_7QZPVtITs4AQLDn5UgwqYofyyf0qJzaWq7JFxrsUg7SrXun2pA99w7TXzO-senJHAKtk5GEUVbS3EuLm5XZ2Zb5erHVLZaRvF1T3/s1600/microsoft-general-feedback-subform-20130715.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgNVOo4w1uCQLm3J9_oj4Slz9jKWDhiKxNYLptQ6my_7QZPVtITs4AQLDn5UgwqYofyyf0qJzaWq7JFxrsUg7SrXun2pA99w7TXzO-senJHAKtk5GEUVbS3EuLm5XZ2Zb5erHVLZaRvF1T3/s1600/microsoft-general-feedback-subform-20130715.png" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Microsoft.com Feedback Form for Fix-It</td></tr>
</tbody></table>
<br />
<div style="text-align: justify;">
A weak underlying model for detecting and reporting errors is often revealed through casually thrown (or thrown off) error messages. One post hoc way to address this deficiency -- though it may not improve the model's weaknesses -- is to request feedback from message recipients. Microsoft Office users are <br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcTdcA7fAtqYehxg-PnPR6M6igklubHRtbIg8QJbE8q6HYKvIw5zAe-esTv30q0svCEm6G6vu7ztoTAsnbc3Cuk5meuG4u0RQMqatyurfteEcokOmnyXKCMsmS7OvbVqb-pfxnEhzNsQTE/s1600/microsoft-fixit_logo.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="104" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcTdcA7fAtqYehxg-PnPR6M6igklubHRtbIg8QJbE8q6HYKvIw5zAe-esTv30q0svCEm6G6vu7ztoTAsnbc3Cuk5meuG4u0RQMqatyurfteEcokOmnyXKCMsmS7OvbVqb-pfxnEhzNsQTE/s200/microsoft-fixit_logo.png" width="200" /></a></div>
sometimes requested to indicate whether a particular message is effective. Not all Microsoft messages offer this feature. How does Microsoft determine which messages deserve this treatment? What internal workflow accompanies the feedback received? If changes are made to the message, how are the proposed changes evaluated prior to release? Will they be improvements or simply add to the confusion?</div>
</div>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-92041326886526844162010-03-13T10:23:00.001-05:002010-03-13T10:23:13.356-05:00The Challenge of "Model Level" Software Errors
<div class='posterous_autopost'>Most of the screenshots collected in errorprocessing.com involve obvious errors. Messages that are painfully obvious are thrown onto the screen, or traceback messages of use only to developers replace "normal" screens. There are other sorts of errors. Some errors are more abstract, or, stated in MVC / DSL language, occur at a higher level in the software model. In this case, a screenshot may not reveal the error. <p /> A recent example occurred when activating a replacement phone with Sprint. The Sprint web content that solicited the phone identification strings directed users to phone-specific instructions on programming the phone to reflect the new phone activation steps. I clicked into the phone-specific page, but instead of the new phone's instructions, the web content showed the old phone instructions. After 15 minutes of browsing the Sprint site failed to find FAQs for the new phone, I resorted to Google, which returned the specific URL needed: <a href="http://support.sprint.com/support/device/HTC/HTC_Touch_PRO-PPC6850SP. ">http://support.sprint.com/support/device/HTC/HTC_Touch_PRO-PPC6850SP. </a> Result? No screenshot, but an error nonetheless. <p /> Considering how software test applications must be developed to detect failures of this sort, it is perhaps clearer why knowledge engineering is an integral part of developing model semantics as an integral part of software engineering. <p style="font-size: 10px;"> <a href="http://posterous.com">Posted via email</a> from <a href="http://knowlengr.posterous.com/the-challenge-of-model-level-software-errors">knowlengr </a> </p> </div> knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-47066396584353623672009-05-12T12:39:00.000-04:002009-05-12T12:41:14.418-04:00Error Processing Via Cartoon / Clip Art<div style="text-align: justify;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_eKmZml9fwkQ/SgmmXVX1VzI/AAAAAAAAAZU/Jy7v4ew4oLw/s1600-h/bit-ly-interrupt-show-20090511.jpg"><img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 233px; height: 201px;" src="http://2.bp.blogspot.com/_eKmZml9fwkQ/SgmmXVX1VzI/AAAAAAAAAZU/Jy7v4ew4oLw/s320/bit-ly-interrupt-show-20090511.jpg" alt="" id="BLOGGER_PHOTO_ID_5334978153401374514" border="0" /></a>Some might argue that if an application is going to fail, it should do so with a human touch. Perhaps, but helpfulness is to be preferred over humor. In this warning message from URL-shortener and URL-tracking utility <a href="http://bit.ly/">bit.ly</a>, the cartoon approach is given top billing.</div>knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.comtag:blogger.com,1999:blog-4373418720420879859.post-27360289945864511562009-05-07T11:16:00.000-04:002013-07-16T18:50:13.433-04:00"Forbidden!" - It's not a game, Mildred<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXvJwjIpBQQ52O02OpB96O9DoFucVMwfnxglLk8bj0Z8Q0Gv87PzFciKQ0EJbjqdgD7S_QPrx79sJAjfzOI3LJtKLQnfOso2l2kU1eZvworKUI22ulPf01p2YrZN81JqOZZYhIi706_Dga/s1600-h/google-bad-url-webserver-msg-20090507.png" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5333101713073620978" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXvJwjIpBQQ52O02OpB96O9DoFucVMwfnxglLk8bj0Z8Q0Gv87PzFciKQ0EJbjqdgD7S_QPrx79sJAjfzOI3LJtKLQnfOso2l2kU1eZvworKUI22ulPf01p2YrZN81JqOZZYhIi706_Dga/s200/google-bad-url-webserver-msg-20090507.png" style="float: right; margin: 0pt 0pt 10px 10px;" /></a><br />
<div style="text-align: justify;">
Give Google Sites a poorly formed URL and receive this message from the webserver. Error 403 is commonplace, routine in web dev circles, but isn't so common that users recognize its cause and realize that it's essentially innocuous. The "forbidden" message has a misleading tone.</div>
knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-26276911151975442142009-05-04T22:20:00.000-04:002009-10-04T00:34:58.437-04:00"System Unavailable" - But Not Really<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXmXVBNrym-X4DlFVgReKevDvq3oLrU0t0VGh6FCDxCqj2_ibj76JLLuQr1au9fIw3m4kXww-xVQSX02Z9CkS_iTteJdWDzszHxkypCm3FB6TABcXxG0YRcaskBZxIAZDjY__QeAep48vA/s1600-h/schwab-moneylink-1st-transaction-20090322.jpg"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5332160191516018290" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXmXVBNrym-X4DlFVgReKevDvq3oLrU0t0VGh6FCDxCqj2_ibj76JLLuQr1au9fIw3m4kXww-xVQSX02Z9CkS_iTteJdWDzszHxkypCm3FB6TABcXxG0YRcaskBZxIAZDjY__QeAep48vA/s320/schwab-moneylink-1st-transaction-20090322.jpg" style="display: block; height: 136px; margin: 0px auto 10px; text-align: center; width: 320px;" /></a><br />
<div style="text-align: justify;">This glitch (22 March 2009) with a recently updated Schwab website appeared to be caused by a difference in how workflow was conducted to authorize ACH transfers between a Schwab account and non-Schwab accounts. The CSR was able to straighten it out by changing the order in which screens were traversed. It most certainly was not because the system had become suddenly "unavailable."<br />
</div><br />
<div></div>knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0tag:blogger.com,1999:blog-4373418720420879859.post-20903277364045887392009-05-04T22:05:00.000-04:002009-10-04T00:35:31.859-04:00Something Technical This Way Comes<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5mnpG36rHDOEEdgBi7qk1PdE2WIO7W2KDVGBl2W5f-882jFagoyHR6-F_OI5vvQBRX9g3nBS8ub0Pee0k5mp6G6x0zeQjtyiHCOLt8GxYD8vnore720C017839J8VYNXXkmLGEcZOQd-j/s1600-h/twitter-something-wrong-20090310.jpg"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5332155698809711250" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg5mnpG36rHDOEEdgBi7qk1PdE2WIO7W2KDVGBl2W5f-882jFagoyHR6-F_OI5vvQBRX9g3nBS8ub0Pee0k5mp6G6x0zeQjtyiHCOLt8GxYD8vnore720C017839J8VYNXXkmLGEcZOQd-j/s320/twitter-something-wrong-20090310.jpg" style="display: block; height: 132px; margin: 0px auto 10px; text-align: center; width: 320px;" /></a><br />
<div style="text-align: justify;">Twitter (10 March 2009) recognizes a problem, but doesn't recommend anything. Did the last status message get sent? Perhaps Twitter doesn't know? Should I resend?<br />
</div><br />
<div></div><br />
<div></div>knowlengrhttp://www.blogger.com/profile/01857586646777639084noreply@blogger.com0