From: T F <tf...@ho...> - 2001-01-24 15:16:01
|
>From: Chris Nandor <pu...@po...> >Reply-To: sla...@li... >To: sla...@li... >CC: <sla...@li...> >Subject: Re: [Slashcode-development] Thoughts on persistent storie >capability. >Date: Wed, 24 Jan 2001 08:40:41 -0500 >MIME-Version: 1.0 >Received: from [216.136.171.194] by hotmail.com (3.2) with ESMTP id >MHotMailBC38270700C6D821EEE4D888ABC2FC2C0; Wed Jan 24 05:43:35 2001 >Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net)by >usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))id >14LQBZ-00011E-00; Wed, 24 Jan 2001 05:42:05 -0800 >Received: from fire.he.net ([216.218.144.2])by usw-sf-list1.sourceforge.net >with esmtp (Exim 3.16 #1 (Debian))id 14LQBG-0000vP-00for ><sla...@li...>; Wed, 24 Jan 2001 05:41:46 >-0800 >Received: from [10.0.1.177] >(pre...@ma... [24.48.179.232]) by >fire.he.net (8.8.6/8.8.2) with ESMTP id FAA12952; Wed, 24 Jan 2001 05:41:46 >-0800 >From sla...@li... Wed Jan 24 05:44:25 >2001 >X-Sender: chr...@po... >Message-Id: <p05010402b6948b360316@[10.0.1.177]> >In-Reply-To: <000c01c085ec$521a1130$8be2fc9e@happy> >References: <000c01c085ec$521a1130$8be2fc9e@happy> >Sender: sla...@li... >Errors-To: sla...@li... >X-BeenThere: sla...@li... >X-Mailman-Version: 2.0 >Precedence: bulk >List-Help: ><mailto:sla...@li...?subject=help> >List-Post: <mailto:sla...@li...> >List-Subscribe: ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto:sla...@li...?subject=subscribe> >List-Id: Development mailing list only for slashcode. No new user or >install questions. <slashcode-development.lists.sourceforge.net> >List-Unsubscribe: ><http://lists.sourceforge.net/lists/listinfo/slashcode-development>,<mailto:sla...@li...?subject=unsubscribe> >List-Archive: ><http://lists.sourceforge.net/archives//slashcode-development/> > >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. Back to his moderating mod - letting someone moderate in a persistent story (aka a bender story since they're never archived) that they've already posted in: Would this be a good case where using a story param could be used to mark a story 'nomoderatorlocking'? So, after modifying article.pl, and/or one of the templates that has the show/no show for the moderation stuff, you'd be able to turn moderation on all the time for any particular story. _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com |