<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DUYCRns7fCp7ImA9WhBaGU4.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930</id><updated>2013-05-30T11:06:07.504-07:00</updated><category term="Fail" /><category term="Business Services" /><category term="domains" /><category term="Web-Applications" /><category term="Microsoft" /><category term="tools" /><category term="Internet" /><category term="javascript" /><category term="entrepreneur" /><category term="Drivers" /><category term="Email" /><category term="custos" /><category term="Phone Solicitation" /><category term="Remote Support" /><category term="government" /><category term="privacy" /><category term="Engineering" /><category term="Windows" /><category term="Security" /><category term="APIs" /><category term="chrome" /><category term="start-up" /><category term="Amazon Web Services" /><category term="Gentoo" /><category term="PHP" /><category term="hellarad" /><category term="VoIP" /><category term="iPhone" /><category term="PostgreSQL" /><category term="SEO" /><category term="twilio" /><category term="Linux" /><category term="Fraud" /><category term="Mac" /><category term="samba" /><category term="performance" /><category term="sem" /><category term="code" /><category term="Android" /><category term="Google Apps" /><category term="google" /><category term="money" /><category term="e-commerce" /><title>Edoceo's Blog</title><subtitle type="html">Business Technology related Commentary, Open Source in the Small Business, Entrepreneur Experience</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.edoceo.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.edoceo.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>109</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/EdoceosBlog" /><feedburner:info uri="edoceosblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;DUYNQXo8eSp7ImA9WhBbFU0.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-8155451444532485539</id><published>2013-05-13T21:53:00.000-07:00</published><updated>2013-05-13T21:53:10.471-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-13T21:53:10.471-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="start-up" /><category scheme="http://www.blogger.com/atom/ns#" term="domains" /><category scheme="http://www.blogger.com/atom/ns#" term="Internet" /><title>Sites Don't Respect Trademarks of Small Businesses</title><content type="html">&lt;p&gt;
Recently we've been in a battle with some of the webs busier sites regarding our registered trademark.
&lt;/p&gt;

&lt;p&gt;
See, many sites let the username represent the owner of the account like twitter.com/edoceo.
Many sites (Tumblr, Wordpress/Gravatar, Twitter and others) make no efforts what-so-ever to ensure that these usernames are not crossing trademarks.
&lt;/p&gt;

