We stated that Secondbrain is working for you and that’s one of the things you’ll love about it. Now is the time to prove our statement and to move forward to developing the best content aggregation platform there ever was.
We already aggregate content from del.icio.us, digg, StumbleUpon, fave, blogger, Metaweblog, WordPress, Google Docs, MindMeister, Slideshare, Zoho, Flickr, Revver, Picasa and YouTube. Now we want to know from you what services to aggregate next.
Choose your favorite service in the poll below and we’ll start adding new services based on your preferences. Feel free to post your comments and ideas too: even comments on this blog count for the Secondbrain contest we announced at the beginning of May (Remember? You have a chance to win a MacBook Air, an xbox 360 or an iPod nano!). We reward the most active users, users like you, who help us grow and get better and better each day.
[polldaddy poll="608200"]
Vimeo, Scribd and Mento (the del.icio.us on steroids)
Cool tip, Mariusz! I’ve never heard of Mento before and god knows I am a social media enthusiast. On my way to check it out right now.
Tumblr, Tumblr, Tumblr
I suppose I do not get to vote three times.
Vimeo, Scribd, Tumblr, Blip.pl, Pownce
I should be able to add any profile page of mine which has an RSS feed. You should provide a generic means of adding anything so that I can add more obscure services such as menuism.com that’d you’d never likely build explicit support for.
@prowsej : i think you’re right. though now we’re focusing on the larger services, we want to support general feeds later. the challenge is how to parse different kinds of XML/RSS to show the content correctly.
@Bob Boynton: we like Tumbler - but one challenge with it is that many people synchronize other services to Tumbler, and we’d likely get some duplicates in our streams. I will think about how we should handle this.
I never surf the web or have a Firefox install without Diigo and its toolbar. I even forgot about del.icio.us. So if I’m going to aggregate my content somewhere, I’d like to have it.
But what I would really like is to Second Brain become what I thought it was when I first signed in to it: I then thought it would replace one piece of software I enjoyed when I used Windows, and that was The Brain - which enabled you to collect all kind of things AND to connect and organize them in ways similar to what our real brain does: it doesn’t just collect things in groups of lists, it gives meaning to them through connections to previous stuff at different levels.
That’s the reason why, even though I still keep an eye on Second Brain and how it’s evolving, I actually haven’t been using it. But I hope I will…
Ditto wast cristambor wrote — two must-have features in my view are:
[1] The ability to link content items IN ADDITION to the current organizational tools (grouping in collections, searching, and relating-by-tags). Linking creates temporally stable relationships, while searching and relating by tags creates ad hoc relationships. Both are crucial.
[2] The ability to add “notes” as a content type. This is in contrast to being able to add comments on content… a note would be a root piece of content, just as a Web page currently is.
Thanks for asking…
Jack
Excellent suggestions @cristambor and @jack - this is definitely in our product road map.
I too would like to see tumblr and generic feed import.
Lars, the argument of duplication is valid, but unless only a very few number of actors survive during the next years, duplication (or really, the possibility of it) cannot be avoided, since life stream/aggregation services pop up everywhere already. I believe SecondBrain must either ignore a huge user base, or ‘open’ up for duplication.
In my opinion, avoiding duplication must be up to the users. Current services are adding functionality all the time, making it inevitable that some of them one day offer duplicate functionality. One can’t any longer just jump on every new web application (as I’ve done myself for some time) and post everything everywhere. I post content to different services depending on both my own and the content’s context, and this works very well - as long as I avoid posting duplicates