This is a great idea for a module, and I'm interested in how it could be extended to truly be a "lifestream" like on the http://www.yongfook.com/ example.

From my limited testing, this looks like it is a simple interface to add tumblr output that you could add with the tumblr embed code or an rss feed. However, the concept behind it is solid with a ton of potential.

Can this take other types of json or rss data?

I'm imagining a system that would let users add content from all types of accounts, flickr, youtube, facebook, etc. A user would go to the settings page and simply enter their username for each service and suddenly have a "lifestream" showing latest videos, status updates, tumblr content (separated as text, video, image, etc.), flickr photos, etc.

Does this sound like the direction you are hoping to go with this? Or is there a better way to do it via feedapi? I'm interested in discussing more. Great work.

Comments

nickgs’s picture

nickgs commented

Your vision aligns directly with what I am thinking for this module!

Right now I am just simply taking json data from tumblr and outputting it. I would like to systematically introduce new data streams from other services that we all love to use and truly make this a lifestream of user activity across the Internet.

Thanks!

jasonwhat’s picture

jasonwhat commented

How do I help you move this forward? I think this is a great concept. I'm also interested in how other existing modules like "planet" and "feed api" might help.

I'm also playing around with an implementation of this using yahoo pipes. Many pipes already exist that simply need a user variable passed to them to fetch the data from say flickr or youtube. This may be a good route because pipe does all the hard work.

nickgs’s picture

nickgs commented

Excellent. The past couple of days I have not been able to devote that much time to this project. I do plan of spending some time this weekend to get some more code checked in. If you would like if you have a CVS account I can grant you access to check in code.

I must admit I am not very familiar with using CVS just yet. I still have to get a HEAD branch going here.

jasonwhat’s picture

jasonwhat commented

I'm afraid I'm not much help on the code side, but happy to contribute with documentation. I'm also interested in discussing further what the implementation will look like and how it is best done. For example, how will content be presented? Will the module come with a css file and a "lifestream" page for each user? Could views or panels be used to have custom displays?

Also, short of having all content become persistent nodes (or semi-nodes that are automatically deleted if no action is taken to save them, like is often done with RSS import modules) maybe each stream could be a node to allow some flexibility. i.e. A user who logs in and configures their lifestream with a facebook account (status updates -- maybe pics or more since fb allows that), a youtube account, and a tumblr account, would have a "facebook account node," a youtube one, and a tumblr one. These 3 nodes would be tied to the user, but they would each individually load the data. Also, this would allow admin to create views of all user videos, or all images from users. Display of lifestreams could be customized via views, panels, and arguments.

asak’s picture

asak commented

sub.

and will say something a bit later...

nickgs’s picture

nickgs commented
Status: Active » Closed (fixed)