Re: [Slashcode-development] Thoughts on persistent storie capability.

[CertIndex.com W. <web...@ce...>]

----- Original Message -----
From: "Chris Nandor" <pu...@po...>
To: <sla...@li...>
Cc: <sla...@li...>
Sent: Wednesday, January 24, 2001 5:40 AM
Subject: Re: [Slashcode-development] Thoughts on persistent storie
capability.


> At 01:59 -0800 01.24.2001, CertIndex.com Webmaster wrote:
> >Persistent stories: Stories that are meant to be continuously used for
> >discussion regarding one or more issues/subjects/blah that do not 'time
> >out/die' like typical 'news' type stories that are tied to chronology.
The
> >example I gave was on a web design site, a story could be created for
'HTML
> >Help'. Since on a site like this that kind of story would always be
> >beneficial and isn't tied to anything chronological (like news stories.)
it
> >would be nice to have this always 'stick around'. It's pretty much the
only
> >real feature BB's like UBB and Phorum have over Slash and I see it
> >constantly requested.
> >
> >So that I don't have to preface any conversation regarding this with that
> >'definition' does anyone have a better suggestion for this kind of story
> >than persistent story? Otherwise I'll refer to it as that from now on
with
> >no preface.
>
> The only thing I don't see is how Slash (bender, esp.) does not have this
> now.  I mean, I see how some things would need to change to make this
> feature of Slash _better_ (as you stated in the rest of the post, about
> moderation, pruning comments, etc.), but it is there and it works, as far
> as I can tell.

Let's clarify. The architecture of Slash is such that hacking out a BB
wouldn't be too hard, but there is no robust 'out of the box' support for
having some sections ( or however this functionality would be supported ) be
in BB format. If there was, wouldn't Slashdot's cousin, SourceForge, have
used it for their forums? :) Reference URL:
http://sourceforge.net/forum/?group_id=1

By your logic, everything that can exist in the weblog/bb type app already
does exist in Slash because 'it'd only take a little change to make it
*better*'. That's not how *most* people look at it, obviously, since this
feature has been requested multiple times in the past week alone. Until
someone can specify some configuration setting somewhere to simply turn 'BB
style' on for a section in Slash and have all stories in it turn into topics
and not 'go away' and have all comments posted in those topics not 'go
away', I don't consider this feature existing.

I agree that it would not be hard to do, and that's what we're working to
do, but I strongly disagree that this is 'there'. Perhaps this mentality is
what keeps a lot of people from Slash. For example, of course Slash installs
(usually ;) but does it install well? Does it install with a few clicks
rather than massive perl knowledge and so on? I'd say not. (And please don't
use the argument that you don't want to support click-and-configure type
installs because they are 'l4m3' or Windows'esque or something equally
elitist. You know what I'm getting at.) Regarding this example, don't take
offense. I am a proponent of Slash whenever I can and I constantly think
about ways to improve the project wherever I/we can, but recognizing it's
short-comings from our *and* regular Slash users' perspectives is important
if we want Slash to have wide-spread acceptance as a viable solution.

Also consider someone new to Slash coming to slashcode.org looking to run it
isn't going to have the intimate knowledge of Slash you do, so what may be
simple to you may be daunting to them. That's why I think there should
always be a focus to make features as easy to support/configure/etc rather
than requiring a perl certification to make the damn shit work. :)

Regards

>
> --
> Chris Nandor                      pu...@po...    http://pudge.net/
> Open Source Development Network    pu...@os...     http://osdn.com/
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
>