My Google Reader replacement

Veröffentlicht am 26.9.2013, 14:48 Uhr

After Google closed their RSS reader I of course was looking for a web based replacement for it. Wanting more a  „river of news“ than Pinterest or „Let us decide what you want to read“, the search actually got quite complicated – many of the new reader replacements popping up didn’t match my requirements, and even if they looked like they did, most of the time they were broken or not really thought through.

A more structured list of my requirements:

I used ReplaceReader, Russel Beattie’s Readerpocalypse-the-Players-article, this epic list and some Google searches to find the following list of replacements:

Feedly, free

Very feature complete. Sometimes strange UX, quite often doesn’t really save read progress. But has an API that is supported by the biggest iOS readers.

TheOldReader, free

Matches the old Google Reader very closely. Didn’t scale well in the first days after the shutdown, actually seems to closely related to Google Reader to innovate.

Aol Reader, free

Big company, good designers. Makes a great rss reader with a perfect design. Shame they needed sooooo looooong to offer users to reorganize their imported feeds. Small feature, big frustration if it’s missing.

Digg Reader, free

See what I wrote about Aol Reader.

Newsblur, limited free, $2/month, $24/year

Oldie but a goodie. Works great, but I don’t like parts of the interface.

Feedbin, $3/month, $30/year

Ben Ubois created one of the newer Google Reader alternatives, and he did a pretty good job. I really like the general style of the product, but really dislike the user of tags instead of folders and the missing ‚complete articles river‘ view.

Yoleo, free (or $9/year donation)

„the beautiful reader“ is it’s tagline, and Jamie Gilgen did a really good job at that. Unfortunately, she also made some very strange decisions and the river of articles, or „waterfall“ as she calls it, is still missing.

Curata Reader, free

„The Cleanest Reader“. Yup, but also missing lots of the functionality I want.

Feedspot, free, $3/month, $24/year

Again, most of the stuff of Google Reader (and more) works and looks pretty decent.

Commafeed, free

„Bloat-free feed reader“. Support the most important stuff, but is also quite slow.

Hive, free

„Content first, no distractions“

Bloglovin, free

Works, pretty, but also not flexible enough. Very Pinterest/fashion oriented.

kouio, free

Prettyyyyyy. But no river view and not really made for lots of folders.


More great readers, but didn’t really bring anything new to the table beside variations in design and which features were or were not supported:

Tiny Tiny RSS

Because it actually looks good I also decided to include this self hosted reader.

So which one did I choose? Feedly. It just worked when all the others had scaling problems and it supports all the features I need. It’s not perfect, but now I’m used to it.

Wikipedia Mobile #1

Veröffentlicht am 8.4.2012, 02:00 Uhr

This morning I accidentally installed Wikipedia’s mobile app on my iPad. It felt sluggish, strange and not at all what I expected. As bitching doesn’t help and I wanted to use my professional knowledge in my free time, I started poking around. This is the result.

Starting position

The iOS Wikipedia app has really bad ratings. Users complain about bad performance, bad usability and about the feeling that this is more an Android app but an iOS app. In sum, this creates you a rating of only 2 stars for the current version. Ouch.

Android users seem to be happier with their 4.5 star rating. The problems only exists with the iOS version of the (similar) app. Strange. Let’s start with the basics and look into the feature set:

Doesn’t sound too bad. It’s not only stuff a mobile web site could do, so an app makes sense. So lets start to investigate.

What’s the background of all that?

The AppStore description of the app also links to a Twitter account and the source code of the app on Github:

From these two links I basically spent hours reading, clicking, reading again – typical procrastination stuff (Procrastinators beware if you are even near Wikipedia articles…). But I learned a lot ;) Back to topic: The following links all are relevant to the mobile efforts of Wikipedia:

While reading these pages, I noticed information about two different iOS apps: One is based on Rhodes, one on Phonegap. It turns out the Phonegap version for iOS is quite new and the old one is to be retired and phased out:

So we have several projects and initiatives in the mobile space of Wikipedia:

Not too bad. Of course the articles in the wiki are quite… organically grown and sometimes hard to differentiate and classify. But I think that’s the case most of the time when volunteers and professionals work together.

The funny stuff: code

Now I have an overview, so let’s get back to the funny stuff: code.

As I have never used git before, I spend some time installing all the tools and learning how to use them. After that I can finally checkout the repository on Github. While I do this, I notice that the isn’t as pretty as all the readmes of the other Github projects I know. So that’s the first thing I decide to fix. 1 hours, lots of reading and 3 minutes of ‚coding‘ and a pull request later, it is done. My commit gets integrated by reedy a few minutes later. I’m in.

But now to the real code. The folder structure of the repository isn’t very clear. There are lot’s of confusing files in the root that don’t really belong there in a multi platform project, several folders that also don’t make sense to me or I can’t identify. Again, this seems to have grown over time. This is definitely something that could and should be fixed.

