We moved a small, vigorous band of bloggers from scoop to roller and
enhanced their experience.
They created more blog entries and interacted more with their
audience than when using Scoop, even though Scoop is certainly
designed to facilitate and encourage interaction.
Scoop diaries are IMHO blogs that are not promoted to the Scoop
site's front page and may, if the blogger so chooses, be effectively
sequestered.
Individual diary entries are readily "promoted" to the front page by
a Roller administrator with sufficient administrative privilege. That
hierarchy of privilege is in my view the social core of both Scoop
and SlashCode.
Scoop is designed to support that complex hierarchy and to permit
participants to earn their up through it by making "good" decisions
in recommending user-created content for promotion to the site's
online audience in general.
Roller neither has nor appears to promise anything truly comparable.
Roller isn't designed to engender a somewhat self-regulating online
community of people who assign formal rank one another's work and
thus determine its degree of promotion.
At the same time, Roller is readily adapted to the needs of an editor-
centered organization, and Scoop is not.
Roller can certainly support a community of bloggers who have shared
concerns.
It does and has done so almost from inception.
I see Sun's blogs and their clustering by interest/technological
concern as a worthwhile example.
Roller's content aggregations features are certainly compelling
advantages, and while Scoop has somewhat similar features, I didn't
feel they were well-realized. Nor was I a happy camper when trying to
build on that code base.
If you're asking whether Roller can fulfill the functions of Scoop or
SlashCode, however, someone else may have good reason to disagree,
but I don't see it.
Roller is of course a development platform as well as a fully
functional set of products.
You could with some programming effort add features you find useful.
Depends, I guess, on what they are.
You can certainly add classical content publication platform
capabilities, and I see no reason for a skilled Java/database
programmer to be daunted by the tasks.
That to me is important.
We had to substantially modify Scoop to meet clients' needs, and in
various ways also Roller.
For us, things go better with Roller.
Hope this helps.
George Frink
President,
Southern Connections Inc.
919 341 2999
[EMAIL PROTECTED]
On Nov 21, 2007, at 11:25 AM, David Bloom wrote:
I have using a blog platform called scoop which powers
www.dailykos.com, www.sbnation.com, and their array of blogs.
The top five highest trafficked blogs in baseball happen to be the
ones who use this scoop and a key thing about these blogs is they have
a feature called diaries which
is ..
http://scoop.kuro5hin.org/
"Scoop is designed to enable your website to become a community. It
empowers your visitors to be the producers of the site, contributing
news and discussion, and making sure that the signal remains high."
Example: http://www.athleticsnation.com/?
op=search&offset=0&old_count=30&type=diary&topic=§ion=&string=&sea
rch=Search&count=50
http://en.wikipedia.org/wiki/Scoop_(software)
What do you think about this diaries concept in terms of the roller
platform?
Its a separate part of the blog like a wiki or message board like
feel where users can contribute.
--David
