I don't know what you have going on here exactly, but I think I like it.
So, I have been playing around with newsblur. I think it could be really usefull here. It has an API, and all that is missing is a people you follow section.What if we started to pool friends lists in one place, here and then find the intersection.Then if you let people designate there news shared items feed. It could be google plus, or posterous or hea.pe, it just needs to be a feed.From there you could do two things either then export an OPML file with all of your friends feeds, or using something like the. Newsblur API create the group o behalf of the user.
The nice thing about NewsBlur is that you can get the source code for
from github [1] and run your own server. So, if it ever goes away, the
software is still available.
That, and he charges money for a premium account, so that makes me think
I'd be more of a customer than for Google :)
[1]: https://github.com/samuelclay/NewsBlur
--
m...@lmorchard.com
http://decafbad.com
{web,mad,computer} scientist
Also trust is a tricky thing. I don't think you should trust newsblur.
It's not that they aren't trustworthy either, it's just that a system
should never have a single point of failure. It's okay that newsblur
is a buisness entity. The most important part of the new system is
that it needs to be distributed. If you don't have one point of
failure then you can always route around a bad actor.
I think you can start with newsblur as the base of anything new you
do, and you just need to layer some things on top. Social is a given,
and the dude behind newsblur has made this a priority but how do we
make social distributed?
I have started making my own tools in the wake of readers
disappearance(http://hea.pe). If others find them useful I want them
to use it, but I don't want them to 'trust' me. Right now the best
way I know around this problem is that I use webhooks to distribute
any information back to them that I gather for them. In this way in
realtime I am replicating any state I keep about a user to a place of
there choosing. I also export all shared items as an rss feed which
again a user can place where they want.
So, if you accept this idea of using webhooks to replicate state
through a distributed system then we might be able to start thinking
about comments as something that gets replicated between systems.
For what it's worth there is already an open protocol that tries to
distribute comments it's called the salmon protocol.
http://www.salmon-protocol.org/ Google had backed it for Buzz, and who
knows they might bring it back for Google+.
If newsblur had a way to distribute comments to other systems I think
we might be able to build a system on top of that.
I do want to point something out. All this openesss, and distributed
software is cool but it's not easy. I have a strong feeling that the
first site that creates a fully integrated solution, even if it isn't
distributed, is going to get the lion share of the google reader
Diaspora.
If our idea is to build the biggest community of previous google
reader users we might want to focus on integrating everything first,
and then working of distributing the system.
First somehow make it distributed. When
That being said, Newsblur is open source, so we shouldn't stop
thinking about a decentralized systems if people want to think about
it.
I don't think it's easy, and there is no magical solution out there
right now but it's not impossible.
> My plan is to build commenting and sharing into a shared feed that is asymmetric -- anybody can follow your shared feed and you can follow anybody else's shared feed. One shared feed per user means simplicity. No private groups, sharing between multiple groups, and privacy settings beyond all or nothing. I feel this simplicity will work best for new users and in terms of providing a consistent and unambiguous sharing experience. Think of it as Twitter for feed sharing.
>
> That's my idea, and I'm hoping to build it in the next couple months. I'm also open to feedback. And you should follow me on GitHub to watch this all happen in real-time: http://github.com/samuelclay.
Funny, cause that's exactly what I intend to do. :-)
Some people will want privacy options. I'm punting on those for v1 and maybe forever. Shares want to be shared!
-A