Wednesday, August 27, 2014

Feedly vs Inoreader, my thoughts (part 1)

Note: This is Part 1 in my humble series, as I agonize over whether to commit to Feedly or Inoreader as my RSS reader of choice. See Part 2Part 3Part 4, and Part 5 if you're interested. 

When Google Reader died, I was heartbroken. Luckily, like a rebound lover, Feedly was there to pick up the pieces and make me feel all warm and safe. However, as time has gone on, Feedly has started to seem to lose interest in me, pushing me into the arms of another lover: Inoreader.

Basically it comes down to one key point: each RSS reader's treatment of "small time" feeds. What I mean are those feeds that are maybe not updated very often, such as once a month or once every two months, and those feeds with very few subscribers (including, but not limited to, feeds for which I might be the sole subscriber).

Examples of what I mean include:
  • Reddit subreddits that have just a few new posts each month
  • Blogger and Wordpress comment feeds (subscribing via RSS to new comments on specific posts)
  • Sourceforge application update feeds
  • Craigslist search results feeds
  • Blogs of some personal friends
I first started noticing that Feedly was dropping these feeds when I'd get curious about some sites, sites that I knew had updated, not showing up in my Feedly. Visiting the feed from within Feedly indicated no new material, even after manual refreshing. Yet a quick visit to the feed URL itself confirmed my fears: the feed was updated, and nearly a month ago, with two new items. Feedly totally missed them. Had I relied purely on Feedly to deliver my news, I would never have seen them. That, to me, is a big problem.

Putting them to the test: Inoreader on top

So I've tried out Inoreader for the last two weeks. Basically, I pared down my subscribed feeds, cleared them all out, then started fresh on both services by importing the same OPML file into both, and watching the results.

After two weeks of this, it became clear: many of my "smaller" feeds were being ignored by Feedly. One or two had "feed issues" (the Reddit feeds) according to Inoreader's informative subscription management pane, but were nonetheless being fetched by Inoreader.

Here you can see the relative fetching speed of each service. I erased all my subscriptions, loaded a fresh OPML subscription list (a smaller one than I usually use, just 20 feeds) into each service, then waited two hours. Here was the result:



You can see that Inoreader did a better job of feed fetching.

Some thoughts about both: Feedly's revenge

This may seem that I am overwhelmingly in favor of Inoreader, but that's not exactly true. I'm still a bit on the fence, and here's why:
  1. Feedly, for better or worse, seems the dominant player in RSS feed readers, which is a small enough field not to permit too many competitors. Most Google Reader refugees originally fled to Feedly. This may change in the future (Inoreader seems right on its tail, which to me suggests that others are migrating as well), but for now I'm still hesitant to leave behind the large and potentially more stable Feedly in favor of yet another newer reader.
  2. Feedly is more beautiful. This may not be an important factor for some, but I personally find Feedly to be the more "readable" of the two. It feels a little more slick, a little more polished, a little more concerned with appearances. And to me, as someone who reads hundreds of feeds a day, that matters. Inoreader is not ugly by any means. It's really just a personal preference. The font, the transitions, the design, seems smoother, especially in the Android app, on Feedly than Inoreader. This may change when Inoreader's update comes out.
Additionally, although this should be unnecessary, there are a few things I've done to improve the performance of Feedly:
  1. Feedburner. Going through my subscription list, I discovered many blogs for which I was subscribed to the blog's own RSS feed (like but that the blog also has a Feedburner feed. Switching my subscription to the Feedburner feed improved Feedly's performance in fetching articles, especially infrequently-updated blogs.
  2. IFTTT. For feeds that are rarely updates or unique to me, I've found that IFTTT's "feed" channel is equal to Inoreader at fetching articles from sources quickly and accurately. Thus I've just created IFTTT recipes for those problematic few feeds, so I now have new posts e-mailed to me. This has the fringe benefit of drawing more attention to these infrequently-appearing posts, which I might have inadvertently scrolled past in an RSS reader.

Final thoughts

After all this, I find myself leaning towards Feedly still. I've been with them since Google Reader, and feel willing to give them one more shot. Of course, until I'm more confident about the quality of their service, there's no way I'm buying a pro plan, even if I'd like to. Too risky to invest in a service I might soon see a need to flee from. Maybe they can change their ways, or maybe I'm going back to an abusive relationship and will long to get out again soon and into the sexy seductive arms of Inoreader. Either way, it's great that both of these services allow import/export of your OPML reading list, so that moving between them is fairly painless (unless you have a lot of tagged, saved articles you also want migrated, in which only Inoreader supports it.)

