Skip to content

Instantly share code, notes, and snippets.

@sent-hil

sent-hil/reason_behind_river.md Secret

Created January 27, 2013 09:51
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sent-hil/4647608 to your computer and use it in GitHub Desktop.
Save sent-hil/4647608 to your computer and use it in GitHub Desktop.
Download ZIP
The reasoning behind River
Raw
reason_behind_river.md

Activity feeds are ubiquitous on the Internet.

Nearly every site I use daily has an activity feed or something that represents a constantly changing group of infomation presented in a list like format. I first had the idea for River when I realized every activity on the web has four common properties: actor, verb, object & context. "Susie posted a commented on your photo" Here 'Susie' is the actor, 'posted' is the verb, 'photo' is the object and 'your photo' is the context. Turns out there's even a spec for it.

River brings it all together.

The golden rule is any group of related activities can be a River: your Github feed, blog's rss, HackerNews entries about Ruby. A user can then subscribe to it and receive updates on that particular River's activities only. Or they don't have to be connected at all, such as a random River. Just like Pandora allowed users to create their own ratio statios, River allows users to create their own activity streams.

TODO

  • Make Github River
  • Make RSS feed River
  • Make HackerNews Ruby river
  • Make random River
  • Link the above rivers above
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment