Personally, I think that FriendFeed (and other lifestreaming services) tend to become your centralized point. With the ability to continue conversations, and in some cases comment on Disqus, Twitter or the original blog all from one location may help simplify some of the "fragmentation issues". The other side of following your "friends" and all of their feeds helps simplify some of the duplication of content issue as well. Obviously, I am a big fan of FriendFeed.
Mark "Rizzn" Hopkins
· 1 year ago
Clearly. :)
I should clarify that I don't use my own homepage as my central point to find and update conversations I like. It simply acts as a showcase for what I'm doing already on the FriendFeed site.
It would appear, though, that casual viewers of my site enjoy that type of content as much as my actual blog posts, if the traffic is any indicator, which says to me that there is something in the idea of using FriendFeed as a content creation tool as well as a discussion system.
Yves
· 1 year ago
I had a similar intention with my blog, that aggregates all my micro and blogging activities in one place: my blog. So I have everything friendfeed has, except the commenting possibilities of my micro blogging. But the intention to have it all in my own (walled) garden is only an option if you have the proper coding skills - today. For the rest of us, there's no way around friendfeed, disqus & Co.
Mark "Rizzn" Hopkins
· 1 year ago
I'm not looking to cut any of them out of the equation, really.
The content is on display at my blog, for the moment, but to join in on the conversation, but each item contains a path back to FriendFeed, and in certain cases a path back to the original item.
Markdykeman
· 1 year ago
I tend to see my FriendFeed output as being separate from my blogging output, although I do have the Wordpress FriendFeed widget on my blog that displays likes and comments.
Mark, don't you find that your FriendFeed stream suffers a bit from lack of context? For example, if Disqus comments appear, you can't automatically see the original post where they came from. Also, having Tweets appear can be one-sided, particularly if you are replying to someone else. I see that you've added in a lot of the context, though, so you're compensating pretty well. Isn't Disqus still a problem?
Mark "Rizzn" Hopkins
· 1 year ago
There is a bit of context lacking, you're right.
That's why the specific feed I chose was items only with comments on them, so that there was the context of a discussion.
I've also done a bit of custom programming to pull in the source material, in certain cases (like in a google shared item discussion, I pull the text of the share in from my shared items feed).
I haven't tackled the Twitter issue, yet, but I theorize that pulling in the discussion from the Summize API would be a decent solution for this problem.
washwords
· 1 year ago
oy. still trying to figure out just HOW to get it on my wordpress blog. I love all the power in this technology. and I hate it. ;)
thanks for the post.
AC
· 1 year ago
Thank-you SOOO much for this... I've moved my blog to WP.com and didn't know what to do with my domain (which I need for email) until now.
The only thing I did differently was substitute MyBlogLog for FriendFeed -- here's the result:
All Comments
I should clarify that I don't use my own homepage as my central point to find and update conversations I like. It simply acts as a showcase for what I'm doing already on the FriendFeed site.
It would appear, though, that casual viewers of my site enjoy that type of content as much as my actual blog posts, if the traffic is any indicator, which says to me that there is something in the idea of using FriendFeed as a content creation tool as well as a discussion system.
The content is on display at my blog, for the moment, but to join in on the conversation, but each item contains a path back to FriendFeed, and in certain cases a path back to the original item.
Mark, don't you find that your FriendFeed stream suffers a bit from lack of context? For example, if Disqus comments appear, you can't automatically see the original post where they came from. Also, having Tweets appear can be one-sided, particularly if you are replying to someone else. I see that you've added in a lot of the context, though, so you're compensating pretty well. Isn't Disqus still a problem?
That's why the specific feed I chose was items only with comments on them, so that there was the context of a discussion.
I've also done a bit of custom programming to pull in the source material, in certain cases (like in a google shared item discussion, I pull the text of the share in from my shared items feed).
I haven't tackled the Twitter issue, yet, but I theorize that pulling in the discussion from the Summize API would be a decent solution for this problem.
thanks for the post.
The only thing I did differently was substitute MyBlogLog for FriendFeed -- here's the result:
www.andrewcurrie.ca
Brilliant!