&lt;p&gt;
According to their policies you could register &amp;quot;Microsoft&amp;quot; and these sites would not mind (but we know that's not true).  However, when it comes to small businesses like mine these sites don't care at all.  They are full of lame excuses.  It super easy check trademark with an API query (http://edoceo.io/trademark)
&lt;/p&gt;

&lt;p&gt;
On some sites we've identified orphaned accounts, that clearly have no usage and formally requested access.
We're told things like: it cannot be changed, or there are &amp;quot;data integrity&amp;quot; issues.  Bullshit.
We know for a fact that at least one of these offending sites is backed by MySQL - &lt;code&gt;UPDATE&lt;/code&gt; is a pretty easy statement.
&lt;/p&gt;

&lt;p&gt;
Other bigger carriers such as YouTube and Instagram do respect the trademark.  Simply send them a nice letter, using the provided forms and wait a few days.  Done and done.
&lt;/p&gt;

&lt;p&gt;For now, we're looking for legal council in SF to help us out.&lt;/p&gt;

&lt;p&gt;Also, we've made a tool called &lt;a href="http://usernameshop.com/"&gt;Username Shop&lt;/a&gt; which helps to research as well as buy &amp;amp; sell these usernames aftermarket.  At least, until these sites start respecting trademarks.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/8qnMfZehNgg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/8155451444532485539/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=8155451444532485539&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8155451444532485539?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8155451444532485539?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/8qnMfZehNgg/sites-dont-respect-trademarks-of-small.html" title="Sites Don't Respect Trademarks of Small Businesses" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/05/sites-dont-respect-trademarks-of-small.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04DRXs7fSp7ImA9WhBbFU0.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-1308622753087787636</id><published>2013-04-26T22:38:00.000-07:00</published><updated>2013-05-13T22:39:34.505-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-13T22:39:34.505-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="Internet" /><title>Linode Outage Review - Counting Events</title><content type="html">&lt;p&gt;
Yesterday one of out hosting providers had a &lt;a href="http://status.linode.com/2013/04/fremont-connectivity-issues.html"&gt;network hiccup&lt;/a&gt;.
We use a number of providers and something happens somewhere at least once a week.
Network blips are something one simply has to build around, redundancy &amp;amp; failover and all that.
&lt;/p&gt;

&lt;p&gt;
Linode manages their issues well with frequent updates to their &lt;a href="http://status.linode.com"&gt;status page&lt;/a&gt;.
Employees participate in their IRC channel as well and are very responsive.
&lt;/p&gt;

&lt;p&gt;
It was however speculated that the Fremont data-centre has more outages than others.
&lt;/p&gt;

&lt;table style="width:99%;"&gt;
&lt;tr&gt;&lt;th&gt;Location&lt;/th&gt;&lt;th&gt;2010&lt;/th&gt;&lt;th&gt;2011&lt;/th&gt;&lt;th&gt;2012&lt;/th&gt;&lt;th&gt;2013&lt;/th&gt;&lt;th&gt;Sum&lt;/th&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Atlanta&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;16&lt;/td&gt;&lt;td&gt;20&lt;/td&gt;&lt;td&gt;14&lt;/td&gt;&lt;td&gt;58&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Dallas&lt;/td&gt;&lt;td&gt;22&lt;/td&gt;&lt;td&gt;12&lt;/td&gt;&lt;td&gt;30&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;68&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Fremont&lt;/td&gt;&lt;td&gt;20&lt;/td&gt;&lt;td&gt;16&lt;/td&gt;&lt;td&gt;22&lt;/td&gt;&lt;td&gt;12&lt;/td&gt;&lt;td&gt;70&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;London&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;18&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;32&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Newark&lt;/td&gt;&lt;td&gt;16&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;22&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;48&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td&gt;Tokyo&lt;/td&gt;&lt;td&gt;0&lt;/td&gt;&lt;td&gt;0&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/PlkNnW3Hi6w" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/1308622753087787636/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=1308622753087787636&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1308622753087787636?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1308622753087787636?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/PlkNnW3Hi6w/linode-outage-review-counting-events.html" title="Linode Outage Review - Counting Events" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/05/linode-outage-review-counting-events.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0MCQX8_eSp7ImA9WhBQGUQ.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-1403406278212828263</id><published>2013-03-22T16:35:00.000-07:00</published><updated>2013-03-22T16:37:40.141-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-22T16:37:40.141-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Fraud" /><category scheme="http://www.blogger.com/atom/ns#" term="government" /><title>Seattle PD Discrimination: Parking</title><content type="html">&lt;p&gt;
I had this theory for a while that SPD parking enforcement targets vehicles operated by &amp;quot;poor&amp;quot; people.
I heard and saw anecdotal evidence - my beat-up Jetta gets a ticket for a time-violation, while the BMW behind me does not.
&lt;/p&gt;

&lt;p&gt;
So, today we have an actual experiment going on.
My beat-up Jetta, a nice BMW and a clean Dodge Doakota have all parked, on the same block in the same 2h limit zone.
&lt;/p&gt;

&lt;p&gt;
The parking time limit is enforced from 8am to 6pm.
The BMW arrived around 8:30, my Jetta at 9:00 and the Dodge at 9:10.
As yet, we've not see the parking attendants.
&lt;/p&gt;

&lt;h3&gt;09:50 No Sign of Parking Enforcement (PE)&lt;/h3&gt;

&lt;h3&gt;11:14 Parking Enforcement Spotted&lt;/h3&gt;
&lt;p&gt;
Parking enforcement just passed our three sample cars, slowly.
I'm sure that each was recognised by their system, they have marked the tires of our sample cars with white chalk.
&lt;/p&gt;

&lt;h3&gt;11:32 Dodge Leaves&lt;/h3&gt;
&lt;p&gt;
The Dodge has left, so now our sample cars are down to two.
I'm not wanting to get a ticket on the Jetta, so I'm going to move it now.
However, I still assume that by EOD the BMW will still not have a ticket.
&lt;/p&gt;

&lt;h3&gt;12:03 Parking Enforcement Spotted&lt;/h3&gt;
&lt;p&gt;
PE makes another pass, this time using orange chalk markings.
An observation of the BMW has no marking, in either white or orange chalk.
Cars that were chalked include: Toyota, Honda and an F150 - all on the same block &amp;amp; same zone as the BMW.
&lt;/p&gt;

&lt;h3&gt;13:53 Parking Enforcement - Marking&lt;/h3&gt;
&lt;p&gt;
Didn't see them pass however, I did just look at the cars.
Now a new Toyota and a Nissan have been marked with white chalk, the BMW however still has no chalk markings.
&lt;/p&gt;

&lt;h3&gt;16:00 Parking Enforcement Spotted&lt;/h3&gt;
&lt;p&gt;
I just watched the Parking Enforcement dude (same guy I've seen three times today) drive past.
Chalking tires, guess what - the BMW - which has been parked since about 8:30 in a two (2) hour zone - still has not been chalked or ticketed.
&lt;/p&gt;

&lt;h3&gt;16:29 BMW Leaves&lt;/h3&gt;
&lt;p&gt;
The BMW just left, roughly eight (8) hours in a two (2) hour limited zone.
Tires were never chalked, though the tires of surrounding vehicles was.
Not citation was issued, although I saw other citations being given out.
&lt;/p&gt;

&lt;h2&gt;Summary&lt;/h2&gt;
&lt;p&gt;
I've managed to convince myself, after today's diligent observation that SPD Parking Enforcement is not applying the rules the same to all illegally parked vehicles.  My theory that the &amp;quot;nice car&amp;quot; would not get a parking citation, while other cars would be targeted played out as I described.  Accommodation for the Affluent.
&lt;/p&gt;
&lt;p&gt;
What I'd like to get my hands on now is the data about the citations, make, model, age as well as the zip code of the citation and zip code of the license holder.  From that we could build a pretty good model.
&lt;/p&gt;
&lt;p&gt;
I'm betting that the City and the State don't want that type of transparency.
&lt;/p&gt;
&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/QtY6yXI-s94" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/1403406278212828263/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=1403406278212828263&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1403406278212828263?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1403406278212828263?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/QtY6yXI-s94/seattle-pd-discrimination-parking.html" title="Seattle PD Discrimination: Parking" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/03/seattle-pd-discrimination-parking.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQCQ349eyp7ImA9WhBQGUo.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-7928897384809158056</id><published>2013-03-22T10:12:00.000-07:00</published><updated>2013-03-22T10:12:42.063-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-22T10:12:42.063-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="entrepreneur" /><category scheme="http://www.blogger.com/atom/ns#" term="start-up" /><title>Entrepreneurship &amp; Letting go of Ideas</title><content type="html">&lt;p&gt;
In Oct 2010 I had this concept of an IT related skills quiz, community constructed and community graded.
Conversations with others in the field led me to register a domain (ibise.org) and create a prototype of the system.
The grand scheme was to create some type of community regulated certification system.
&lt;/p&gt;

&lt;p&gt;
Progress was(is?) slow.
By 2012: I'd told a few people; created code to handle various question types (pick one, pick many, fill-in and essay) and created a few questions.
The breadth of skills represented was small.
The name had changed to Opus, and now &lt;a href="http://ars.io/"&gt;Ars&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
It's hard, very hard, to grow a project when it's not able to get more than 10% of your time.
I wanted this thing; however I had no time to grow it.
Nor did I feel like spending a few buck to have it populated with questions, polished and published.
&lt;/p&gt;

&lt;p&gt;
Over time the idea morphed around; what was the real issue I'm solving.
What did/does/are/were the problems which others in my field faced with regards to representing skill-set?
The name changed, more than once (Opus, then finally Ars I/O) which makes it hard to get a good bond with the project.
&lt;/p&gt; 

&lt;h2&gt;Time to Let it Go&lt;/h2&gt;
&lt;p&gt;
Recently I came across &lt;a href="http://www.smarterer.com/"&gt;Smarterer&lt;/a&gt; which provides for very similar quiz functionality (limited to pick-one style questions).
And the Ars project (as it's now called) had migrated away from the focus on the Skills quiz and become yet another on-line profile.
I think we have to let-go of the Quiz part and simply integrate with Smarterer.
&lt;/p&gt;

&lt;p&gt;
I had/have some &amp;quot;my baby&amp;quot; feelings about what I've built so far, so it's tough.
However...
&lt;/p&gt;

&lt;p&gt;
From the feedback the my associates gave me the site had morphed into a system that pulls your IT profile from a bunch of sites and makes a pretty display.
From fancy Quiz system to simple Resume Editor.
&lt;/p&gt;

&lt;p&gt;
So, yes, now &lt;a href="http://ars.io/"&gt;Ars&lt;/a&gt; integrates with Smarterer.
And, of course &lt;a href="http://stackexchange.com/"&gt;Stack Exchange&lt;/a&gt; is getting into the Resume business with their &lt;a href="http://careers.stackoverflow.com/"&gt;Careers 2.0&lt;/a&gt; option, which is suprisingly like Ars.
&lt;/p&gt;

&lt;p&gt;
I'll either have to give more time to Ars to compete with Stack Exchange, or I'll have to let this thing it's morphed into go too.
&lt;/p&gt;

&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/WcyQ3Graqao" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/7928897384809158056/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=7928897384809158056&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7928897384809158056?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7928897384809158056?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/WcyQ3Graqao/entrepreneurship-letting-go-of-ideas.html" title="Entrepreneurship &amp; Letting go of Ideas" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/03/entrepreneurship-letting-go-of-ideas.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcARXg-fCp7ImA9WhBSFUU.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-4497235488228039451</id><published>2013-02-22T18:20:00.001-08:00</published><updated>2013-02-22T18:20:44.654-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-22T18:20:44.654-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="entrepreneur" /><category scheme="http://www.blogger.com/atom/ns#" term="domains" /><category scheme="http://www.blogger.com/atom/ns#" term="Internet" /><title>Backorder Domain Auctions - False Metrics, Lost Revenue</title><content type="html">&lt;p class="lead"&gt;
Domain brokers and re-sellsers are inflating their metrics with false numbers.
&lt;/p&gt;

&lt;h2&gt;The Back Story&lt;/h2&gt;
&lt;p&gt;
Edoceo has been tasked with acquiring a domain name on behalf of a client. We'll call it &amp;quot;V.com&amp;quot;
&lt;/p&gt;
&lt;p&gt;
We review the WHOIS to attempt a direct transaction.
This is blocked by the GoDaddy Domains by Proxy addresses.
No matter, simply make a purchase attempt via GoDaddy to use their auction system.
We began that process and submitted our bid.
&lt;/p&gt; 

&lt;h2&gt;The False Metrics&lt;/h2&gt;
&lt;p&gt;
When we first viewed the domain auction with GoDaddy the metrics were zero (0) direct visits and zero (0) auction views.
We attempted bid placement however, since we had to login in we were redirected back - now the view count was two (2).
Our bid was entered and prompted to visit the shopping cart - for a domain with a bid view count of four (4).
Returning back to the domain review page the view count now shows six (6)!
We completed the bid process with a view count of seven (7) showing; still zero direct visitors.
&lt;/p&gt;

&lt;h2&gt;Lost Revenue&lt;/h2&gt;
&lt;p&gt;
The domain auction had a few (20+) days to close.
Of course, we kept checking on it too.
By the time it close the view count for the auction was over 20 - that was 99% us.
&lt;/p&gt;
&lt;p&gt;
The down side is that the seller viewed this as an increased interest in their domain.
And while we were interested and bid accordingly ($600) this decade old, unused domain remains unsold.
&lt;/p&gt;
&lt;p&gt;
It appears that the false counts delivered by GoDaddy &amp;amp; Sedo provide a soft-basis for inflated value for the domain holders.
Rather than pocket $500, this domain owner will likely lose another $50 over the next five years waiting for another buyer.
And with new TLDs coming on-line, the demand for &lt;code&gt;.com&lt;/code&gt; is waning.
&lt;/p&gt;

&lt;p&gt;Whatever, domains are easy to find - $9.95 got us another very cool &lt;code&gt;.co&lt;/code&gt;.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/5AHvKUT-L6Y" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/4497235488228039451/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=4497235488228039451&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/4497235488228039451?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/4497235488228039451?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/5AHvKUT-L6Y/backorder-domain-auctions-false-metrics.html" title="Backorder Domain Auctions - False Metrics, Lost Revenue" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/02/backorder-domain-auctions-false-metrics.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YFSX05eSp7ImA9WhBTF0Q.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-5721094795379191837</id><published>2013-02-13T14:38:00.001-08:00</published><updated>2013-02-13T14:38:38.321-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-13T14:38:38.321-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-commerce" /><category scheme="http://www.blogger.com/atom/ns#" term="start-up" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><title>Inheriting Sloppy Code</title><content type="html">&lt;p class="lead"&gt;Just started working with a new company, inherited sloppy code&lt;/p&gt;

&lt;h2&gt;Recognising Sloppy Code&lt;/h2&gt;
&lt;p&gt;
Developers know it when they see it; non-modular; repeated, disorganised directory structure, editing on production systems.
Business operators on the other hand don't, here's some tips.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Examine the Project&lt;/strong&gt; You don't know code, but if you see many duplicate names.
Or files like like &lt;code&gt;home.php, home-0.php, home-12july.php, home-bk.php, home.php~&lt;/code&gt; that is an indicator of slop.
More importantly it highlights that there is no code tracking tools in place.
&lt;/p&gt;
&lt;p&gt;
It's very important that the code team use tools like Subversion or Git or Mecurial or Bazaar.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Third Party Review&lt;/strong&gt; Get a second opinion.
Have an alternate, cash compensated dis-interested third party review the code.
The the report comes back an mentions duplicated code, lack of structure and other such then we have slop.
&lt;/p&gt;

&lt;p&gt;
If the code as been identified as sloppy, it can be an expensive process to resolve it.
It's important to enforce good development practices from the beginning.
&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Use a Source Control system (Subversion, Git, &amp;amp;c)&lt;/li&gt;
&lt;li&gt;Host Multiple Environments: Work, Test, Beta, Live&lt;/li&gt;
&lt;li&gt;Review Code with a trusted third party&lt;/li&gt;
&lt;li&gt;Test, Test, Test&lt;/li&gt;
&lt;li&gt;Control the Team - Don't let them stray or feature creep&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;Resolving Sloppy Code&lt;/h2&gt;
&lt;p&gt;
Quite a tough problem, clean what is there or throw it out entirely and start over?
Depends on the depth of the project.
Many times small fixes to the slop can keep the system operational and continue to generate revenue.
Rebuilding requires to redefine the specifications and basically re-build from the foundation up.
Maintenance time is lost to rebuild-time - or one could bring in a new team for the rebuild.
&lt;/p&gt;

&lt;p&gt;
Smaller teams are forced to try to re-work existing code to a more unified option, perhaps implementing one framework or another.
In some circumstances early projects have two conflicting methodologies in-place.
And the choice must be made to use one of those two, or fork to yet a third option.
&lt;/p&gt;

&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/yA3IJ7CqNAY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/5721094795379191837/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=5721094795379191837&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/5721094795379191837?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/5721094795379191837?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/yA3IJ7CqNAY/inheriting-sloppy-code.html" title="Inheriting Sloppy Code" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/02/inheriting-sloppy-code.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak4DQHgycCp7ImA9WhNUFUo.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-8063816372015652616</id><published>2013-01-07T09:16:00.000-08:00</published><updated>2013-01-07T09:16:11.698-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-01-07T09:16:11.698-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Security" /><category scheme="http://www.blogger.com/atom/ns#" term="Fail" /><category scheme="http://www.blogger.com/atom/ns#" term="chrome" /><title>Stealing Passwords with Google Chrome</title><content type="html">&lt;p&gt;
Here's a neat trick to steal your friends passwords using Google Chrome.
&lt;/p&gt;

&lt;h2&gt;Environment&lt;/h2&gt;
&lt;p&gt;
The target computer is using Google Chrome, which is currently not signed in to a Google Account.  This local Chrome profile has some saved passwords.
&lt;/p&gt;

&lt;h2&gt;The Attack&lt;/h2&gt;
&lt;p&gt;
Using that local Chrome profile sign-in to Chrome with your profile (eg: attacker@gmail.com).  Now, because you have Chrome sync enabled all the passwords from the local Chrome profile are now merged with the passwords you've saved in your roaming Chrome profile.  Theft complete!
&lt;/p&gt;

&lt;h2&gt;Discovery&lt;/h2&gt;
&lt;p&gt;
We had a computer at the office, a test bed system.  We'd have it save passwords for things during test.  We never purged the profile.  This is similar to what your Victims computer would have.
&lt;/p&gt;

&lt;p&gt;
Then for another test we actually did sign-in to Chrome, at which point the this remote profile had 100s of new usernames &amp;amp; passwords which were clearly from our test environment.
&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I don't know if it's evil but, it's really fucked up.&lt;/strong&gt;&lt;/p&gt;


&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/mUUwxXnvTEg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/8063816372015652616/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=8063816372015652616&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8063816372015652616?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8063816372015652616?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/mUUwxXnvTEg/stealing-passwords-with-google-chrome.html" title="Stealing Passwords with Google Chrome" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2013/01/stealing-passwords-with-google-chrome.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYMRH47eip7ImA9WhNbFks.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-7861292162274449073</id><published>2012-12-22T17:22:00.001-08:00</published><updated>2013-01-19T22:43:05.002-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-01-19T22:43:05.002-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Security" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Apps" /><category scheme="http://www.blogger.com/atom/ns#" term="privacy" /><title>Google Play Store Forces TOS Agreement</title><content type="html">&lt;p&gt;
If you have multiple accounts on one table or device using the Google Play Store forces users to accept the TOS or it will become completely blocked.
&lt;/p&gt;

&lt;p&gt;
We have one tablet, with multiple accounts configured and one accidental click has left the Play Store unusable, none of the apps can update.
&lt;/p&gt;

&lt;h2&gt;Steps to Reproduce&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Use an Android 4.0 or newer device&lt;li&gt;
&lt;li&gt;Add multiple accounts to the device, including one that has not agreed to Play Store yet.&lt;/li&gt;
&lt;li&gt;Open the Play Store, it will presently select an existing account.&lt;/li&gt;
&lt;li&gt;Select the New Account, you will be prompted to Accept&lt;/li&gt;
&lt;li&gt;Decline - Play Store Exits&lt;/li&gt;
&lt;li&gt;You are now Stuck - Google is forcing you to Accept due to this bug&lt;/li&gt;
&lt;/ol&gt; 


&lt;p&gt;
The reason that one account should not accept the TOS for the Play Store is that those applications are not &amp;quot;Kid Safe&amp;quot;.
&lt;/p&gt;

&lt;p&gt;
The only option now is to remove the account from the device entirely and start over.  The average user wouldn't do that, they'd simply enter into this binding contract with Google - even if they didn't want too.
&lt;/p&gt;

 
&lt;p&gt;
Seems like there is nobody at Google working in QA, bugs like this - and the terrible password issues in Chrome - keep appearing in their products.
&lt;/p&gt; &lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/zPxzZU25LCo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/7861292162274449073/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=7861292162274449073&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7861292162274449073?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7861292162274449073?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/zPxzZU25LCo/google-play-store-forces-tos-agreement.html" title="Google Play Store Forces TOS Agreement" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/12/google-play-store-forces-tos-agreement.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0AAQHs8fip7ImA9WhNXEkw.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-7614383853995808552</id><published>2012-11-29T12:09:00.000-08:00</published><updated>2012-11-29T12:09:01.576-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-11-29T12:09:01.576-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="APIs" /><category scheme="http://www.blogger.com/atom/ns#" term="Security" /><title>API Performance and Availability Monitoring</title><content type="html">&lt;p&gt;
For quite some time we've been building out &lt;a href="http://custos.co/"&gt;Custos&lt;/a&gt; - a network service monitoring tool.
&lt;/p&gt;

&lt;p&gt;
Recently, while working with a few teams to develop external APIs the discussion came around to monitoring API availability and performance.
&lt;/p&gt;

&lt;p&gt;
This was exciting for us! One of the claims we make about Custos is that creating custom monitors is super easy.  It follows that a service monitor for almost any API can be created with Custos.
&lt;/p&gt;

&lt;p&gt;
In only a few short minutes we were able to construct a PHP based monitoring script that was able to run a proper HTTP-API request, collect metrics (size, speed) and send the reports to Custos.  Super easy!
&lt;/p&gt;

&lt;pre&gt;

$ch = curl_init('http://server/api/listTarget');
curl_setopt($ch, CURLOPT_RETURNTRANSFER,true);
$body = curl_exec($ch);
$info = curl_info($ch);

$ttfb = $info['starttransfer_time'] * 1000;
$ttlb = $info['total_time'] * 1000;
$size = $info['size_download'];

echo "status Good\n";
echo "detail Testing the List Target API\n";
echo "metric ttfb=$ttfb\n";
echo "metric ttlb=$ttlb\n";
echo "metric size=$size\n";

&lt;/pre&gt;

&lt;p&gt;
How cool was that?
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/gZ3ab7pG010" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/7614383853995808552/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=7614383853995808552&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7614383853995808552?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7614383853995808552?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/gZ3ab7pG010/api-performance-and-availability.html" title="API Performance and Availability Monitoring" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/11/api-performance-and-availability.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcARHszeip7ImA9WhJbFk8.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-7069125649807922746</id><published>2012-09-25T17:40:00.000-07:00</published><updated>2012-09-25T17:40:45.582-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-09-25T17:40:45.582-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="tools" /><category scheme="http://www.blogger.com/atom/ns#" term="sem" /><category scheme="http://www.blogger.com/atom/ns#" term="google" /><title>What is SEM (Search Engine Marketing)</title><content type="html">&lt;p&gt;
We've had a recent up-tick it seems in clients wanting to know how to make their web-site more visible to search engines and, more importantly, people.  This used to be called &lt;em&gt;SEO&lt;/em&gt; but, seems the new phrase is &lt;em&gt;SEM&lt;/em&gt;.
&lt;/p&gt;

&lt;p&gt;The bottom line is this: &lt;strong&gt;SEM is a marketing campaigns based on search&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;What SEM Is:&lt;/h2&gt;
&lt;p&gt;
The process of marketing your site and or services through search engines;  namely Bing and Google.  Make sure your site shows up properly for terms that people are searching for.  Make sure your using the right keywords.  Make sure you're getting links that are on target.
&lt;/p&gt;

&lt;p&gt;
There are dozens of options at your disposal.  The basics are:
&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Build a Quality Site with Quality Content&lt;/li&gt;
&lt;li&gt;Acquire Links to your site and pages&lt;/li&gt;
&lt;li&gt;Promote via Social Media&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;
Firstly building a quality site, that is having original well-formed content.  You'll want appropriate keywords, but don't over saturate.  And make sure the site you operate follows current &amp;quot;best practices&amp;quot; (use a tool like: &lt;a href="http://seosorcerer.com/" title="SEM Tools"&gt;SEO Sorcerer&lt;/a&gt;).
&lt;/p&gt;

&lt;p&gt;
Get some links. Ask your blogging friends or those who operate other sites to link to you.  Perhaps your web-designer or developer can link to you.  There are also tools to purchase links however, those are generally frowned upon by search engines.
&lt;/p&gt;

&lt;p&gt;
More Facebook Likes, Tweets, Plus-Ones and Pins and all that social stuff helps.  Perhaps run an advertisement on Facebook or try to introduce a new hashtag on Twitter (or use popular ones in your tweets).
&lt;/p&gt;

&lt;p&gt;
That's the basics of what SEM is.  The reality of the situation, like so many other things, is that SEM is a big, complicated realm.  It's generally a good idea to get a consultant or other subject matter expert involved to help you. SEM is much to complicated to be executed properly while trying to run your business.
&lt;/p&gt;
&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/IHaW1DyEZ30" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/7069125649807922746/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=7069125649807922746&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7069125649807922746?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7069125649807922746?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/IHaW1DyEZ30/what-is-sem-search-engine-marketing.html" title="What is SEM (Search Engine Marketing)" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/09/what-is-sem-search-engine-marketing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4NSHw9eip7ImA9WhJWGE8.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-1939429229132629667</id><published>2012-08-15T20:50:00.000-07:00</published><updated>2012-08-24T09:49:59.262-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-08-24T09:49:59.262-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-commerce" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon Web Services" /><title>AWS Billing is Broken</title><content type="html">&lt;p&gt;
We've been a user of AWS for quite some time, over five years.  We interact with AWS services (S3, EC2, mTurk) on at least a weekly basis.  Things had been going quite well.
&lt;/p&gt;

&lt;p&gt;
Today Amazon sent a notice about a problem with our account, apparetnly it's been going for some time.  We just got a notice about charges on the dates below.
&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;February 1, 2008 - February 29, 2008 for 69.60&lt;/li&gt;
&lt;li&gt;March 1, 2008 - March 31, 2008 for 74.51&lt;/li&gt;
&lt;li&gt;October 1, 2010 - October 31, 2010 for 64.44&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
That is quite some time ago (it's Aug 2012 when I write this).
&lt;/p&gt;

&lt;p&gt;
What is going on over at AWS that they lose track of money and then come around and ask for it four years later?  Why didn't it come up in my last 48 months of usage? And, who do I contact over there? All we get is an email loop while they threaten my account (was fours day till suspension!)
&lt;/p&gt;

&lt;h2&gt;UPDATE!&lt;/h2&gt;
&lt;p&gt;
Eventually we found Amazon provides &lt;strong&gt;telephone&lt;/strong&gt; based support for this issue.  The on-phone support staff was helpful &amp;amp; personable. We came to an agreeable resolution within 15 minutes! That makes a better customer experience than what is offered by many others (I'm looking at you Facebook, Google).
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/wKAP30R_clI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/1939429229132629667/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=1939429229132629667&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1939429229132629667?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1939429229132629667?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/wKAP30R_clI/aws-billing-is-broken.html" title="AWS Billing is Broken" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/08/aws-billing-is-broken.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcGSHg9eyp7ImA9WhJXGEU.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-234426863792426671</id><published>2012-08-13T10:38:00.000-07:00</published><updated>2012-08-13T10:47:09.663-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-08-13T10:47:09.663-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-commerce" /><category scheme="http://www.blogger.com/atom/ns#" term="google" /><category scheme="http://www.blogger.com/atom/ns#" term="Google Apps" /><title>Google Checkout/Wallet Migration Nightmare</title><content type="html">&lt;p&gt;
Some time ago Google began this forced migration process of regular Google Accounts into Google Apps accounts - for those that had overlap.  For these users data from multiple services had to be migrated or merged.  We wrote about it twice: &lt;a href="http://blog.edoceo.com/2011/05/google-apps-to-accounts-transition.html"&gt;accounts transition&lt;/a&gt; and &lt;a href="http://blog.edoceo.com/2011/06/google-apps-migration-blogger-accounts.html"&gt;blogger migration&lt;/a&gt;.  The migration for Checkout has been terrible!
&lt;/p&gt;

&lt;h2&gt;Checkout Migration Issues&lt;/h2&gt;
&lt;p&gt;
Even after months of being told that migration would soon be possible it still has not become so.  Our checkout data is now scattered across three accounts.  It's a terrible inconvenience to the business.  The resolution is drop the other two, of course but for us that is kind of an issue.
&lt;/p&gt;

&lt;p&gt;
Our merchant id and the codes used for integrating our infrastructure into Google Checkout/Seller/Wallet/Whatever-next was in production across multiple servers and multiple applications, some more tied into the management systems than others.  Basically, we have to ack/grep a bundle of code/configs for the two IDs that were created in the interim to try and solve the migration/transition issue - and re-test all of it.
&lt;/p&gt;

&lt;p&gt;
We had these three accounts, accountA, B and C; A was the original Google Account that became conflicted with a Google Apps Account (C); B is the interim account that was a temporary holding while migrating.  Each had to be bank verified while migrating and then cleaned-up. Checking code on multiple applications across multiple servers takes time - more than you want to spend and of course interrupts existing work-flow. 
&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Sign-In to AccountA
&lt;li&gt;Check Google Dashboard - false positives for subscribed services&lt;li&gt;
&lt;li&gt;Confirm Checkout Settings (9 pages - Preferences, Tax and Integration are important!)&lt;/li&gt;
&lt;li&gt;Archive Orders and Financial Data&lt;/li&gt;
&lt;li&gt;Search Apps/Servers, Replace IDs&lt;/li&gt;
&lt;li&gt;Test - Google lets the same account buy from themselves?&lt;/li&gt;
&lt;li&gt;Wait to Process to re-verify for Badge Status&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;Questions for Google&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Why did you force migration before all services could be migrated?&lt;/li&gt;
&lt;li&gt;Why has there been no progress on the Checkout/Seller/Wallet migration since?&lt;/li&gt;
&lt;li&gt;Do you know it's not cool to mess around wildly with financial systems that many businesses &lt;strong&gt;depend&lt;/strong&gt; on?
&lt;/li&gt;
&lt;li&gt;Why can't we simply re-assign the Owner role? It's stuck to the '@gtempaccount.com' still (even after creating the migration account like you directed)!
&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;Alternative Solution Path&lt;/h2&gt;
&lt;p&gt;
So, that was quite an inconvenience for us and a few of our clients as well - other payment processors haven't done anything that stupid to date (that I'm aware of).  Evaluating a few we've decided that &lt;a href="http://www.stripe.com/"&gt;stripe&lt;/a&gt; is the way forward.  Their system is elegant, secure and very easy to integrate.  Since they're dedicated to just one thing it's less likely they'll force you into a lot of work when they mis-manage an infrastructure &amp;quot;integration&amp;quot; project.
&lt;/p&gt; 


&lt;h4&gt;See Also&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://productforums.google.com/forum/#!category-topic/apps/new-infrastructure-for-google-apps-accounts/fYFry-rIP1A%5B1-25%5D"&gt;How Do I Transition Google Checkout Seller Services&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/X0W8R-Xklno" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/234426863792426671/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=234426863792426671&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/234426863792426671?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/234426863792426671?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/X0W8R-Xklno/google-checkoutwallet-migration.html" title="Google Checkout/Wallet Migration Nightmare" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/08/google-checkoutwallet-migration.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQFQHk9cCp7ImA9WhJWGE8.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-8213982090078079729</id><published>2012-07-27T14:06:00.001-07:00</published><updated>2012-08-24T09:55:11.768-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-08-24T09:55:11.768-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Linux" /><category scheme="http://www.blogger.com/atom/ns#" term="Windows" /><category scheme="http://www.blogger.com/atom/ns#" term="samba" /><title>Resara, Samba4, Windows7</title><content type="html">&lt;h2&gt;RIP Resara&lt;/h2&gt;
&lt;p&gt;
Dramatic news this week when &lt;a href="http://www.resara.com/"&gt;Resara&lt;/a&gt; announced their closing.  We're sad to see Resara go, competition is good for customers.  And to their existing customers: we're offering commercial support services for Resara.
&lt;/p&gt;

&lt;h2&gt;Samba4 Updates&lt;/h2&gt;
&lt;p&gt;
Speaking of Samba based small business servers, our Praxis system has expanded now to offer Samba4 as a "stable" environment - however it should be noted that Samba4 is still in a beta stage.
&lt;/p&gt;
&lt;p&gt;
We've updated our &lt;a href="http://praxis.edoceo.com/howto/samba4"&gt;Samba4 How To&lt;/a&gt;, and even provided updated &lt;a href="http://cdn.edoceo.com/portage/net-fs/samba/samba-4.0.0_beta6.ebuild"&gt;Samba4 ebuilds&lt;/a&gt; to the Gentoo community.
&lt;/p&gt;

&lt;h2&gt;Samba4 + Windows7&lt;/h2&gt;
&lt;p&gt;
Also, this week gave us the largest Samba4 installation we've executed working with Brian &lt;a href="http://carolinahelpdesk.com/"&gt;Carolina Help Desk&lt;/a&gt;.  It initially started with an attempt using Samba 3.6, cause we know it's stable - but Windows7 just would not play nice.
&lt;/p&gt;
&lt;p&gt;
Round and round we went in this environment; and decided to run a Samba4 trial.
It worked great! Better than 3.x for sure but there are still some lingering issues (non-browsable shares, homes-magic) but they are trivial to work around.
&lt;/p&gt;

&lt;p&gt;
A test run of Samba4 resolved all the Windows7 issues we were having and eliminated the nasty registry hacks and other stuff - see our &lt;a href="http://praxis.edoceo.com/howto/samba4"&gt;Samba4 Reference&lt;/a&gt;.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/kD7ASBYtET0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/8213982090078079729/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=8213982090078079729&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8213982090078079729?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8213982090078079729?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/kD7ASBYtET0/resara-samba4-windows7.html" title="Resara, Samba4, Windows7" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/07/resara-samba4-windows7.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYHQ3g8eyp7ImA9WhJWGE8.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-3244187034122564973</id><published>2012-07-24T17:44:00.002-07:00</published><updated>2012-08-24T09:52:12.673-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-08-24T09:52:12.673-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="entrepreneur" /><category scheme="http://www.blogger.com/atom/ns#" term="tools" /><title>10 Business Model Canvas Tools - Review</title><content type="html">&lt;p&gt;
The business model canvas gets mentioned a lot in lean/start-up circles.
Here's my quick review of 8 of them.
&lt;/p&gt;

&lt;p&gt;
The current best-list of business model canvas tools is located at &lt;a href="http://leanstartup.pbworks.com/w/page/47250326/BusinessModelCanvas"&gt;http://leanstartup.pbworks.com/w/page/47250326/BusinessModelCanvas&lt;/a&gt;.
&lt;/p&gt; 

&lt;h2&gt;&lt;a href="http://bmdesigner.com/"&gt;BM Designer&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
A free tool, embeddable on blog or web-page, highly interactive UI, good clues/info-tips on the various sections.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://bmfiddle.com/"&gt;BMFiddle&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
Also free and based directly from Osterwalder. This is a very attractive JS based UI, pretty colours, good prompts for the section data, excellent highlighting/diff viewer.  Markdown support.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://canvanizer.com/"&gt;canvanizer&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
Free, only requires email (but fakes accepted).  Multiple canvas templates (business model, lean, swot, customer journey) to choose from. A very awesome and unique canvas history replay tool.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://www.boardofinnovation.com/business-model-templates-tools/"&gt;Business Model Brainstorm Kit&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
This is an actual, tangible kit for purchase.  It comes with magnetic icon blocks that you can stick to surfaces and then draw on.  They also have links to some super awesome examples around companies you've heard of (Spotify, Groupon).
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://www.businessmodelgeneration.com/"&gt;The Business 
Model Canvas &amp;amp; Toolbox&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
The original, a big PDF to download to help you get started as well as an iPad application.  A web-application is in the works.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://businessmodelpress.com/"&gt;Business Model Press&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
This one is a WordPress plugin, if you're already on WP why not give this one a try? It's currently invite only beta.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://leancanvas.com/"&gt;Lean Canvas&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
This one provides a nice canvas UI, between $12 and $49/mo and a two person free plan.  The Lean Canvas based on the Osterwalder canvas.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="https://www.leanlaunchlab.com"&gt;Lean Launch Lab&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
Free for a single user, then plans between $9 and $99/mo.  Allows for multiple projects, multiple collaborators.  LLL also provides more tools than just a canvas.  There are some good tools for experiments and customer interviews for example as well as team communication tools.
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://plancruncher.com/"&gt;Plan Cruncher&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
Not so much a canvas but a quick plan/model builder; has some very plesant icons to add to the model.  Produces a PDF document of your Idea, Team, Product, Revenue, Funding Goals and Partnership.  I think this is turning out an executive summary and does really help you focus on the message (with "tweet length" limits)
&lt;/p&gt;

&lt;h2&gt;&lt;a href="http://opus.io/canvas"&gt;Opus Business Canvas&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;update:&lt;/strong&gt; dropping this canvas tool - use bmfiddle!&lt;/p&gt;
&lt;p&gt;
This last one is ours, just made it while working through Start-Up Owners Manual.
It has a typical canvas layout, allows for markdown input, exportable as markdown as well.  Canvas is free and can be shared widely with your collaborators.  Our UI is a bit more limited than the others.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/IASItqOEAX4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/3244187034122564973/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=3244187034122564973&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/3244187034122564973?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/3244187034122564973?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/IASItqOEAX4/10-business-model-canvas-tools-review.html" title="10 Business Model Canvas Tools - Review" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/07/10-business-model-canvas-tools-review.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYNQX09fyp7ImA9WhJQEUo.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-4050071316611678534</id><published>2012-07-23T12:25:00.000-07:00</published><updated>2012-07-24T17:46:30.367-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-24T17:46:30.367-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="entrepreneur" /><category scheme="http://www.blogger.com/atom/ns#" term="money" /><category scheme="http://www.blogger.com/atom/ns#" term="VoIP" /><category scheme="http://www.blogger.com/atom/ns#" term="twilio" /><title>Understanding Twilio Costs - It's not $0.01/minute</title><content type="html">&lt;p&gt;
We do lots of work with Twilio - it powers our political phone banking software and is the back-end for our virtual branch exchange - and of course we provide development/engineering services for those looking to integrate Twilio.
&lt;/p&gt;

&lt;p&gt;
One significant issue we encounter with almost every new Twilio user is their mis-conceptions about how Twilio bills and what their costs will be.
&lt;/p&gt;

&lt;h2&gt;The Penny per Minute Myth&lt;/h2&gt;
&lt;p&gt;
When we had our main office line hosted on a true VoIP service the cost was $0.01/minute - yes - one cent per minute.  We migrated to Twilio - now inbound calls ( which are generally forwarded to another phone number) are billed at $0.03/minute.  Where did the other two cents come from?
&lt;/p&gt;

&lt;p&gt;
Traditional providers charge only for one leg of the call - that is the inbound or outbound leg.  This leg of the call originates/terminates from your VoIP system (we like FreeSWITCH).  On Twilio however there are frequently &lt;b&gt;two&lt;/b&gt; legs of the call.
&lt;/p&gt;

&lt;div&gt;
&lt;img src="http://vbx.io/i/twilio-routing.png"&gt;
&lt;/div&gt;

&lt;p&gt;
The top example shows traditional VoIP operations - where the call goes to your server, or some "server" you operate and the other side is on your existing infrastructure.  With Twilio however that "server" is them.
&lt;/p&gt;

&lt;p&gt;
So, when using Twilio to route (forward) inbound calls to another device you'll be paying for both legs of the call.  This is clearly visible in the billing reports from VBX - where the two legs are shown together.
&lt;/p&gt;
&lt;div style="text-align:center;"&gt;
&lt;img src="http://vbx.io/i/twilio-billing.png"&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/DbGnZShT8Z8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/4050071316611678534/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=4050071316611678534&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/4050071316611678534?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/4050071316611678534?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/DbGnZShT8Z8/understanding-twilio-costs-its-not.html" title="Understanding Twilio Costs - It's not $0.01/minute" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/07/understanding-twilio-costs-its-not.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUEGRn0ycCp7ImA9WhJRGEw.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-4635735800136163652</id><published>2012-07-20T12:39:00.001-07:00</published><updated>2012-07-20T12:47:07.398-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-20T12:47:07.398-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="start-up" /><category scheme="http://www.blogger.com/atom/ns#" term="Engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="Business Services" /><title>Five Warning Signs about your Technology Person/Team</title><content type="html">&lt;p&gt;
It's almost unreal how much your business depends on technology.  Computers, Internet, Mobile, Social even the old-school fax machine is technology.  It is a critical component of your business.
&lt;/p&gt;

&lt;p&gt;
Over the past decade we've seen numerous times where the technology needs of a business were not being met.  Sadly, many business operators are yoked to the wrong fit for their technology providers.  Are the consultants, developers, engineers, technicians you work with on a daily delivering the value you need?  Are they contributing or cramping your business?
&lt;/p&gt;

&lt;p&gt;
Here are five of the behaviours that, at least according to us, should be taken as warning signs.  These actions, or in-action, could be costing you hundreds or even thousands of dollars.
&lt;/p&gt;

&lt;h2&gt;Warning Signs&lt;/h2&gt;

&lt;h3&gt;Solitary Knowledge&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;
Do you have only one? Or perhaps one primary who handles 80% of your technology needs? What happens if your one go-to is not available?
&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
This is a simple continuity issue.  If your mission critical systems are in the hands of only one person there is a very large single point of failure.  If this person is unavailable what happens?  For many the work stops, or is delayed.  Think about the difficulty (both time and cost) with finding a replacement.
&lt;/p&gt;
&lt;p&gt;
It is business-critical to have more than one person to depend on for their mission critical systems - such as revenue generating web-sites or in-office desktops.
&lt;/p&gt;

&lt;h3&gt;Captive Knowledge&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;
How widely known are your systems?  Where is the documentation? Network maps?  Server information and change-logs?  Code documentation? Wiki? Source control?
&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
All to often this issue is tied directly to Solitary Knowledge - why document when the team is only one?  Without documentation new team members have to scramble in the dark to &amp;quot;get their head around things&amp;quot;.  This is wasted time for new members. Some times the idea of this sunk-cost when brining them on-board prevents the expansion!
&lt;/p&gt;
&lt;p&gt;
If these kinds of things are not available it becomes difficult to on-board new team members. It also makes comparing new members to existing members impossible.  That unshared, internal knowledge that existing team members is being hoarded up.  If fact, this prevents new team members from performing to their best ability.
&lt;/p&gt;

&lt;h3&gt;Infallibility&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;
Is your Tech-team &amp;quot;never wrong&amp;quot;? Is their way always the &amp;quot;best&amp;quot;? How do they respond to new ideas?  How do they respond to outside review of their work?
&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
Tech folks are known for their arrogance/confidence - and lets not confuse that with infallibility.  If your tech-team responds with declination towards others work then look out. When asked about others work do they claim they can do better or faster? If they say yes 100% of the time be wary - nobody is that good.
&lt;/p&gt;

&lt;h3&gt;Superiority/Condescending&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;
How about their review of others work?  Or their reactions to the new team members?
&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
Perhaps you're fortunate enough to bring another person to the team - how does your Alpha member behave?  Is the new guys work &amp;quot;terrible&amp;quot;? Is there heated discussions where the Alpha raises their voice first? (Big warn!).
&lt;/p&gt;
&lt;p&gt;
Too often we've seen these first members belittle, degrade and insult new members.  A bit of hazing is expected but obvious animosity creates an unstable team.  It's a clear indicator that the Alpha is not the right person for the job.
&lt;/p&gt;

&lt;h3&gt;Accountability&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Are they missing deadlines?  Are projects getting pushed later and later?  Is working piling up behind them?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
If the previous four conditions exist you won't even be able to track this. But, if you were, how do they respond when asked &amp;quot;why was this project two weeks late&amp;quot;.  You know what responsibility sounds like and if you don't hear it then look out.
&lt;/p&gt;
&lt;p&gt;
Many times these Solitary, Captive, Infallible, Superior tech-types have zero accountability - with no basis of measurement.  Which documentation and shared knowledge would demonstrate.  Put these systems in place.  Soon! 
&lt;/p&gt; 

&lt;h2&gt;Bottom Line&lt;/h2&gt;
&lt;p&gt;
Don't be afraid to prove-out the people your business depends on.  Ask them tough questions.  Ensure that you are not critically dependent on one person or team member.  Ensure their work stands-up under third party review.  Look for positive attitude towards new ideas and team-members.
&lt;/p&gt;

&lt;p&gt;
Here is a check-list of things to have that can help you build an accountable, dependable and reliable tech-team.
&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2+ humans on the task.&lt;/li&gt;
&lt;li&gt;Documentation System - Wiki or something.&lt;/li&gt;
&lt;li&gt;Issue/Work Tracking System - track assignments, estimates and completion.&lt;/li&gt;
&lt;li&gt;Outside Review - find another person/team to check things out.&lt;/li&gt;
&lt;li&gt;Outside Assistance - bring in other helpers on some tasks and gauge response.&lt;/li&gt;
&lt;li&gt;Manage their Workload and hold them accountable&lt;/li&gt;
&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/ro9ZdSUoqjw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/4635735800136163652/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=4635735800136163652&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/4635735800136163652?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/4635735800136163652?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/ro9ZdSUoqjw/five-warning-signs-about-your.html" title="Five Warning Signs about your Technology Person/Team" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/07/five-warning-signs-about-your.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YNQH8_eCp7ImA9WhJRE00.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-752353203554085307</id><published>2012-07-14T16:39:00.001-07:00</published><updated>2012-07-14T16:39:51.140-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-14T16:39:51.140-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="APIs" /><category scheme="http://www.blogger.com/atom/ns#" term="Amazon Web Services" /><title>mTurk API Needs Your Help!</title><content type="html">&lt;p&gt;
Amazons Mechanical Turk is awesome and needs your help.  They are hiring so I suggest you contact them!  Here is some stuff you can work on:
&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;CreateHIT API needs a way to make the HIT visible in the standard UI&lt;/li&gt;
&lt;li&gt;Dispose and Disable behave inconsistently&lt;/li&gt;
&lt;li&gt;Worker Feedback exposes their Email Address - a violation of Amazon TOS&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can &lt;a href="https://requester.mturk.com/careers"&gt;fix those problems&lt;/a&gt;.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/CNCCXnUfMbw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/752353203554085307/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=752353203554085307&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/752353203554085307?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/752353203554085307?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/CNCCXnUfMbw/mturk-api-needs-your-help.html" title="mTurk API Needs Your Help!" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/07/mturk-api-needs-your-help.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUMRHw9eSp7ImA9WhJSEUU.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-1479987344670328997</id><published>2012-07-01T17:18:00.000-07:00</published><updated>2012-07-01T17:18:05.261-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-01T17:18:05.261-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SEO" /><category scheme="http://www.blogger.com/atom/ns#" term="google" /><title>Be Careful Of Geo-Targeted Domains</title><content type="html">&lt;p&gt;
Just recently we were assisting a young company with a roll-out of a new domain &amp;quot;&lt;a href="http://opus.io/"&gt;opus.io&lt;/a&gt;&amp;quot;  Taking a look in the Google Webmaster we noticed the Geotargetable domains was not configurable.
&lt;/p&gt;
&lt;p&gt;
Hrm, it is for other domains we operate.  Well, &lt;a href="http://support.google.com/webmasters/bin/answer.py?hl=en&amp;answer=1347922"&gt;it's not changeable for &lt;em&gt;.io&lt;/em&gt;&lt;/a&gt; - but many others are OK.
&lt;/p&gt;
&lt;p&gt;
As usual, &lt;a href="http://domaininfo.buydomains.com/domain-names/geo-targeted-domainsmatt-cutts/" rel="nofollow"&gt;domain sellers hype this&lt;/a&gt;.  And of course Google provides explicit instructions on how to configure Geotargeting.
&lt;/p&gt;
&lt;p&gt;
&lt;p&gt;
You can watch what &lt;a href="http://www.youtube.com/watch?v=GY65Mlgw124"&gt;Matt says&lt;/a&gt; about it to get the complete story.
&lt;/p&gt;
&lt;h2&gt;GeoTargeting Summary&lt;/h2&gt;
&lt;p&gt;
I'm thinking it breaks down to these two points.
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;There are 38 blessed non-targeted domains&lt;/li&gt;
&lt;li&gt;Other domains are country targeted, &amp;quot;swimming up-stream&amp;quot; to target others&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
What this means for opus.io is that, it will be seen by Google as more relevant to the &lt;em&gt;British Indian Ocean Territory&lt;/em&gt; than US or UK visitors.
&lt;/p&gt;
&lt;p&gt;
Make sure your domain falls in this blessed list for best global visibility, and specifically target that TLD when necessary. You can use &lt;a href="http://seosorcerer.com/" title="seo domain check"&gt;this tool&lt;/a&gt; to check.
&lt;/p&gt;
&lt;p&gt;
Here's to hoping that Google adds &lt;em&gt;.io&lt;/em&gt; to their list of blessed domains soon.
&lt;/p&gt;
&lt;p&gt;
Also, aren't TLDs going to be opened wide-up soon? So, that makes gTLD, rTLD and gccTLD stuff less relevant?
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/EMDuPkvJdlc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/1479987344670328997/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=1479987344670328997&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1479987344670328997?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1479987344670328997?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/EMDuPkvJdlc/be-careful-of-geo-targeted-domains.html" title="Be Careful Of Geo-Targeted Domains" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/07/be-careful-of-geo-targeted-domains.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQGSXw5eip7ImA9WhJTEkk.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-8114786047149917195</id><published>2012-06-20T17:45:00.000-07:00</published><updated>2012-06-20T17:58:48.222-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-20T17:58:48.222-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="javascript" /><category scheme="http://www.blogger.com/atom/ns#" term="APIs" /><category scheme="http://www.blogger.com/atom/ns#" term="chrome" /><category scheme="http://www.blogger.com/atom/ns#" term="google" /><title>Chrome Extension Content Security Policy &amp; Manifest Version 2</title><content type="html">&lt;p&gt;
Starting around Chrome/Chromium 18 extensions are moving to manifest version two and this starts enforcing a content security policy.  Many extension developers will need to update their manifest and re-write some code.
&lt;/p&gt;

&lt;p&gt;
Here's what we had to do for the Twilio Client Extension.
&lt;/p&gt;

&lt;h4&gt;Update the Manifest&lt;/h4&gt;
&lt;p&gt;
The Manifest needs to change how the content is loaded.
&lt;/p&gt;
&lt;pre&gt;
{
  "manifest_version": 2,
  "content_security_policy": "media-src 'self' https://*.static.twilio.com; object-src 'self' https://*.static.twilio.com; script-src 'self' https://*.static.twilio.com;",
  "background": {
      "page":"background.html"
  },

&lt;/pre&gt;
&lt;p&gt;
The previous setting for &lt;em&gt;background_page&lt;/em&gt; is gone.
&lt;/p&gt;

&lt;h4&gt;Content Security Policy&lt;/h4&gt;
&lt;p&gt;
This was the more confusing part of this update for me as I'd only had passing exposure to CSP before.  Read the &lt;a href="http://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html#syntax"&gt;W3C docs&lt;/a&gt;, it shows where the names like &lt;strong&gt;*-src&lt;/strong&gt; come from.
&lt;/p&gt;

&lt;p&gt;
What our CSP shows is that we load media from self and from all HTTPS hosts inside of the static.twilio.com domain, including static.twilio.com itself.  This was necessary otherwise the JS console will throw errors like:
&lt;blockquote&gt;
Refused to load script from 'https://static.twilio.com/libs/twiliojs/1.0-392a7f1/twilio.js' because of Content-Security-Policy.
&lt;/blockquote&gt;
&lt;/p&gt;

&lt;h4&gt;Removing In-Line JavaScript&lt;/h4&gt;
&lt;p&gt;
This part is pretty easy, and you know you should have built your code this way in the first place but, like many, used the in-line methods for "convenience" :)
&lt;/p&gt;

&lt;p&gt;
This means all the stuff that was built like this needs to be removed.
&lt;/p&gt;
&lt;pre&gt;
&lt;!-- It's a No No Now --&gt;
&amp;lt;script type="text/javascript"&amp;gt;
var bgp = chrome.extension.getBackgroundPage();
bgp.doCoolness();

$('#some_field').on('click',some_routine());
&amp;lt;/script&amp;gt;
&lt;/pre&gt;

&lt;p&gt;
Should be re-constructed to load from a source.
&lt;/p&gt;
&lt;pre&gt;
&amp;lt;script type="text/javascript" src="j/ext.js"&amp;gt;&amp;lt;/script&amp;gt;
&lt;/pre&gt;

&lt;p&gt;
Of course, now your scripts need to wait till DOM ready, so some things must be wrapped inside of ye-ould event listener.
&lt;/p&gt;

&lt;pre&gt;
// 100s of lines of JS here

// Last
document.addEventListener("DOMContentLoaded", function () {
  my_ext.init();
  my_ext.be_cool({duration:'forever'});
});
&lt;/pre&gt;

&lt;p&gt;HTH&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/Z-XlxU88fPs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/8114786047149917195/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=8114786047149917195&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8114786047149917195?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8114786047149917195?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/Z-XlxU88fPs/chrome-extension-content-security.html" title="Chrome Extension Content Security Policy &amp; Manifest Version 2" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/06/chrome-extension-content-security.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQFRXg_cCp7ImA9WhJTEUU.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-1253457161996144429</id><published>2012-06-20T01:18:00.001-07:00</published><updated>2012-06-20T01:18:34.648-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-20T01:18:34.648-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="APIs" /><category scheme="http://www.blogger.com/atom/ns#" term="code" /><title>Twilio API Paging &amp; GnuTLS Issues</title><content type="html">&lt;p&gt;
Just recently we were working on some updates for our &lt;a href="http://vbx.io/"&gt;hosted twilio application&lt;/a&gt; service and ran into some issues with a larger volume of call traffic (32K/mo).
&lt;/p&gt;

&lt;h4&gt;GnuTLS Errors from Twilio&lt;/h4&gt;
&lt;p&gt;
This is a snip of the error that was being spewed out from the cURL library.
&lt;/p&gt;
&lt;pre&gt;
56:GnuTLS recv error (-9): A TLS packet with unexpected length was received.
&lt;/pre&gt;

&lt;h4&gt;Problem Circumstances&lt;/h4&gt;
&lt;p&gt;
These issues only occurred when paging backwards through the records, and only after few requests have been issues.  That is, paging backwards by 1024 records we saw the errors round pages 30 (of 80+).  There was no consistent behaviour.
&lt;/p&gt;

&lt;p&gt;
Naturally we contacted the Twilio support team (which is pretty good!)
And we through few steps with them.
&lt;/p&gt;

&lt;p&gt;
These issues would still occur when we tried page sizes of 512 and 256 and 128.
Other attempts at resolution we tried were using different versions of SSL (SSLv2, SSLv3, TLSv1).  All the requests were throwing this error in-side of the 30s timeout that is implemented on the Twilio API.
&lt;/p&gt;

&lt;h4&gt;Problem Resolution&lt;/h4&gt;
&lt;p&gt;
The actual fix for us was a two part process.
Firstly, we added a retry loop on our Twilio requests (as suggested by Twilio support).
&lt;/p&gt;
&lt;p&gt;
Also, very important when using the Twilio APIs and paging back through the records is to use the &amp;quot;next_uri&amp;quot; returned in the response.  There is a special parameter there &lt;strong&gt;AfterSid&lt;/strong&gt; which provides a good performance hint for the Twilio system.
&lt;/p&gt;

&lt;p&gt;HTH&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/b-ezPTC58Lg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/1253457161996144429/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=1253457161996144429&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1253457161996144429?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1253457161996144429?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/b-ezPTC58Lg/twilio-api-paging-gnutls-issues.html" title="Twilio API Paging &amp; GnuTLS Issues" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/06/twilio-api-paging-gnutls-issues.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08NQn05cSp7ImA9WhJTEEk.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-8443665241643771998</id><published>2012-06-18T11:58:00.000-07:00</published><updated>2012-06-18T11:58:13.329-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-18T11:58:13.329-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Web-Applications" /><category scheme="http://www.blogger.com/atom/ns#" term="entrepreneur" /><category scheme="http://www.blogger.com/atom/ns#" term="start-up" /><category scheme="http://www.blogger.com/atom/ns#" term="hellarad" /><title>Hella Rad Project Management</title><content type="html">&lt;p&gt;
We just heard the scoop today (announced on Seattle Tech Start-ups list) that &lt;a href="http://www.artefactgroup.com/"&gt;Artefact&lt;/a&gt; has launched their unbelievably awesome project management software called &lt;a href="http://www.10000ft.com/"&gt;10000ft&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
Only 20 minutes ago Shyam sent the email blast.  I went straight to check it out. The landing page - was easy, gave clear info in a simply way. A great first impression.
&lt;/p&gt;

&lt;h2&gt;Sign-Up Done Right&lt;/h2&gt;
&lt;p&gt;
Their sign-up process is what all others should aspire to be.  One simple page, no requirements for credit-card; get started right now.
&lt;/p&gt;
&lt;p&gt;
And to follow that, their system initialises your environment with some reasonable play data so you can get started right away.
&lt;/p&gt;

&lt;h2&gt;Other Impressions&lt;/h2&gt;
&lt;p&gt;
Their UX team hit the grand-salami!  There are awesome user hints the whole way through, it's direct and easy to find the tools you're looking for.  The budgeting feature was just about brain-dead easy to use and the reports are easy enough for even the dimmest of PHBs to get.
&lt;/p&gt;

&lt;p&gt;
This is an example of a good team with a laser focus on what their product does: fluid project management.  Congratulations to Rob, Shyam and the rest of the 10000ft team.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/77eqHVrjcdU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/8443665241643771998/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=8443665241643771998&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8443665241643771998?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8443665241643771998?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/77eqHVrjcdU/hella-rad-project-management.html" title="Hella Rad Project Management" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/06/hella-rad-project-management.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQARH4_eSp7ImA9WhVaGUo.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-1892651431020052035</id><published>2012-06-17T14:59:00.000-07:00</published><updated>2012-06-17T14:59:05.041-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-17T14:59:05.041-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="entrepreneur" /><category scheme="http://www.blogger.com/atom/ns#" term="Business Services" /><title>CapLinked Doesn't Work Right, has No Value</title><content type="html">&lt;p&gt;
CapLinked found our company, through the magic of the Internet on May 17th 2012.
Since that time they have been bombing our inbox on a weekly basis with worthless messages.
&lt;/p&gt;

&lt;h2&gt;What is CapLinked&lt;/h2&gt;
&lt;p&gt;
CapLinked claims to be a service that helps to make private investment easy and you find Investors and Advisors for your business.
&lt;/p&gt;

&lt;h2&gt;But Edoceo Doesn't Trust Them?&lt;/h2&gt;
&lt;p&gt;
Nope, For a few simple reasons.
&lt;/p&gt;

&lt;h3&gt;Contact via Generic Mail Address&lt;/h3&gt;
&lt;p&gt;
We never contacted CapLinked, instead they contact us. Through a generic email address in our domain (&lt;em&gt;info&lt;/em&gt;).  Lame. A better demonstration of their legitimacy as an organisation would be to contact through less generic.  And, of course our account was created without action on our part so our first order would be to reset the password on an account we never made.
&lt;/p&gt;
&lt;p&gt;
We've had multiple contacts with investors, advisors, angels &amp;c; not once has that contact come through a generically guessable address.  Quite the opposite in fact, contact was made via telephone or LinkedIn.
&lt;/p&gt;


&lt;h3&gt;Pre-Fab Account Creation&lt;/h3&gt;
&lt;p&gt;
The initial email was because CapLinked had already created a profile for us! Unfortunately, the profile was incomplete which means any of the other CapLinked users looking at us would think we are lame due to the lack of information on our profile.
&lt;/p&gt;
&lt;p&gt;
It is not cool to automatically create a public profile for a person/company with incomplete information and then ask them to claim it.  CapLinked should have waited for us to come to them (eg: like &lt;a href="http://www.crunchbase.com/"&gt;CrunchBase&lt;/a&gt; does it).
&lt;/p&gt;

&lt;h3&gt;Non-Functional Un-subscribe&lt;/h3&gt;
&lt;p&gt;
Naturally we tried their un-subscribe option.
That did not work.
&lt;/p&gt;
&lt;p&gt;
A sure sign of a poorly operated company is a non-functional un-subscribe system.
&lt;/p&gt;

&lt;h3&gt;Claim Feature Broken&lt;/h3&gt;
&lt;p&gt;
So, finally we tried to claim our company.  We were sent a "Claim Edoceo on CapLinked" email with a simple hyper-link.  We followed it (incognito window of course).  The page showed our incomplete profile with a clearly defined "Claim this company" button - which I clicked.
&lt;/p&gt;
&lt;p&gt;
Within a few seconds I was sent another "Claim Edoceo on CapLinked" email - exact same text, formatting and message - except the hyper-link hash was a bit different.  So, naturally we followed that link again.  That resulted in the error message: "This company has been claimed by another user.".
&lt;/p&gt;

&lt;h3&gt;Duplicated Companies to Claim&lt;/h3&gt;
&lt;p&gt;
Once we finally get into their system it's odd that there are two profiles for Edoceo - but both have the same stub.  Lame.
&lt;/p&gt;

&lt;h2&gt;Summary&lt;/h2&gt;
&lt;p&gt;
First you make an incomplete profile of my company and notify our generic contact address it exists.  Then both the Un-subscribe and Claim features of the system don't work.  Duplicated company profiles and the only way to get a verified account is to pay $40/mo.  Edoceo will stick with traditional methods of engaging investors, advisors and clients.
&lt;/p&gt;

&lt;p&gt;
Edoceo fixes problem like these; we build systems that work.  Perhaps CapLinked should contact us to get their system operational?
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/4hqAxBg5X-s" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/1892651431020052035/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=1892651431020052035&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1892651431020052035?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/1892651431020052035?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/4hqAxBg5X-s/caplinked-doesnt-work-right-has-no.html" title="CapLinked Doesn't Work Right, has No Value" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/06/caplinked-doesnt-work-right-has-no.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYAR3YyfSp7ImA9WhVbGEk.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-8380724259497662444</id><published>2012-06-04T15:15:00.000-07:00</published><updated>2012-06-04T15:15:46.895-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-04T15:15:46.895-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Web-Applications" /><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="Engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="custos" /><title>How many Users can Our System Support?</title><content type="html">&lt;p&gt;
This is a question we are frequently asked.
&lt;/p&gt;
&lt;blockquote&gt;
How many users can I support.
&lt;/blockquote&gt;

&lt;p&gt;
The answer is always complicated and conversations typically go something like:&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Customer:&lt;/em&gt; We are getting ready to scale up; are we ready to handle 100 mega-users?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Edoceo:&lt;/em&gt; how many users are on the system now, what resources do you have?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;C:&lt;/em&gt; We've got a million sign-ups and we're hosted at Rackspace.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;E:&lt;/em&gt; No, how many servers? What is the environment?  How much existing load, &amp;amp;c.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;C:&lt;/em&gt; We have two servers, it's built with RoR and uses a combination of MySQL and MongoDB (for web-scale).  I think we have lots of room - we have 4Gig of RAM - so how many users can we handle?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;E:&lt;/em&gt; We need lots of data to make that prediction, step one is to measure the current usage and resource consumption, increase the usage and then review the measurements again - that will give us two points on a grid from which we can make linear predictions - of course more samples are better.  What do you use for monitoring now?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;C:&lt;/em&gt; Rackspace tells us when the server is down.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;E:&lt;/em&gt; :(&lt;/p&gt;

&lt;p&gt;
This goes on for some time, attempting to translate user-accounts to actual users.  There is a world of difference between 400m user-accounts and 400m active users in a 12h period.  The critical performance metric is active users.
&lt;/p&gt;

&lt;p&gt;
Once you have a measurement of active users, then we determine what resources active users require.  Naturally this necessitates measurement of these resources such as CPU, RAM, HDD, Network and various services such as web-servers, database-servers, caching servers and many other aspects (we could go on and on).  Without these metrics capacity prediction will be impossible.
&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Decide Acceptable Performance, eg 1 second TTLB on homepage.&lt;/li&gt;
&lt;li&gt;Determine Active Users, eg: recent session count&lt;/li&gt;
&lt;li&gt;Measure resource consumption at current level&lt;/li&gt;
&lt;li&gt;Use gauges and equations to predict growth/consumption rates&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;Finding Active Users&lt;/h2&gt;
&lt;p&gt;
Some determination needs to be made with regard to measuring active users.  How long is their session?  How frequent are their page requests?  Some web-apps/sites have less, some more.  Make a determination for your environment.  For example we check active sessions that are updated in the last four minutes.  That becomes our basis for creating a base-line measurement.
&lt;/p&gt;

&lt;pre&gt;
# example script which queries a session database server and publishes metric
val=$(psql \
    --quiet \
    --no-align \
    --tuples-only  \
    --command &amp;quot;SELECT count(id) FROM session WHERE atime &gt;= current_timestamp - '4 minutes'::interval; &amp;quot)

curl -d "stat=good" -d "metric=users=$val" 'http://custos/api/service/stat?s=...' &gt;/dev/null
&lt;/pre&gt;

&lt;h2&gt;Measure Resource Consumption&lt;/h2&gt;
&lt;p&gt;
This is perhaps the most time consuming factor in performance monitoring.  Configuring first the collector system and then configuring the environment.  There are many monitoring systems to choose from and thousands of scripts for collecting metrics.
&lt;/p&gt;

&lt;p&gt;
The collection system will likely be one of: Nagios, OpenNMS, MRTG+Cacti but could also be tools from WatchMouse, CloudKick or even our &lt;a href="http://custos.io"&gt;Custos&lt;/a&gt; system (currently beta).  These system will use the scripts to collect the system metrics and hopefully build nice charts and graphs that are used in the next phase.
&lt;/p&gt;

&lt;h3&gt;What Metrics to Capture&lt;/h3&gt;
&lt;p&gt;
Determining what to capture on the hardware/software side is a bit easier, we almost already know what to measure. Generally we start with the &amp;quot;standard&amp;quot; things such as CPU, RAM, HDD and NIC - that is processor, memory, disk and network.


&lt;h2&gt;Making the Predictions&lt;/h2&gt;
&lt;p&gt;
Once these metrics are collected, for some usable time-period then we can start the game of predicting the future.
For example: knowing how much, RAM, CPU and other resources are used for 400 users, we can then extrapolate how much resources are needed for 4000 users.
The graphs also can show growth rates for data, which can let one know when to upgrade/improve the database back-ends.
&lt;/p&gt;

&lt;p&gt;
Usage predictions are difficult at best, collecting the metrics is the critical first-step to planning for web-site growth.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/hAjBduzrwSY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/8380724259497662444/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=8380724259497662444&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8380724259497662444?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/8380724259497662444?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/hAjBduzrwSY/how-many-users-can-our-system-support.html" title="How many Users can Our System Support?" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/06/how-many-users-can-our-system-support.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQESHo8eip7ImA9WhJQEUo.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-6427969643956435755</id><published>2012-05-16T15:09:00.000-07:00</published><updated>2012-07-24T17:48:29.472-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-24T17:48:29.472-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Web-Applications" /><category scheme="http://www.blogger.com/atom/ns#" term="e-commerce" /><category scheme="http://www.blogger.com/atom/ns#" term="Fail" /><category scheme="http://www.blogger.com/atom/ns#" term="Internet" /><title>eNom Doesn't Care about their Credit Card UI</title><content type="html">&lt;p&gt;
Almost 12 months ago we reported to eNom that their user interface had a bug.  The issue causes an inconvience for users but, it's not fatal.  Sadly, it's an easy fix too - but eNom just has done nothing. Lazy.
&lt;/p&gt;

&lt;h2&gt;The eNom Bug&lt;/h2&gt;
&lt;p&gt;
On the account refill page users are presented with form, which includes some account, including phone number.
Notice, and this is the bug, that the phone number is mangled on this form.
Other parts of the eNom system display this phone number correctly, including their WHOIS data.
&lt;/p&gt;

&lt;p&gt;
Not a serious bug right?
The problem is that, when using the refill form customers (like us) don't pay much attention to that field.
Why would we?
The phone number was set when we created the account and our number has been the same the whole time.
But it mangles our data when we save.
&lt;/p&gt;

&lt;p&gt;
Also, how lame is it to have a broken form on your website? Lame.
How lame is it when that form is the credit card form? Double lame.
Hard to have confidence in a company that cannot manage something so simple as phone number data.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/vh5K2wvBxrk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/6427969643956435755/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=6427969643956435755&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/6427969643956435755?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/6427969643956435755?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/vh5K2wvBxrk/enom-doesnt-care-about-their-credit.html" title="eNom Doesn't Care about their Credit Card UI" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/05/enom-doesnt-care-about-their-credit.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQGRXs7fSp7ImA9WhVXE0g.&quot;"><id>tag:blogger.com,1999:blog-2202207999277431930.post-7519359153990063002</id><published>2012-04-13T16:03:00.002-07:00</published><updated>2012-04-13T16:05:24.505-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-04-13T16:05:24.505-07:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Internet" /><title>See You in Hell Blogger</title><content type="html">&lt;p&gt;
Blogs are dead, or at least this one is.  It's so &amp;quot;2000 &amp;amp; late&amp;quot; to be blogging so we're dropping it.
&lt;/p&gt;

&lt;p&gt;
The fad known as blogging is over, &amp;quot;it's dead Jim&amp;quot;.  The functionality that it used to offer is now replaced by Twitter (worthless), Facebook, Tumbler and Google+ streams (among others).  So, stop blogging and start stream-posting! (streamcasting?).
&lt;/p&gt;

&lt;p&gt;
It was kind of nice to be able to replay the Blog feed to our home-page, which is not possible from Google+ (unless using &lt;a href="http://blstr.co/"&gt;Blstr!&lt;/a&gt;) but that was only a marginal gain.
&lt;/p&gt;

&lt;p&gt;
We'll continue to publish useful information about Linux on our &lt;a href="http://praxis.edoceo.com/" title="Linux How To Guides"&gt;Praxis&lt;/a&gt; site, about coding web-applications on our &lt;a href="http://radix.edoceo.com/" title="PHP Framework"&gt;Radix&lt;/a&gt; site, performance monitoring on &lt;a href="http://custos.edoceo.com" title="performance monitoring"&gt;Custos&lt;/a&gt; and other useful information on our &lt;a href="http://edoceo.com/"&gt;primary site&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
Blogging is dead, moving on.
&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;!-- Post Feed Footer --&gt;
&lt;address&gt;http://blog.edoceo.com/&lt;/address&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/EdoceosBlog/~4/LkYeiEF4h00" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.edoceo.com/feeds/7519359153990063002/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2202207999277431930&amp;postID=7519359153990063002&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7519359153990063002?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2202207999277431930/posts/default/7519359153990063002?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EdoceosBlog/~3/LkYeiEF4h00/see-you-in-hell-blogger.html" title="See You in Hell Blogger" /><author><name>David Busby</name><uri>https://plus.google.com/100813199769666372911</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh4.googleusercontent.com/-53KD7AazY_g/AAAAAAAAAAI/AAAAAAAAATs/NFaJRTuf3hE/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://blog.edoceo.com/2012/04/see-you-in-hell-blogger.html</feedburner:origLink></entry></feed>
