Fwd: Re: [IMC-Tech] Active 2?

[Paul Riismandel]

There's a thread talking about updates to Active on global-tech --here's 
something about SF's own fork of the Active code:


>Delivered-To: mediageek-org-listgeek at mediageek.org
>From: Joshua Thayer <joshua at craigslist.org>
>To: Lee Azzarello <lee at eds.org>
>cc: <IMc-tech at lists.indymedia.org>
>Subject: Re: [IMC-Tech] Active 2?
>Date: Mon, 22 Oct 2001 17:41:00 -0700 (PDT)
>
>
>
>i guess i'll jump in here.
>
>san francisco has long been running our own version of active. we're
>running a bastardized version that was originally forked before the LA
>DNC, and has been in development locally since then.
>
>sf-active (as we have been calling it) uses MySQL as its db, has an
>effective caching system, supports topical newswires, supports a large
>number of MIME-types, uses templates, has an integrated and pretty
>advanced features management system, a working search feature, and a
>registration-free ratings system (which we're not using right now, but is
>similar to kuro5hin's). the code is all PHP. we have an integrated
>calendering system. there are probably some other features i'm not
>thinking of right now, as i'm at work and should be doing other things...
>
>currently, only sf.indymedia.org is running the sf code, but we've been
>approached by a number of new and existing IMCs to migrate to the sf code.
>in the next week, we're going to be working hard on cleaning everything
>up, putting it properly into CVS, and working on a distribution scheme.
>we'll also be adding i18n support.
>
>i agree that collaborative editorial systems are a cool idea and have a
>lot of interesting implications, but when we were experimenting with it on
>sf.indy (many months ago), it failed simply because not enough people were
>using it. maybe it would work better now that our traffic is higher.
>
>i'd be happy to talk about this on irc, i'm generally in #tech all the
>time.
>
>cheers,
>
>joshua / espe
>
>
>On Mon, 22 Oct 2001, Lee Azzarello wrote:
>
> > This same discussion is happening here in NYC. I found two systems that
> > appeal to me. First is IMCslash, Philly's hacked version of slashcode. The
> > second has nothing to do with the IMC at all but is a very interesting way
> > of participatory editorship. The engine is called Scoop, it's GPLed and
> > written in Perl (as far as I can tell). A great example of Scoop in action
> > is http://www.kuro5hin.org
> >
> > Info about Scoop technology is at http://scoop.kuro5hin.org/
> >
> > Basically, there are no centralized editors. Stories appear on both the
> > frontpage center column and the smaller side column through a user
> > moderation system. Someone submits a story, it gets stacked in a story
> > queue. Then if you login, you can view the queue and vote on where you
> > feel the story should appear. You can give it a +1 center column, a +1
> > side column, a 0 indifferent, or a -1 throw away. There are threshold
> > levels set for when an article moves out of the queue and into either the
> > frontpage, or the trash.
> >
> > I think this could really work as a a participatory form of moderation. It
> > also doesn't exclude anyone's voice because if one chooses, one can login
> > and view the entire unmoderated queue. Actually, the moderation queue
> > functions as a little discussion forum in it's own. Try it, it's
> > addictive.
> >
> > I'm thinking of setting up a Scoop server in nyc to give it a trial run.
> >
> > -l[e^2]
> > -----------------
> > chmod -R 777 /
> > chown -R nobody /
> > imagine true freedom
> >
> > http://eds.org/~lee
> >
> >
> > _______________________________________________
> > imc-tech mailing list
> > imc-tech at lists.indymedia.org
> > http://lists.indymedia.org/mailman/listinfo/imc-tech
> >
>
>_______________________________________________
>imc-tech mailing list
>imc-tech at lists.indymedia.org
>http://lists.indymedia.org/mailman/listinfo/imc-tech