<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>gladlyCode</title>
	<atom:link href="http://gladlycode.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://gladlycode.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 29 Sep 2010 03:46:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Singapore number is 9035 5240</title>
		<link>http://gladlycode.com/2010/singapore-sms-gateway-down/</link>
		<comments>http://gladlycode.com/2010/singapore-sms-gateway-down/#comments</comments>
		<pubDate>Mon, 23 Aug 2010 13:02:24 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[disruption]]></category>
		<category><![CDATA[expiry]]></category>
		<category><![CDATA[mistake]]></category>
		<category><![CDATA[opps]]></category>
		<category><![CDATA[silly]]></category>
		<category><![CDATA[singapore]]></category>
		<category><![CDATA[sms]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=109</guid>
		<description><![CDATA[
			
				
			
		
gladlyCast has been in operation for more than a year and your generous support has been appreciated. Lately we have been busy with our own work and have found it hard to contribute to this project. It is regrettable that the gladlyCast Singapore mobile phone number has expired as we did not top up the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fsingapore-sms-gateway-down%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fsingapore-sms-gateway-down%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>gladlyCast has been in operation for more than a year and your generous support has been appreciated. Lately we have been busy with our own work and have found it hard to contribute to this project. It is regrettable that the gladlyCast Singapore mobile phone number has expired as we did not top up the service in time.</p>
<p>Unfortunately we cannot recover the current Singapore phone number. You can&#8217;t imagine how silly we are feeling right now.</p>
<p>The remedy plan was to get a new number as soon as we possibly can and announced it. <strong>Our new number for Singapore is +65 9035 5240.</strong></p>
<p>We ask you, our users, to tell your friends about it, help us explain the situation, and forgive our oversight.</p>
<p>Thank you.</p>
<p>Yours,<br />
K.</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2010/singapore-sms-gateway-down/feed/</wfw:commentRss>
		<slash:comments>22</slash:comments>
		</item>
		<item>
		<title>We were on TODAY</title>
		<link>http://gladlycode.com/2010/we-were-on-today/</link>
		<comments>http://gladlycode.com/2010/we-were-on-today/#comments</comments>
		<pubDate>Tue, 17 Aug 2010 01:48:46 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=107</guid>
		<description><![CDATA[
			
				
			
		
&#8230; with the accurate capitalization of our name too!


Pennywise but tech savvy, too
by May Chua
Twitter is no fun if you can&#8217;t send updates on the go. Use free services like gladlyCast to have your SMSes pushed to Twitter. Log on to gladlycast.com and sign in with your Twitter account to set it up. The SMSes [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fwe-were-on-today%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fwe-were-on-today%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>&#8230; with the accurate capitalization of our name too!</p>
<p><img src="http://gladlycode.com/assets/2010/08/showimageCC.jpg" alt="TODAY comic" title="TODAY comic" width="433" height="450" class="aligncenter size-full wp-image-108" /></p>
<blockquote>
<h3>Pennywise but tech savvy, too</h3>
<p>by May Chua</p>
<p>Twitter is no fun if you can&#8217;t send updates on the go. Use free services like gladlyCast to have your SMSes pushed to Twitter. Log on to gladlycast.com and sign in with your Twitter account to set it up. The SMSes are sent to a local number, so you can use your free SMSes to tweet away happily whenever you want.</p></blockquote>
<p>Full article: <a href="http://www.todayonline.com/Tech/EDC100813-0000121/Pennywise-but-tech-savvy,-too">http://www.todayonline.com/Tech/EDC100813-0000121/Pennywise-but-tech-savvy,-too</a></p>
<p>Thanks to all your support and TODAY for writing about us.</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2010/we-were-on-today/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>New Singapore number: +65 8262 9845</title>
		<link>http://gladlycode.com/2010/new-singapore-number-65-8262-9845/</link>
		<comments>http://gladlycode.com/2010/new-singapore-number-65-8262-9845/#comments</comments>
		<pubDate>Fri, 07 May 2010 14:55:13 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[recovery]]></category>
		<category><![CDATA[singapore]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=106</guid>
		<description><![CDATA[
			
				
			
		
Our Singapore server is now back online, with a new number: +65 8262 9845. (NOTE: The new number is +65 9035 5240.)
Unfortunately, we had to bid farewell to our earlier Singapore number. We are not able to recover it.
Please update your phone or address book with our new Singapore number.
And if you would do us [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fnew-singapore-number-65-8262-9845%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fnew-singapore-number-65-8262-9845%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>Our Singapore server is now back online, with a new number: +65 8262 9845. <strong>(NOTE: The new number is +65 9035 5240.)</strong></p>
<p>Unfortunately, we had to bid farewell to our earlier Singapore number. We are not able to recover it.</p>
<p>Please update your phone or address book with our new Singapore number.</p>
<p>And if you would do us favor, we would appreciate if you could also inform your friends about our new number. :)</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2010/new-singapore-number-65-8262-9845/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>gladlyCast down for Singapore</title>
		<link>http://gladlycode.com/2010/gladlycast-down-for-singapore/</link>
		<comments>http://gladlycode.com/2010/gladlycast-down-for-singapore/#comments</comments>
		<pubDate>Fri, 07 May 2010 01:14:05 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[service disruption]]></category>
		<category><![CDATA[singapore]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=105</guid>
		<description><![CDATA[
			
				
			
		
Our Singapore number is having issues. We will update at the end of today, May 7. In meantime, do not send in messages to our Singapore number.
Thanks for your understanding.
]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fgladlycast-down-for-singapore%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2010%2Fgladlycast-down-for-singapore%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>Our Singapore number is having issues. We will update at the end of today, May 7. In meantime, do not send in messages to our Singapore number.</p>
<p>Thanks for your understanding.</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2010/gladlycast-down-for-singapore/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Technical oppses</title>
		<link>http://gladlycode.com/2010/technical-oppses/</link>
		<comments>http://gladlycode.com/2010/technical-oppses/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 15:16:40 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[regression]]></category>
		<category><![CDATA[technical]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=103</guid>
		<description><![CDATA[
			
				
			
		
We have had some technical oppses and have since resolved it. Tweets have been delayed, however. We have increased the flood caps to send out the tweets faster.
This time, the issue has been mostly a mistake on our part. We have failed to take sufficient measures to keep the gladlyCast code base up-to-date and we [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2010%2Ftechnical-oppses%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2010%2Ftechnical-oppses%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>We have had some technical oppses and have since resolved it. Tweets have been delayed, however. We have increased the flood caps to send out the tweets faster.</p>
<p>This time, the issue has been mostly a mistake on our part. We have failed to take sufficient measures to keep the gladlyCast code base up-to-date and we succumbed issues concerning software regression.</p>
<p>In time, we should be pushing out all the tweets by midnight. We are observing the gladlyCast system closely for a couple of days.</p>
<p>Happy tweeting!</p>
<p><em>[All tweets have been sent out.]</em></p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2010/technical-oppses/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Unexpected outage due to host&#8217;s power issues</title>
		<link>http://gladlycode.com/2009/rackspace-outage/</link>
		<comments>http://gladlycode.com/2009/rackspace-outage/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 14:35:46 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[offline]]></category>
		<category><![CDATA[outage]]></category>
		<category><![CDATA[power]]></category>
		<category><![CDATA[rackspace]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=102</guid>
		<description><![CDATA[
			
				
			
		
gladlyCast and gladlyCode went offline for almost 2 hours and back online again at 4:00 PM. All Twitter and Plurk updates from Singapore, Malaysia and Philippines are redelivered. There was some issues with our web provider.
Update on Scheduled Maintenance/Interruption
Rackspace has experienced a service interruption during tonight’s scheduled maintenance on UPS Cluster G. We were testing [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2009%2Frackspace-outage%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2009%2Frackspace-outage%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>gladlyCast and gladlyCode went offline for almost 2 hours and back online again at 4:00 PM. All Twitter and Plurk updates from Singapore, Malaysia and Philippines are redelivered. There was some issues with our web provider.</p>
<blockquote><h3>Update on Scheduled Maintenance/Interruption</h3>
<p>Rackspace has experienced a service interruption during tonight’s scheduled maintenance on UPS Cluster G. We were testing phase rotation on a Power Distribution Unit (PDU) when a short occurred and caused us to lose the PDUs behind this Cluster. The phase rotation allows us to verify synchronization of power between primary and secondary sources.</p>
<p>All power has been restored and devices are being brought back online. The PDUs were down for a total of about 5 minutes. We have aborted the maintenance for the remainder of the evening and will reschedule this for another date. (Source: <a href="http://www.rackspace.com/blog/?p=690">Rackspace</a>)</p></blockquote>
<p>User <a href="http://twitter.com/neyrashazeyra">@neyrashazeyra</a> is first to discover it not working. That said, if you discover gladlyCast not to be functioning correctly, do drop us an email or tweet to us. That will certainly alert us quicker. Also, if you&#8217;re interested, TechCrunch is <a href="http://www.techcrunch.com/2009/11/02/large-scale-downtime-at-rackspace-cloud/">affected too and has more about the Rackspace outage.</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2009/rackspace-outage/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Mabuhay Philippines!</title>
		<link>http://gladlycode.com/2009/sms-twitter-philippines/</link>
		<comments>http://gladlycode.com/2009/sms-twitter-philippines/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 11:27:19 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[philippines]]></category>
		<category><![CDATA[pilipinas]]></category>
		<category><![CDATA[sms]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=98</guid>
		<description><![CDATA[
			
				
			
		
gladlyCast is now available in the country of beautiful islands, Philippines.

(Roxas Boulevard taken by jimpg2)
Kumusta po kayo?
Filipinos now can enjoy updating Twitter and Plurk from a local number, with no extra charges, by sending an SMS to +63 929 106 0211.
To sign up and start using the service, you can visit http://gladlyCast.com. 
No need to tell us your [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fsms-twitter-philippines%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fsms-twitter-philippines%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>gladlyCast is now available in the country of beautiful islands, Philippines.</p>
<p><img class="alignnone size-full wp-image-100" title="Roxas Boulevard" src="http://gladlycode.com/assets/2009/10/roxas-small1.jpg" alt="Roxas Boulevard" width="450" height="252" /><br />
<span style="font-size: 0.8em;">(Roxas Boulevard taken by <a href="http://www.flickr.com/photos/jimmydavao/">jimpg2</a>)</span></p>
<p>Kumusta po kayo?</p>
<p>Filipinos now can enjoy updating Twitter and Plurk from a local number, with no extra charges, by sending an SMS to <strong>+63 929 106 0211</strong>.</p>
<p>To sign up and start using the service, you can visit <a href="http://gladlyCast.com">http://gladlyCast.com</a>. </p>
<p>No need to tell us your passwords (for Twitter).<br />
We don&#8217;t insert any self-promotional URL in your tweets.<br />
Simply sign in and start gladlyCasting.</p>
<p>Feel free to drop us a comment or DM us at <a href="http://twitter.com/gladlycast">@gladlyCast</a> if you need any help.</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2009/sms-twitter-philippines/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Why your tweets got delayed</title>
		<link>http://gladlycode.com/2009/twitter-ntt-america-network/</link>
		<comments>http://gladlycode.com/2009/twitter-ntt-america-network/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 18:21:51 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[delay]]></category>
		<category><![CDATA[diagram]]></category>
		<category><![CDATA[explanation]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ntt]]></category>
		<category><![CDATA[ntt america]]></category>
		<category><![CDATA[routing]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=91</guid>
		<description><![CDATA[
			
				
			
		
First of all, gladlyCast users&#8217; tweets has been delayed from around 6 to 11 pm on Oct 18, Malaysian / Singapore time. This has been partially resolved. Your tweets may not be delivered orderly. Read on if you&#8217;re interested in what occurred or if you like bad art.
At around 7:30 pm, we noticed every tweet [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2009%2Ftwitter-ntt-america-network%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2009%2Ftwitter-ntt-america-network%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>First of all, gladlyCast users&#8217; tweets has been delayed from around <strong>6 to 11 pm on Oct 18</strong>, Malaysian / Singapore time. This has been partially resolved. Your tweets may not be delivered orderly. Read on if you&#8217;re interested in what occurred or if you like bad art.</p>
<p>At around <strong>7:30 pm</strong>, we noticed every tweet we attempted to send out failed. We did some troubleshooting and discovered one of the nodes in between gladlyCast and Twitter wasn&#8217;t functioning normally. This is a rough diagram to show you what went wrong &#8212; the route between gladlyCast and Twitter has been disrupted:</p>
<p><img class="size-full wp-image-95" title="gladlyCast was unable to establish a successful connection to Twitter." src="http://gladlycode.com/assets/2009/10/twitter-down-1a.png" alt="gladlyCast was unable to establish a successful connection to Twitter." width="570" height="260" /></p>
<p>We got a little relieved knowing other Twitter services such as TwitPic are also having similar network issues. When we are quite certain one of the nodes of Twitter&#8217;s provider NTT America has failed, we tweeted a short explanation:</p>
<p><a href="http://twitter.com/gladlyCast/status/4965836774"><img class="alignnone size-full wp-image-93" title="Twitter network issues reported" src="http://gladlycode.com/assets/2009/10/twitter-resized.png" alt="Twitter network issues reported" width="380" height="151" /></a></p>
<p>It&#8217;s <strong>10 pm</strong> and the route between gladlyCast and Twitter is unlikely to recover soon. However not all routes are affected, we can successful update Twitter using one of our laptops.</p>
<p>We decided to implement a temporary measure to pull all the tweets from our outbox into one of our laptops. This laptop then acts as the server to Twitter, creating a successful alternate route. The network diagram looks something like that:</p>
<p><img class="size-full wp-image-96" title="Setting up a temporary solution to deliver Twitter messages." src="http://gladlycode.com/assets/2009/10/twitter-down-2.png" alt="Setting up a temporary solution to deliver Twitter messages." width="570" height="352" /></p>
<p>At <strong>11 pm</strong>, we successfully sent out the first tweet with one of our laptops. We finally got the time to read your responses. We got some angry tweets, we got some nice ones too. We understand how timely each SMS update means to you and are just as  frustrated as you are over the issue.</p>
<p><strong>Twitter <a href="http://status.twitter.com/post/216351172/responding-to-network-connectivity-problems">acknowledged the issue</a></strong> couple hours later. We still hope Twitter fixes the problem soon so that we can give the poor laptop proper rest it much deserved.</p>
<p><em>We wrote this to share with you some issues that can occur when we deliver a tweet. We dedicate this entry to one of our users <a href="http://twitter.com/avaricedevil">avaricedevil</a> who wanted to know more on running a web server.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2009/twitter-ntt-america-network/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Now with Plurk</title>
		<link>http://gladlycode.com/2009/plurk-sms/</link>
		<comments>http://gladlycode.com/2009/plurk-sms/#comments</comments>
		<pubDate>Mon, 21 Sep 2009 18:26:28 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[daemon]]></category>
		<category><![CDATA[plurk]]></category>
		<category><![CDATA[sms]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=89</guid>
		<description><![CDATA[
			
				
			
		
We are most excited to announce support for one more conversation universe &#8211; Plurk.
We have been discussing on the possibility of supporting Plurk since a month ago. One of the priorities we had is ease of use and reliability that is similar to what we offered for Twitter. We finally agreed our Plurk feature is [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fplurk-sms%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fplurk-sms%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>We are most excited to announce support for one more conversation universe &#8211; Plurk.</p>
<p>We have been discussing on the possibility of supporting Plurk since a month ago. One of the priorities we had is ease of use and reliability that is similar to what we offered for Twitter. We finally agreed our Plurk feature is good to  be released for your usage.</p>
<p>Plurk SMS support is offered to Singapore and Malaysian users. To update Plurk with your handphone, just <a href="http://gladlycast.com/sign-in-with-plurk">sign in with your existing Plurk email and password</a>. Unlike for Twitter, gladlyCast requires your email and password here. </p>
<p>If you have associated your phone number with Twitter already, sending an SMS to gladlyCast will not only update Twitter but your Plurk too. Have fun (:</p>
<p>In the spirit of Emmys, we&#8217;d like to thank you for all the little feedbacks we have been receiving. This feature would not be possible without Plurk too. Thanks everyone.</p>
<p>You should <a href="http://www.plurk.com/gladlyCast">friend us at Plurk too if you have one</a>.</p>
<p><strong>Tips for users with Twitter and Plurk</strong>:</p>
<ul>
<li>SMS in &#8220;<code>w <strong>twitter</strong> message</code>&#8221; or &#8220;<code>w <strong>t</strong> hi</code>&#8221; to update <strong>Twitter</strong></li>
<li>SMS in &#8220;<code>w <strong>plurk</strong> hi</code>&#8221; or &#8220;<code>w <strong>p</strong> hi</code>&#8221; to update <strong>Plurk</strong>.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2009/plurk-sms/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Scheduled maintenance 22-Sep-2009 @ 2 AM</title>
		<link>http://gladlycode.com/2009/scheduled-maintenance/</link>
		<comments>http://gladlycode.com/2009/scheduled-maintenance/#comments</comments>
		<pubDate>Sun, 20 Sep 2009 14:55:36 +0000</pubDate>
		<dc:creator>gladlyCode</dc:creator>
				<category><![CDATA[gladlyCast]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[maintenance]]></category>
		<category><![CDATA[plurk]]></category>

		<guid isPermaLink="false">http://gladlycode.com/?p=87</guid>
		<description><![CDATA[
			
				
			
		
We are scheduling a homepage refresh for gladlyCast on September 22, at 2 AM, lasting about 15 minutes. This update enables a pending feature and requires a change in our homepage.
Delivery of Twitter status update is not affected in this update and there is no expected downtime.
So once again, it’s Tuesday morning 2 AM, 15 [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fscheduled-maintenance%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgladlycode.com%2F2009%2Fscheduled-maintenance%2F&amp;source=gladlyCode&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>We are scheduling a homepage refresh for gladlyCast on September 22, at 2 AM, lasting about 15 minutes. This update enables a pending feature and requires a change in our homepage.</p>
<p>Delivery of Twitter status update is not affected in this update and there is <strong>no expected downtime</strong>.</p>
<p>So once again, it’s <strong>Tuesday morning 2 AM, 15 minutes</strong>.</p>
<p>On a totally random note, we have <a href="http://www.plurk.com/gladlyCast">a Plurk page</a> and a purple logo. You can friend us there.</p>
<p><strong>Update 2:00 am</strong>: We&#8217;re performing tiny homepage and have chosen not to go offline.<br />
<strong>Update 2:10 am</strong>: Update has been performed &#8211; we are supporting another conversation universe &#8211; Plurk</p>
]]></content:encoded>
			<wfw:commentRss>http://gladlycode.com/2009/scheduled-maintenance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

