New Google Site: Teaching with Inoreader

Given interested by others in how I'm using Inoreader, I decided that it would be more productive to collection my Inoreader-related items at a website, rather than at a blog: Teaching With Inoreader. I'm excited about this because it will give me a chance to re-acquaint myself with Google Sites, too, so that I will do a better job of helping my students as they work on their own Google Sites. So, on this page, I will keep regular updates about what I am posting at the new website that specifically pertain to my classes.

Here are the new posts as of November 23, 2014:
  • Student Blogs and Comments. This explains how I set up the blog network by subscribing to student blog post feeds and comment feeds.
  • Archiving Assignments. There are a few assignments that I want to archive after the class is over; here's how I save an assignment archive as a PDF.
  • One-Time Fetch. The lack of updates for post content is the only real problem I had with Inoreader, but I found some good work-around solutions.
  • My Rookie Mistakes. Learn from my mistakes, so you don't have to learn from your own! :-)


  1. In the wee hours of this morning, I spotted Ino's "extended Black Friday" and upgraded, which I've been planning to do anyway. I'd been on Ino as my primary Google Reader replacement (discovered by chance) but following your account of developing your own model convinced me Ino would be the best way to organize my not-a-course information network.

    Besides getting swept up (subsumed, deluged) in other projects (including a new ed advocacy blogging one), tasks (however self selected and imposed), most of the exercises / assignments just did not fit what I needed. Not to say that #ccourses has not been without its great finds and reconnectings. Bless async and archiving: I can still go back and fill in gaps.

    Although as open as any connectivist network, the instructor-add course structure suits better at this juncture than sign ups/feed submissions. Since most adjuncts don't have this habit yet, I need to start by populating a network clip (or clips) with feeds I I've already been collecting. Many don't really understand distributed networks either, although that seems to be coming along too. As you've mentioned about your own colleagues, moving out of the more familiar structured, top-down and closed does not come easy to many academics. Starting out more independent (willfully so some might say) helps.

    Since I don't always check my feed readers daily, I might have missed the Ino special. Fate smiled (again) ... surely you have Latin LOLCats for that. Now to review the Ino posts again and more closely.

  2. Oh, I am thinking it could be SO USEFUL for you, Vanessa! Being able to send stuff back out via RSS and/or the HTML clippings that you could embed in your site pages would be a way for people to get the benefit of all the curating that you do even though they don't have the time to do that themselves. I'll be documenting my Inoreader use more carefully over the break since I am even going to try to get my students to use it, and also to see if I cannot rouse up a little more interest in blogging among people at OU.
    And listen, here's something really cool: Alan Levine is putting together a panel proposal for DML with the guys from ds106, Reclaim Hosting, WithKnown... and he invited me to go along and talk about Inoreader too. If we get accepted and if I get the money to go (argh!), it will be such a great chance both to talk about Inoreader to a new audience AND to give the guys working on these other projects ideas for things that Inoreader can do which you cannot really do easily in the WordPress-based systems.

  3. Checking "Notify me" box is another thing I need to remember better.

    I've been using Ino for collecting, bundling and sharing (although Feedly is better there for FB sharing) but the more I followed what you're doing (some I did on Google Reader), the more I realized I'd have to spring for paid to do what I really wanted to. I started keeping a myself folder on G Reader just to keep track of myself. That might sound strange to some, but I know you'll understand.

    Then came the Twitter and G+ feeds (I so thought of you when I saw that one). I can hand code Twitter feeds but they keep changing their API, so I tend not to as much. I'm particularly happy about having G+ feeds. Too many more to enumerate. I wonder if the NetWorkedBlogs app would syndicate them to FB. If so, I could tag and bundle stories for different FB pages, syndicate the tag feed.

    Here's another piece of Ino usefulness (and a reason to syndicate whole posts): a while back, I inadvertently deleted a Tumblr account. The two most important blogs originated on another account, so I didn't lose those but did lose a couple I'd rather not have ~ one as a favor web archiving news aggregation emails. Just a few days ago, I saw new posts in one of the gone blogs (someone took over the vacated name), looked down the list and saw the old posts. So I checked a few others and there they were. Obviously I can't open them online. On Tumblr, gone is gone. No going back. But I can copy them to another. Joe can't have a whole blog for his group news (bcc) emails but, with tags, can have a url and a feed.

  4. YES about the Tumblr... I am scared to trust Pinterest too much, so even if the RSS feeds are screwy (I get other people's pins!), I am glad to use Inoreader as a way to back up my PInterest stuff. I saw some great Tumblrs during Connected Courses, so I need to go explore there more. It wouldn't work well for my students as a blogging platform (I need comments RSS feed), but it might be a way to publish their class project, esp. if they are doing something blog-gy in terms of their style. In fact, OH, thinking out loud here: it might really be fun for the people who are doing Portfolios and want to have their Portfolio on a platform separate from their blog.

    Anyway, so much good stuff going on! I am really (REALLY) glad that I did Connected Courses. It has been a big part of why this semester has been so incredibly satisfying, even more than usual! :-)

  5. I've been trying to get to replying for ages (weeks it looks like). Ino features are going to save me time and make the rss reader even more useful than it used to be.

    I've been making bundles for clips and consolidated feeds. Ino started with better sharing than Feedly but changed it and now Feedly's is better, especially for multiple FB pages (which I have and am more or less stuck with as being where my readership/constituency is). So I'm going to add bundle feeds to Feedly for sharing, maybe even eliminate some folders that way.

    Public FB pages make handy auto-transfer points for twitter too ~ I'll take any twofer I can get. Whenever I see George's tag about life in unremitting beta, I mentally nod but add "in everflowing rss." Love RSS = Read Smart and Share.

    I notice your clip is by tag rather than bundled folders. In Google Reader, I made a point of making tags not the same as folders. I can try both. No doubt one will be better for some and the other for others but I won't know until I try.

    1. PS Save me time but now I have to make the time to get to it ~ best in stages.

  6. Is anyone using Innoreader to integrate with Canvas somehow? I was hoping to be able to...

    1. Hi Donna, I have not used Canvas in a few years but when I tested it out, it had EXCELLENT RSS features, which would make it perfect for using with Inoreader. Since Inoreader allows you to take incoming RSS of all kinds, plus Twitter and Google+, and then send that back out again, recombined into new RSS feeds, that would work really well for Canvas. (D2L, which we use at my school, has zero RSS capabilities; there is no incoming-RSS feature built into the system as I recall there was for Canvas, and that was several years ago!)


I have limited comments to Google Accounts only (the best way to eliminate spam that I have found)... but with no word verification. If you do not have a Google account, please share your comments with me at Thank you!