<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alex's Adventures on the Infobahn - rss</title><link href="https://www.bennee.com/~alex/" rel="alternate"></link><link href="https://www.bennee.com/~alex/blog/tag/rss/feed" rel="self"></link><id>https://www.bennee.com/~alex/</id><updated>2013-03-14T22:17:00+00:00</updated><subtitle>the wanderings of a supposed digital native</subtitle><entry><title>On the death of Google Reader</title><link href="https://www.bennee.com/~alex/blog/2013/03/14/on-the-death-of-google-reader/" rel="alternate"></link><published>2013-03-14T22:17:00+00:00</published><updated>2013-03-14T22:17:00+00:00</updated><author><name>alex</name></author><id>tag:www.bennee.com,2013-03-14:/~alex/blog/2013/03/14/on-the-death-of-google-reader/</id><summary type="html">&lt;p&gt;You can probably tell the sort of on-line company I keep from the deluge of noise on the social networks regarding Google's decision to shut down Reader. However we shouldn't be that surprised. In fact some companies that source content from Reader &lt;a class="reference external" href="http://blog.feedly.com/2013/03/14/google-reader/"&gt;have anticipated the need to collect content themselves …&lt;/a&gt;&lt;/p&gt;</summary><content type="html">&lt;p&gt;You can probably tell the sort of on-line company I keep from the deluge of noise on the social networks regarding Google's decision to shut down Reader. However we shouldn't be that surprised. In fact some companies that source content from Reader &lt;a class="reference external" href="http://blog.feedly.com/2013/03/14/google-reader/"&gt;have anticipated the need to collect content themselves&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I of course will have to make a decision at some point. However I'll not do it today like a lot of Reader users have. The rush to try out alternatives has over-whelmed some &lt;a class="reference external" href="https://twitter.com/samuelclay"&gt;open source based projects&lt;/a&gt; who were quietly growing organically. I don't envy those that have to suddenly gear up their back-end systems because an Internet behemoth gave us 2593 hours notice to sort out a replacement.&lt;/p&gt;
&lt;p&gt;I'm mulling over the difference between self-hosting and having someone else do it. I'm not overly worried about going for convenience if I know I can get my data back if I need to. In fact the knowledge that you can theoretically self-host might be enough. To be fair to Google their &lt;a class="reference external" href="http://www.dataliberation.org/"&gt;Data Liberation&lt;/a&gt; team made exporting all my Reader data easy.&lt;/p&gt;
&lt;p&gt;Before I make a choice I need to decide what my priorities are. Currently I subscribe to 250+ RSS feeds. Obviously I don't read every single post but I make extensive use of tags to quickly process through stuff I do need to see when I need to see it. Aside from news, blog posts, funny cat pictures I also subscribe to other data feeds like bug trackers, code repositories, and other data sources. I of course want access to all of this data at any point on one of a number of devices. This makes a web hosted solution pretty much a must. There is no point having the data on my desktop when I'm somewhere else. From my point of view I want it to be open source compatible because if the company hosting now decides it no longer wants to I'll only have to move the data and not break my work-flow.&lt;/p&gt;
&lt;p&gt;It would also be very useful if it had a public API so others can interact with the data. I don't need the solution to be all provided by one company. It's perfectly fine to have multiple 3rd parties sorting out the Android integration. I might even look to doing something to integrate it with my favourite editor (the name of which even my non-geek readers probably know by now). So far my experiment with moving all of IRC and IM into Emacs seems to be working well and should be a subject of another post.&lt;/p&gt;
&lt;p&gt;Are you a Reader user? What are your criteria for it's eventual replacement? Is RSS just a dying protocol or is the need to aggregate and sift through data becoming more important?&lt;/p&gt;
&lt;p&gt;There may well be a much better way of solving this problem around the corner. I certainly am open to persuasion. But don't take away my current preferred solution until I'm convinced I'm ready to switch ;-)&lt;/p&gt;
</content><category term="geek"></category><category term="emacs"></category><category term="floss"></category><category term="google"></category><category term="hosting"></category><category term="rss"></category></entry><entry><title>Web 2.0 apps that are worth it?</title><link href="https://www.bennee.com/~alex/blog/2006/10/18/web-2-0-apps-that-are-worth-it/" rel="alternate"></link><published>2006-10-18T14:29:00+01:00</published><updated>2006-10-18T14:29:00+01:00</updated><author><name>alex</name></author><id>tag:www.bennee.com,2006-10-18:/~alex/blog/2006/10/18/web-2-0-apps-that-are-worth-it/</id><summary type="html">&lt;p&gt;Web 2.0 is a lovely little marketing buzzword that is bandied about a lot. It refers to the concept of applications running on your web browser. It used to be that people thought Java apps would be what everyone would want but it turns out that &lt;a class="reference external" href="http://en.wikipedia.org/wiki/Ajax_%28programming%29"&gt;AJAX&lt;/a&gt; can provide …&lt;/p&gt;</summary><content type="html">&lt;p&gt;Web 2.0 is a lovely little marketing buzzword that is bandied about a lot. It refers to the concept of applications running on your web browser. It used to be that people thought Java apps would be what everyone would want but it turns out that &lt;a class="reference external" href="http://en.wikipedia.org/wiki/Ajax_%28programming%29"&gt;AJAX&lt;/a&gt; can provide you with quite a powerful application experience.&lt;/p&gt;
&lt;p&gt;The one I've been playing with quite a bit over the last few days is Google's &lt;a class="reference external" href="http://www.google.com/reader/view/"&gt;RSS Reader&lt;/a&gt;. RSS readers are an exercise in saving the time poor from too many clicks. I used to use &lt;a class="reference external" href="http://liferea.sourceforge.net/"&gt;Liferea&lt;/a&gt; and then when that stalled I started using the Fixefox extension &lt;a class="reference external" href="http://sage.mozdev.org/"&gt;Sage&lt;/a&gt;. However I've finally come across a web application that is truly comfortable to use.&lt;/p&gt;
&lt;p&gt;It seems a natural fit of course. RSS is a product of the web - why would you want to leave your web-browser to read stuff? Much as I find the Live Bookmark capability of Firefox useful it doesn't give the status view of what is new. However Google Reader allows you to set up &lt;a class="reference external" href="http://www.google.com/reader/shared/04449031981434496650"&gt;aggregate feeds&lt;/a&gt; really easily which are an ideal compliment of Firefox's live feed view. The natural integration of feeds into the web environment is one of the key selling points of the reader for me.&lt;/p&gt;
&lt;p&gt;Another thing which is very well done is the keyboard shortcuts. I've not seen them used so widely in a web application before. I'm definitely a keyboard person. Compared to navigating with a mouse it's far more efficient to use a couple of well placed keys. On Reader they have made the process of browsing through articles pretty painless. Switching between feed &amp;quot;tags&amp;quot; is a simple 2+n key sequence which auto-completes to the best fit tag within 2 or 3 keys. &amp;quot;Staring&amp;quot; and sharing items are similarly easy operations.&lt;/p&gt;
&lt;p&gt;The one big bonus of all of this of course is that it's independent of which machine I'm on. I can pick up from were I left of if I'm on the laptop, desktop or work machine. For this reason Google's Reader picks up the first Bennee award for a truly use-able web application.&lt;/p&gt;
</content><category term="geek"></category><category term="google"></category><category term="rss"></category><category term="web2.0"></category><category term="webapps"></category></entry></feed>