<?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>Let's have it ! &#187; blogs</title>
	<atom:link href="http://www.caperet.com/category/blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.caperet.com</link>
	<description>An eclectic mix of technology, news comment, and personal notes.</description>
	<lastBuildDate>Mon, 09 Jan 2012 13:37:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Facebook Redesign and Change Aversion</title>
		<link>http://www.caperet.com/2011/09/facebook-redesign-change/</link>
		<comments>http://www.caperet.com/2011/09/facebook-redesign-change/#comments</comments>
		<pubDate>Thu, 22 Sep 2011 13:41:32 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=729</guid>
		<description><![CDATA[Every time a major site with a big audience changes, there are always going to be detractors. Especially a site like Facebook. People spend a lot of time there, so interface changes are almost tantamount to moving stuff around in their lounge/den. I think there are a number of issues with the new Facebook homepage. [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><a href="http://www.caperet.com/wp-content/uploads/facebook.jpg"><img class="alignleft size-medium wp-image-730" title="Facebook Page" src="http://www.caperet.com/wp-content/uploads/facebook-250x175.jpg" alt="" width="250" height="175" /></a></div>
<p>Every time a major site with a big audience changes, there are always going to be detractors. Especially a site like Facebook. People spend a lot of time there, so interface changes are almost tantamount to moving stuff around in their lounge/den.</p>
<p>I think there are a number of issues with the new Facebook homepage. I&#8217;ve seen it before. It&#8217;s called feature creep. Lots of stuff all clamouring for your attention. Chat, realtime updates, top stories, the rest of the news, adverts, suggestions for friends, app updates, messages (FB-ized email) and notifications. <span id="more-729"></span></p>
<p>Clever use of AJAX saves FB a heavy, slow loading user experience. Unfortunately it also allows stuff to get very busy. Progressive loading is an interesting technique and FB has evangelised it well. They&#8217;ve added a new design pattern I&#8217;m less of a fan of into the mix, inspired no doubt by a pattern I&#8217;ve seen on mobile terminals: revealing scrollbars on mouse over.</p>
<p>For some time you have been able to set overflow:auto on &lt;div&gt; elements so that scrollbars &#8211; regular, OS managed scrollbars that look different depending on whether you&#8217;re a Mac or a PC &#8211; appear if the content goes outside the bounding box as defined for the div. FB are presenting to the masses a funky new way of doing it. A grey rounded scrollbar, as seen on your iPhone / Android terminal when you touch a screen full of text that can scroll, appears when you hover your mouse around each of the blocks of content on the right hand side (and in some other cases too).</p>
<p>I have a big beef with this, because scrollers are now everywhere on the page. You still have your regular scrollbar if you&#8217;re still using a desk/lap-top machine to access the site. Very close to it you now have other scrollable elements that don&#8217;t follow the same rules. They don&#8217;t work the same as OS scrollbars. If like me you often scroll with the keyboard once the area has focus, they&#8217;re a PITA. The target for scrolling is not very wide. The screen looks a mess if you leave all the different boxes scrolled at different points. It&#8217;s not intuitive to know which zones really will scroll or not if text inside them aligns perfectly with then edge of the scrollable zone. So you have to mouse over them, which isn&#8217;t good for an addict of the PgUp, PgDn, Ctrl, Shift and arrow keys like me. I only click to give a zone focus or to position the cursor far from where I am currently.</p>
<p>Other bad karma effect for me: I was assaulted with little bubbles and tutorial messages when the version change happened. Not a discreet &#8220;learn about what&#8217;s new&#8221; that I could easily dismiss, but (IIRC) something like 3 or 4 different notifications all around the screen which meant I had to dismiss them all before getting back to my usual FB timewasting / networking activity.</p>
<p>There is a personality type that resists change, and with group effects in play this gets amplified. I&#8217;ve already seen groups campaigning to get the old back. I could care less about that, by all means go and change and organically improve. Just be careful about the over-riding experience, because a site as popular as FB has a real responsibility to keep design patterns sound, so that people don&#8217;t start getting used to bad practices. FB may have more reasons than most to cram stuff into a central page, but what they&#8217;re doing is making a one-page experience as they remove more and more reasons to leave the main page. You can now comment on people&#8217;s walls straight from the home, and read comments not currently on screen with new fly-outs from the right hand column. I can imagine other sites doing the same, and how difficult they&#8217;d be to navigate.</p>
<p>And of course I can hear them now in boardrooms around the world. &#8220;Why don&#8217;t we just make that a scrolly box, and stick like four of them together in the right column&#8230;&#8221;. Like as if somehow, the page no longer scrolling has solved the old page fold debate, and instead lots of individual blocks will be scrollable. Or not.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2011/09/facebook-redesign-change/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Improving Ways to Read While Writing</title>
		<link>http://www.caperet.com/2011/03/read-while-writing/</link>
		<comments>http://www.caperet.com/2011/03/read-while-writing/#comments</comments>
		<pubDate>Tue, 08 Mar 2011 14:50:39 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=663</guid>
		<description><![CDATA[I have been doing a bit of writing lately, and might even get an article or two published in an online technical publication. Which led me to thinking about the separation between technical stuff I write, often close to my profession, and the more personal items I write at other times. There are bits of [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><a href="http://www.flickr.com/photos/bitzi/228175875/" title="flickr typewriter typo?! by bitzi ☂ ion-bogdan dumitrescu, on Flickr"><img src="http://farm1.static.flickr.com/80/228175875_f2584d61ab_m.jpg" width="240" height="180" alt="flickr typewriter typo?!" /></a></div>
<p>I have been doing a bit of writing lately, and might even get an article or two published in an online technical publication. Which led me to thinking about the separation between <a href="http://www.caperet.com/2007/09/more-on-flickr-save-or-cancel/">technical stuff</a> I write, often close to my profession, and the more <a href="http://www.caperet.com/2008/08/tonsilitis-at-the-end-of-the-hols/">personal items</a> I write at other times. There are bits of photography and music in here too.</p>
<p>Many successful blogs stick to one subject, and treat it well. Some bloggers who want to scratch several itches therefore launch several blogs. I&#8217;ve always preferred one place to do everything, especially given that I don&#8217;t create anything like a useful volume of work to really get a following going anywhere in a given niche subject. I quite like the notion of an eclectic mix, and that has been my sub-heading ever since this blog was launched.</p>
<p><span id="more-663"></span></p>
<p>I may gain from better categorisation and taxonomy (tagging) though. Good categorisation allows a visitor to find related content easily. It may also allow separate blog entry points with navigation options per category. Perhaps I should code a top navigation with a few main category entry points (tech, photography, music &#038; film&#8230;) which would allow different &#8220;views&#8221; of my blog based on different interests. I&#8217;m not exploiting that enough. Good tagging of each article creates little bridges between articles that share particular keywords. With WordPress you can assign multiple categories and tags to each article. Restricting the number of each you use makes all articles have tight interlinking which is good. Using lots of different tags and categories may cause the interlinking to be too spread out. This causes attrition on the usefulness of tag and category efforts in the first place.</p>
<p>
In this blog&#8217;s case, after several years without any tags and a few set categories, I will have to go through all the old articles and reclassify them for any new taxonomy / categorisation to really work. What do you think about mixed-up blogs? Do you ever even look at blog navigation and try to find more content that is like the article you most liked on a blog?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2011/03/read-while-writing/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Why I Won&#8217;t Read Your Blog</title>
		<link>http://www.caperet.com/2011/01/wont-read-your-blog/</link>
		<comments>http://www.caperet.com/2011/01/wont-read-your-blog/#comments</comments>
		<pubDate>Thu, 27 Jan 2011 16:59:25 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=644</guid>
		<description><![CDATA[I surf around quite a lot of blogs, thanks mainly to blog exchanges like Expose Your Blog which are like StumbleUpon but based only on blogs, and have the added bonus of gaining you reciprocal traffic. I used to surf on other exchanges too, but they are all losing traffic and are poorly maintained. Expose [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><a href="http://exposeyourblog.com/?r=58209"><img src="http://www.caperet.com/images/EYB.jpg" alt="Expose Your Blog" /></a></div>
<p>I surf around quite a lot of blogs, thanks mainly to blog exchanges like <a href="http://exposeyourblog.com/?r=58209">Expose Your Blog</a> which are like StumbleUpon but based only on blogs, and have the added bonus of gaining you reciprocal traffic. I used to surf on other exchanges too, but they are all losing traffic and are poorly maintained. Expose Your Blog is relatively new and quite a small but vibrant community of those enthusiasts of personal blogging that haven&#8217;t defected to Facebook, Twitter, Tumblr and others.</p>
<p>I thought I&#8217;d share a few reasons why I might be put off by blogs, and tune out if I land on them again. If you can think of anything else, I&#8217;d be pleased to hear it in the comments. Feel free to share your pet peeves too <img src='http://www.caperet.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p><span id="more-644"></span></p>
<p><strong>Reading:</strong> If your blog is hard to read, then why read it? </p>
<ul>
<li>Don&#8217;t use busy backgrounds that interfere with the foreground text, especially if that foreground is not separate from the background because it&#8217;s semi transparent.</li>
<li>Don&#8217;t use super-small text or change text size, colour or font mid posting. A different style for quotes, captions and other elements can work, but stick to one style per type of content and make your main text as simple and easy to read as possible.</li>
<li>Don&#8217;t make adverts obscure the key content you&#8217;re trying to push. Your blog will not make you rich, get over it.</li>
<li>Don&#8217;t have too many wacky widgets all over the place. Pick the ones that best represent your personality and stick with them if you must have a couple. Try to keep them aligned so that there aren&#8217;t loads of different widths of widget all higgledy-piggledy on the page.</li>
<li>Don&#8217;t have so much fixed content at the top of your blog that it&#8217;s not obvious where the fresh, unread content starts. This last point is particularly important on blog rotation sites because someone who&#8217;s already read your blog wants to identify what&#8217;s new since last time!</li>
<li>Do make sure there is good contrast between your foreground and background. Some people have awful screens; some people are not blessed with good eyesight.</li>
<li>If you are going to use teasers, make sure I get a good idea of the article content before I click a link to read more.</li>
</ul>
<p style="margin-top:1em;"><strong>Writing:</strong> that&#8217;s what your visitors are here for.</p>
<ul>
<li>Don&#8217;t apologise for the lack of posts, or make promises you might not keep like posting more often soon. It will only look worse as the most recent posting date recedes into the past.</li>
<li>Do set a reasonable rhythm of posting and stick to it. No point being one post a day for a while then nothing for ages. Better to set a reasonable goal for yourself and stick to it. I try to make an update about every ten days, I can&#8217;t manage more. If I have a great idea for a post a couple of days in a row, I store them up as writing prompts for the next post.</li>
<li>Commenters: they might want to write too. Don&#8217;t make life difficult for them by requiring them to have a specific website ID like Blogger or OpenID. Let them post anonymously, using either a CAPTCHA or moderation to stop spam. I&#8217;ve actually typed nice comments to people only to find that I can&#8217;t post them anonymously. The nice comment is thus wasted, and my time with it. Yes, I have a Google account but I don&#8217;t want it all over the blogosphere.</li>
<li>Crazy punctuation, over-use of quotes, lots of exclamation and question marks. Tough one this, because some people can do it and it totally fits in with their character and works. Other times it just looks like filler and detracts from an otherwise interesting read.</li>
</ul>
<p  style="margin-top:1em;">I edit myself a lot and try to be as good as possible, but obviously I am guilty of some of these crimes. I&#8217;m happy to hear your suggestions if you have constructive criticism of this blog.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2011/01/wont-read-your-blog/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Installed W3 Total Cache</title>
		<link>http://www.caperet.com/2010/10/installed-w3-total-cache/</link>
		<comments>http://www.caperet.com/2010/10/installed-w3-total-cache/#comments</comments>
		<pubDate>Tue, 26 Oct 2010 15:39:28 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=586</guid>
		<description><![CDATA[I have added a new plugin, W3 Total Cache, to improve performance on this blog. It seemed that pages were taking a bit too long to load according to Google webmaster tools. Solutions for caching nearly always make a difference, but you have to be careful about the parameters you set. However, with minimal adjustment [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><img src="/images/perf.png" alt="" title="W3 Total Cache" /></div>
<p>I have added a new plugin, <a href="http://wordpress.org/extend/plugins/w3-total-cache/">W3 Total Cache</a>, to improve performance on this blog. It seemed that pages were taking a bit too long to load according to Google webmaster tools. Solutions for caching nearly always make a difference, but you have to be careful about the parameters you set. However, with minimal adjustment to the defaults on this plugin, I now have a working configuration. There are plenty of options as you can see with the whole new &#8220;performance&#8221; panel in my WordPress admin screen.</p>
<p>Slow loading pages can really turn visitors off. Most surfers have a very low attention span &#8211; until they&#8217;re captivated by something of course. Improvements in page loading speed have been shown to improve user engagement and site traffic on sites as diverse as Amazon, Google and travel websites. Blogs are probably not as important, but that only means that tolerances are wider. Just because everyone has higher speed internet access, doesn&#8217;t mean they want to wait any more than a second for a page to start displaying. I&#8217;ve seen a few blogs on rotation that are a bit slower than that. Make sure your blog loads progressively if you can&#8217;t reduce overall page elements easily.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2010/10/installed-w3-total-cache/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Troubleshooting WordPress Canonical</title>
		<link>http://www.caperet.com/2010/09/a-wordpress-canonical-problem/</link>
		<comments>http://www.caperet.com/2010/09/a-wordpress-canonical-problem/#comments</comments>
		<pubDate>Wed, 29 Sep 2010 19:53:19 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.caperet.com/2010/09/a-wordpress-canonical-problem/</guid>
		<description><![CDATA[I have been wondering for a while why my jokes pages don&#8217;t list in search engines. They are WordPress pages which have some PHP in them to read from a separate database table containing my jokes. Every now and then I&#8217;ve tried to fix the problem, and I think I&#8217;ve finally found the issue. I&#8217;d [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><a href="http://www.flickr.com/photos/danardvincente/2512148775/" title="photo sharing"><img src="http://farm3.static.flickr.com/2170/2512148775_61fa58b4b3_m.jpg" alt="" /></a></div>
<p>I have been wondering for a while why my <a href="/joke-database/">jokes pages</a> don&#8217;t list in search engines. They are WordPress pages which have some PHP in them to read from a separate database table containing my jokes. Every now and then I&#8217;ve tried to fix the problem, and I think I&#8217;ve finally found the issue. I&#8217;d like to explain how I didn&#8217;t solve the problem too, so you can see the troubleshooting steps I took.</p>
<p>First of all, I wondered if the content on the pages was too similar. I have a page that lists the categories for jokes, and for each link on that there is a page with a list of jokes in that category. I thought maybe the list of links wasn&#8217;t search engine friendly enough. So I added a bit of introductory text, and changed the &lt;title&gt; of each category list page to include the name of the category. I also added links to the next joke in the category on each joke page and changed the position of the breadcrumbs (e.g. Jokes by Category > True Stories jokes) to after the joke so the top of the page wouldn&#8217;t always contain very similar data. That didn&#8217;t work, but the pages are now a bit better to read and each joke in a category links to another joke which allows for better navigation. Perhaps people will read two or three jokes rather than being stuck in a dead end especially if they land on the site on a specific joke page.</p>
<p><span id="more-540"></span></p>
<p>Then I wondered about submitting a <a href="http://www.sitemaps.org/">sitemap</a> of the joke category pages so that Google, Yahoo and Bing would know about them.  It didn&#8217;t work either, but having a sitemap listed in Google&#8217;s webmaster tools allowed me to see that none of the category pages were actually being listed.</p>
<p>I scratched my head for a while on this one, before realising that perhaps the use of a querystring (e.g. in the URL the only thing that changes is the bit after ?CAT= or ?JOKEID=) as the only difference in URLs was a problem. I even went so far as to set up a .htaccess file to <a href="http://corz.org/serv/tricks/htaccess2.php">rewrite URLs</a> from ?JOKEID=123 to /joke/123/ where 123 would be the actual number the joke is referenced as in the database. Funnily enough, that made no difference either &#8211; and it was difficult to get it to cohabit with WordPress because there are internal rewrites within WordPress and my custom joke pages are kind of sidestepping some of that.</p>
<p>Webmaster tools in Google were still saying my pages weren&#8217;t listed. I tried another content update, going so far as to add a paragraph describing each category on the initial list page, and then re-using the category description on the pages that show jokes from only one category. This too was in vain, though the pages now look a lot more interesting. Perhaps they&#8217;re slightly busier and less easy to read but they have extra unique content which is a bonus for those two people who want to work out how I categorised the jokes.</p>
<p>Somewhere along these two last steps, I also noted that Google allow you to specify which parameters in your URL you don&#8217;t want them to ignore. It&#8217;s in a section called parameter handling &#8211; these parameters refer to the querystring I mentioned before. So I set up CAT and JOKEID not to be ignored. Still no joy.</p>
<p>In a final step, within which my eureka moment was to come, I thought that there was perhaps too much guff in the &lt;head&gt; section of my joke pages. The standard stuff that WordPress adds to each header is useful for the homepage and perhaps posts, but not for my custom pages. So I set most of it to display only on the homepage (a lot of it isn&#8217;t of enormous use elsewhere) by changing the template files to include a condition to add that data only for the homepage. When I was testing that on my jokes pages, I suddenly noticed something in the source code which made me shake my head in disbelief. How could I have missed it? There was a line in the &lt;head&gt; which said : </p>
<blockquote><p>&lt;link rel=&#8217;canonical&#8217; href=&#8217;http://www.caperet.com/joke-database/&#8217; /&gt;
</p></blockquote>
<p>WordPress automatically adds a <a href="http://www.mattcutts.com/blog/canonical-link-tag/">canonical</a> reference to all pages, so that there is one master URL which the search engines will use to index the page. This makes sense to avoid having the same page listed multiple times. Except that my custom pages all display different content depending on whether CAT or JOKEID is in the URL but WordPress was effectively saying they are all the same &#8211; to search engines. I soon found a page on how to <a href="http://www.mydigitallife.info/2010/01/24/how-to-disable-wordpress-canonical-url-or-permalink-auto-redirect/">disable canonical links</a> but I didn&#8217;t want to apply it to my whole blog, just the jokes section. Since my jokes pages are all &#8220;Pages&#8221; in WordPress and not &#8220;Posts&#8221;, I added the code at the top of my Page template, and was pleased to note that it works just fine there.</p>
<p>So now my jokes pages should, next time they are crawled, finally all be listed. All that work so that a few people each month might find a joke in my database. At least I&#8217;ve learned something, and perhaps given you an idea of how I&#8217;ve troubleshooted this issue.</p>
<p>[ED] The pages were finally listed in Google on the 19th October, about <em>3 weeks after</em> the initial modifications.</p>
<p><small>Image: <a href="http://www.flickr.com/photos/danardvincente/2512148775/">Search-Engine-Marketing</a><br />
Originally uploaded by <a href="http://www.flickr.com/people/danardvincente/">Danard Vincente</a></small></p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2010/09/a-wordpress-canonical-problem/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Five Years, Still Here</title>
		<link>http://www.caperet.com/2010/08/five-years-still-here/</link>
		<comments>http://www.caperet.com/2010/08/five-years-still-here/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 14:52:24 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=441</guid>
		<description><![CDATA[The first proper post on this blog, discounting some emails about the Tour de France fantasy game which I converted to blog format, was Reading For Free back in late July 2005. I started the blog on WordPress and am still running it (back then it was version 1.2 and then 1.5). I created my [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><img src="/images/adminthumb.gif" alt="Thumbnail of old WordPress CMS back office look" /></div>
<p>The first proper post on this blog, discounting some emails about the Tour de France fantasy game which I converted to blog format, was <a href="/2005/07/reading-for-free/">Reading For Free</a> back in late July 2005. I started the blog on WordPress and am still running it (back then it was version 1.2 and then 1.5). I created my <a href="/2005/09/burnt-orange/">own theme</a> in September with help from <a href="http://urbangiraffe.com/2005/04/12/themeguide1/2/">Urban Giraffe</a> and have modified it a bit since then, adding widget support (very late on that one, but didn&#8217;t need it before), <a href="/2009/05/bringing-it-all-together/">tweets in the sidebar</a>, and most recently a <a href="/2010/07/mobile-version-now-live/">mobile version</a>.</p>
<p>I have just upgraded to the latest version (3.1). The dashboard and back office looks cleaner, and has come a long way from the way it used to look. Sadly my post frequency average is only about 2 posts a month, which means my audience is still very limited. If you can&#8217;t post at least once a day, you&#8217;ll never build up readership &#8211; though once you have your readers, you might be able to diversify and post regularly but not necessarily to the same blog. I&#8217;ve spent five years hoping I could find more time to say more, still hoping.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2010/08/five-years-still-here/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bringing it all Together</title>
		<link>http://www.caperet.com/2009/05/bringing-it-all-together/</link>
		<comments>http://www.caperet.com/2009/05/bringing-it-all-together/#comments</comments>
		<pubDate>Sat, 23 May 2009 13:10:59 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=228</guid>
		<description><![CDATA[On Facebook, you have a status which is limited to something along the lines of 140 characters, rather like a tweet in Twitter, which has a similar character limit. I often update this with a link, a story I have read in the press, or a mundane observation about how awful the weather is lately. [...]]]></description>
			<content:encoded><![CDATA[<div class="myimage"><img src="/images/web2_twitter.png" alt="Twitter + Facebook + Netvibes = fruey 2009" /></div>
<p>On Facebook, you have a status which is limited to something along the lines of 140 characters, rather like a tweet in Twitter, which has a similar character limit. I often update this with a link, a story I have read in the press, or a mundane observation about how awful the weather is lately. Having already linked Facebook and Twitter with the official <a href="http://apps.facebook.com/twitter/">Twitter Facebook app</a>, anything I post to Twitter (a &#8220;tweet&#8221;) is now published to my Facebook status and will also appear in the sidebar of this blog.</p>
<p>I spend most of my spare minutes on <a href="http://www.netvibes.com">Netvibes</a> and <a href="http://www.facebook.com">Facebook</a> these days. Netvibes allows me to follow &#8211; in one place &#8211; the news (The Guardian, BBC News, New Scientist&#8230;), Geek sites (Slashdot, Metafilter&#8230;), French bloggers (Fred Cavazza, Stratégie Interactive&#8230;), podcasts (Guardian Science Weekly, BBC Material World), comments on my stuff (Flickr, Twitter, this blog&#8230;) and my own work projects (Basecamp RSS feed). From a total of 44 feeds loaded on there I may go off to different sites, or spot posts in blogs that I otherwise would never have the time to visit. Facebook allows me to keep in touch with friends &#8211; at least those that actualy use Facebook to publish and share things &#8211; and its value is in the ease with which you can react to news by commenting on things whether they be status updates, photos, videos or posted links.</p>
<p>While surfing around I used to find more time to post fully here, perhaps with an article on <a href="http://www.caperet.com/2007/09/29/more-on-flickr-save-or-cancel/">Flickr</a> or something I had heard on <a href="http://www.caperet.com/2008/10/14/the-latest-in-conversational-artificial-intelligence/">a podcast</a>. That being said it&#8217;s not like blog posts have ever come thick and fast.</p>
<p>So I&#8217;ve decided to activate a weekly tweet digest, which means there should be something going on here most weeks. Visitors may have noticed that updates have dried up in 2009, mainly because it&#8217;s just so hard to find time to write a good article. There&#8217;s <a href="http://www.caperet.com/2006/03/20/once-a-dream-now-ubiquitous/">stuff</a> <a href="http://www.caperet.com/2005/12/08/manhattan-25-years-ago/">worth</a> <a href="http://www.caperet.com/2007/02/12/bringing-up-bilingual/">reading</a> in the archives though, but it doesn&#8217;t always get the exposure it should. So now by combining the blog with the latest internet fads, I should be able to keep things up to date a bit more often just by having Twitter radiate out my comments to all the places people catch up with me <img src='http://www.caperet.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> . </p>
<p><small>p.s. Sorry for the awful diagram.</small></p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2009/05/bringing-it-all-together/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Follow the Twitter Feed</title>
		<link>http://www.caperet.com/2009/05/follow-the-twitter-feed/</link>
		<comments>http://www.caperet.com/2009/05/follow-the-twitter-feed/#comments</comments>
		<pubDate>Fri, 22 May 2009 11:05:19 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=224</guid>
		<description><![CDATA[Lately, I have been mostly microblogging via Twitter. It updates my blog (see the sidebar on the right), my Twitter followers (all two of them) and my Facebook status. Having changed job recently I have precious little free time to write full blog articles. I&#8217;m thinking about directly adding my tweets to the blog as [...]]]></description>
			<content:encoded><![CDATA[<p>Lately, I have been mostly microblogging via <a href="http://www.twitter.com">Twitter</a>. It updates my blog (see the sidebar on the right), my Twitter followers (all two of them) and my Facebook status. Having changed job recently I have precious little free time to write full blog articles.</p>
<p>I&#8217;m thinking about directly adding my tweets to the blog as articles &#8211; it may make more sense that way as updates will be more regular. Happy to hear your thoughts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2009/05/follow-the-twitter-feed/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Recent Upgrade</title>
		<link>http://www.caperet.com/2008/10/recent-upgrade/</link>
		<comments>http://www.caperet.com/2008/10/recent-upgrade/#comments</comments>
		<pubDate>Sun, 05 Oct 2008 15:32:28 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>
		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.caperet.com/?p=165</guid>
		<description><![CDATA[I have just updated to the latest version of WordPress which is the software that runs this blog. If anything is strange, let me know.]]></description>
			<content:encoded><![CDATA[<p>I have just updated to the latest version of <a href="http://wordpress.org">WordPress</a> which is the software that runs this blog. If anything is strange, let me know.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2008/10/recent-upgrade/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spam Avalanche</title>
		<link>http://www.caperet.com/2006/08/comments-closed-on-older-posts-as-spam-increases/</link>
		<comments>http://www.caperet.com/2006/08/comments-closed-on-older-posts-as-spam-increases/#comments</comments>
		<pubDate>Tue, 29 Aug 2006 06:57:06 +0000</pubDate>
		<dc:creator>fruey</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[general]]></category>

		<guid isPermaLink="false">http://www.caperet.com/2006/08/29/comments-closed-on-older-posts-as-spam-increases/</guid>
		<description><![CDATA[I&#8217;ve been away on holiday. On my return I had over 1,000 messages waiting, most of which were blog spam. I spent a considerable amount of time cleaning all that up. So I&#8217;ve now taken steps to reduce spam on this blog by closing comments on posts older than 21 days. Back soon with photos [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been away on holiday. On my return I had over 1,000 messages waiting, most of which were blog spam. I spent a considerable amount of time cleaning all that up. So I&#8217;ve now taken steps to reduce spam on this blog by closing comments on posts older than 21 days.</p>
<p>Back soon with photos of the holiday.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.caperet.com/2006/08/comments-closed-on-older-posts-as-spam-increases/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