In /assets/www I find something that looks like the html application. Loooots of Javascript, jQuery and Zepto *confused. Anyway, using –disable-web-security I can open the Phonegap app in Chrome and even get it working! Still, several ‚file not found‘ as non-existant files are requested. But here it becomes quite clear, that the app itself is no bad in itself. It works, the code is more or less structured, you can see what the developer was thinking. Normally that’s a good thing. So as to not fish around without all information, I conclude my little poking session for today.


After getting this short glimpse into Wikipedia Mobile I think that the code isn’t the first problem to fix. First it needs some love in the Documentation and Organization of the code. So that’s where I will start. Let’s see what I can do.

PS: Well, I installed the app on my old iPod 3 (iOS 4.2.1) and tried to use it – completely unuseable. Maybe we should start with the code after all.

iPhone-Apps analysieren

Veröffentlicht am 6.4.2012, 22:55 Uhr

Heute habe ich ein paar iPhone-Apps auseinander genommen und sowohl Funktionsweise als auch Datenverkehr näher angeschaut.


Dateien auslesen

(Binary) Plist Dateien anzeigen


SQLite Datenbanken anschauen

Web-Traffic nachvollziehen

  2. iPhone und Rechner in selbes WLAN
  3. Rechner-IP:8888 als Proxy der WLAN-Verbindung im iPhone einrichten
  4. Session capturen

SSL-Web-Traffic nachvollziehen

  1. Proxy -> Proxy Settings -> SSL -> Enable SSL Proxying
  2. Locations mit den entsprechenden Domaisn füllen
  3. Help -> Install Charles CA SSL Certificate -> Details -> In Datei kopieren -> Per Mail an iPhone senden und installieren

Vorsicht, besser nicht zu sehr bei der Installation von Apps benutzen, ich war heute 2 Stunden vom AppStore ausgeschlossen ;)

Mit dem Setup kommt man schon recht weit und kann doch so einiges lernen.

Wireshark: Copy content of compressed requests

Veröffentlicht am 7.3.2012, 17:40 Uhr

Copying the content of a request compressed by using gzip is not easy in Wireshark:

  1. Click the request you want the content from
  2. In the Middle panel, click „Packet Details“
  3. Collapse all branches
  4. Right click on last Branch (Could be „Line-based text data: text/html“ or „Media Type“)
  5. Click „Copy“
  6. Click „Bytes (Printable Text Only)“

Now you have the content in your clipboard and paste it where you want.

Fix ugly fonts in Firefox 5

Veröffentlicht am 27.6.2011, 09:40 Uhr

  1. about:config
  2. gfx.direct2d.disabled auf true setzen

Secure XAMPP: only local connections

Veröffentlicht am 25.3.2011, 12:23 Uhr

1) Open file xampp\apache\conf\httpd.conf and replace

Listen 80



2) Open file xampp\apache\conf\extra\httpd-ssl.conf and replace

Listen 443



3) Open file xampp\mysql\bin\my.cnf|.ini and put in


directly after [mysqld] (NOT [mysql]!)

Dual-boot a hackintosh with Windows 7

Veröffentlicht am 7.7.2010, 10:26 Uhr

Pin Freemind to the taskbar in Windows7

Veröffentlicht am 8.4.2010, 09:55 Uhr

The normal Freemind shortcut goes directly to Freemind.exe, but as the execution takes place in Java you can’t pin this shortcut to the taskbar in Windows 7. Another icon will appear with the same icon. If you try to pin this icon, Freemind won’t start or the icon will change to the generic Java icon.

The solution to the problem is to change the target of the shortcut from […]/Freemind.exe to this:
"C:\Program Files\Java\jre6\bin\javaw.exe" -jar lib/freemind.jar
Now you can pin the program to the taskbar in Win7 and use it as every other program.

And yes, this tip works with almost all Java programs that are delivered with working .jar files.

Programming is hard

Veröffentlicht am 16.1.2010, 19:10 Uhr

MySQL: Delete a subset in a table quickly

Veröffentlicht am 21.6.2009, 14:04 Uhr

Heute mal wieder über einen netten MySQL-Hack gestolpert:

The trick is, that INNER JOIN will ’shrink‘ the LargeTable down to the size of the TemporarySmallTable and the delete will operate on that smaller set only, since USING will reference to the joined table.

Mehr davon bitte…

Fatal error: Uncaught Error: Call to undefined function wp_ftr_googlestats() in /www/htdocs/w012bf20/ Stack trace: #0 /www/htdocs/w012bf20/ require_once() #1 /www/htdocs/w012bf20/ load_template('/www/htdocs/w01...', true) #2 /www/htdocs/w012bf20/ locate_template(Array, true) #3 /www/htdocs/w012bf20/ get_footer() #4 /www/htdocs/w012bf20/ include('/www/htdocs/w01...') #5 /www/htdocs/w012bf20/ require_once('/www/htdocs/w01...') #6 /www/htdocs/w012bf20/ require('/www/htdocs/w01...') #7 {main} thrown in /www/htdocs/w012bf20/ on line 19