Expect a follow-up post in a few months.

UPDATE 2014-11-06: And the follow-up post is complete. For more of my comparisons, see this series Part 2Part 3, Part 4, and Part 5 if you're interested. 
Read more ...

Displaying your Blogger posts' location tag on mobile templates other than "Dynamic Views"

Vanishing Location Information on Mobile

I'm a big fan of tagging my Location on Blogger posts, especially on my travel blog, where I review restaurants, document my trips with tips for other travellers, etc. Blogger adds your location tag to the post in the post footer by default, which is great, but more and more people are browsing blogs on their mobile phones rather than the desktop.

As it stands, it seems if your Blogger blog is using the "Dynamic Views" template, the post's location information will be shown on both the desktop and the mobile view, including the address being a clickable link to a Google Map.

But I recently noticed that this is not the case for any other template. I tested out Blogger's other templates (Simple, Picture Window, Awesome Inc, Watermark, Ethereal, Travel, all of them!) and noticed that the location tag is not included when using these templates on mobile.

Here's a demonstration. Here's a test post I made, location tagged at beautiful Bass Lake. These are screen-shots from my phone. Notice the location info displayed here in "Dynamic Views" layout:

Great, I like that a lot. But what if I'm not a fan of Dynamic Views, for one because it takes longer to load?

Here's the same post, with the blog template switched to "Simple":

As you can see, the location information is gone. How can we get it back?

A possible solution?

This can be fixed by adding a short bit of code to your blog's template, telling it to display the location on mobile. However, in my tests, this method only works:
  • on SOME templates ("Simple" but not "Awesome Inc" for example) and
  • seems to only work on blogs that do not use Google+ integration (i.e. still use the old Blogger profile)
Update: I heard from others that this does work on all templates, so give it a try!

Anyway, to try this, edit your blog's template HTML by going to (duh) Template -> Edit HTML.

*** First make a back-up of your blog's template, just in case something goes wrong ***

Now, in the HTML editor, you need to find this tag:
<b:includable id='mobile-post' var='post'>
This will contain the code for how your blog is displayed on mobile devices. You may or may not need to click the little arrow on the side to expand this entry.

Now all you have to do is add this bit of code to the spot where you want the Location displayed. For example, I like having mine displayed in the post footer, so I search for this (it was about 50 lines of code down from the 'mobile-post' tag in mine):
<div class='post-footer-line post-footer-line-1'>
Now then, right below this line, add in the special location-displaying code:
<span class='post-location'>
<b:if cond='data:top.showLocation'> <b:if cond='data:post.location'>
<data:postLocationLabel/> <a expr:href='data:post.location.mapsUrl' target='_blank'><></a> </b:if> </b:if> </span>
And that's it! Now I save the template, and when I refresh my blog post, I see this:

The location details are back! Success!

Helpful Notes

If, like me, you are not a coder in any way at all, please take note: your blog HTML template is going to have multiple entries of the kind <div class='post-footer>. I won't even pretend to know what each of them does or why they all exist. All I can tell you is that this will only work if you put it in the section under that <id='mobile-post' var='post>' tag from above.

Also, as I mentioned above, I've had limited success, depending on the particular blog template. I'd love to hear your experiences with this. 


Credit for the majority of this idea goes to whose blog post here gave me the code used in this trick. I appreciate his support in trying to solve this.

P.S. This post is location tagged at beautiful Napa Valley, California. If the code works, you will hopefully see this post tagged (if you're reading on mobile) as such.

Read more ...

Tuesday, August 12, 2014

Blogger Map widget, for showing geotagged blog posts on a map

This post will show you how to add a side-bar widget to your Blogger/Blogspot blog. The map will display pushpins at each of your location-tagged posts' locations. Click the pins, and a small card appears with the title, date, and a link to the post.
If you'd like the cards/pins to show the full post entries, click here for my other post.

UPDATED June 2015
You can embed the map in a page too, not just as a widget. 

Location-tagged Blogger posts

I like using Blogger, and I always geotag the posts on my travel blog using the "Location" setting in the right-hand side of the Blogger compose page.

Blogger's "Location" tag feature

Read more ...