I have to say, the pollyannish OSS chorus is getting pretty tiring.
OSS is great for building rock-solid libraries and daemons, but has a
pretty poor record of producing usable products for end-users.
Services have an especially serious challenge: they must be
maintained, and hosting bills must be paid, by someone, and end users
become dependent on that person not losing interest - there are severe
SLA and economics problems.
Google+ and FB aren't going anywhere for a long time (same with your
gmail accounts). If those models provide what you want then IMO you
should seriously consider building on top of them.
> I have to say, the pollyannish OSS chorus is getting pretty tiring.
> OSS is great for building rock-solid libraries and daemons, but has a
> pretty poor record of producing usable products for end-users.
Yeah, because no one uses WordPress or Firefox. It's not about being a
Pollyanna, it's a practical matter of sustainability.
Whether the product is usable depends on whether there's effort put into
usability and inviting usability experts as contributors. It can and has
been done.
> Services have an especially serious challenge: they must be
> maintained, and hosting bills must be paid, by someone, and end users
> become dependent on that person not losing interest - there are severe
> SLA and economics problems.
That's true, but it doesn't have much to do with OSS. Other than, you
know, being free to go start up your own service elsewhere with the same
software when the one you were using goes down.
> Google+ and FB aren't going anywhere for a long time (same with your
> gmail accounts). If those models provide what you want then IMO you
> should seriously consider building on top of them.
And that's what got us into this fix in the first place. Google+ and FB
might not be going anywhere, but they own the APIs and can pull out the
rug (or do something distasteful) at any time. If we rebuild using open
software and formats, there are fewer points of failure.
That said, no successful sharing ecosystem can ignore Google+ or FB or
Twitter. That's where a lot of our friends are. But the way to go, IMO,
is to treat them as supported but optional channels - and not the
foundation for the whole thing.
--
m...@lmorchard.com
http://decafbad.com
{web,mad,computer} scientist
The more that can be done with existing feed formats, the better, IMO.
Then you can get value in and out of existing readers without
campaigning for modifications
http://en.wordpress.com/about/
http://www.mozilla.org/en-US/about/careers.html#feature-team
Code and architecture and prototypes fall far short of what it takes
to make a living platform. And if you're making something that's
social, there are zero current examples of successful open-source
social platforms. Diaspora is trying to be the first (and, notably,
they're creating a real organization, i.e. with money, and if you
dismiss Mike's suggestions on technical grounds you might consider
that the technical stuff might not even be the hard part to get right
here).
If social news was something you could get VC funding for, you'd start
out by using Twitter, FB, or Google for *at least* identity. People
who wonder out loud on this list about whether this or that Twitter
integration might work should not be immediately jumped on. Not all of
us agree that the demise of Reader is clear evidence that only an OSS
replacement will do.
But we are not talking about conquering the world or competing with Facebook, but about sustaining little communities of dozens or a couple of hundred of users which are going to share and discuss text contents. Without featuritis, bandwidth and server workload would be negligible
The economics here don't have to be bad, either. This could even be a
place where people could directly pay for something they care about.
Would you pay US$12 to support a social news service for a year? A
little money goes a long way these days.
> Code and architecture and prototypes fall far short of what it takes
> to make a living platform. And if you're making something that's
> social, there are zero current examples of successful open-source
> social platforms.
Zero, if you don't count the web of WordPress sites (and the web in
general) as a social platform - which I do. Not everything has to look
like a Facebook substitute.
> Diaspora is trying to be the first (and, notably, they're creating a
> real organization, i.e. with money, and if you dismiss Mike's
> suggestions on technical grounds you might consider that the
> technical stuff might not even be the hard part to get right here).
I wish them luck, but I'm not holding my breath.
> If social news was something you could get VC funding for, you'd
> start out by using Twitter, FB, or Google for *at least* identity.
Who needs VC funding these days? I'd say the impulse to build atop
another company's platform as a shortcut to VC funding is part of the
problem. If you need money, head to Kickstarter and get a few dozen - or
a few hundred people - together who care about the service.
> People who wonder out loud on this list about whether this or that
> Twitter integration might work should not be immediately jumped on.
If I've jumped on anyone, it's because I'm tired of seeing services I
care about get wrecked or yanked. And it pains me to see new efforts
heading down the same paths that have lead to disappointment in the past.
It's like earthquake-proofing buildings. How many do earthquakes do you
need to live through before you start thinking maybe things should get
built on different foundations?
> Not all of us agree that the demise of Reader is clear evidence that
> only an OSS replacement will do.
Then we can agree to disagree, and I'm sorry if that tires you. You can
ignore people talking about OSS, whether you think we're pollyannas or not.
>> Code and architecture and prototypes fall far short of what it takes
>> to make a living platform. And if you're making something that's
>> social, there are zero current examples of successful open-source
>> social platforms.
>
> Zero, if you don't count the web of WordPress sites (and the web in
> general) as a social platform - which I do. Not everything has to look
> like a Facebook substitute.
Also LiveJournal is based on a free software codebase, (Dreamwidth
uses a substantially identical one too).
--
http://www.lulu.com/spotlight/andrew1308 - Buy my books
National Pep CDs - http://cdbaby.com/cd/nationalpep
You'd have to hack on it a bit, plus you'd be requiring two identities
(which, to me, kind of kills the idea for "normal" users), but I bet
you could get it to work.
I have to say, the pollyannish OSS chorus is getting pretty tiring.
Google+ and FB aren't going anywhere for a long time (same with your
gmail accounts). If those models provide what you want then IMO you
should seriously consider building on top of them.
On Sun, Nov 6, 2011 at 3:15 AM, matvey bossis <bos...@gmail.com> wrote:
> Guys,
>
> We have seen a couple of hacks, which re-enable shared items in GR.
> These hacks might cease to work, if G decides so.
> Here is another idea for a hack: how about a Chrome (or whatever)
> plugin, which would use your '+1' items list, instead of the old
> Shared Items somehow. Ideally, it would show also who else +1'ed the
> item.
> To bring back commenting, in lack of a google equivalent, the
> 'Facebook Comments' plugin may be utilized. I know, I know, it sounds
> ridiculous, but Google will roll out it's own comments plugin once, I
> am sure.
>
> What do you think?
> an open trusted service that can handle commenting for any item we can shareWhy can people be sure that this service will not disappear?
We trust google to hold our mail for good reason, because they have
very very strong incentives to keep the service going, keep it secure,
etc.