Page 2 of 7 FirstFirst 1234 ... LastLast
Results 11 to 20 of 62

Thread: NNTP vs Web Interface

  1. #11
    Join Date
    Jun 2008
    Location
    Finland, European Union
    Posts
    1,879

    Default Re: NNTP vs Web Interface

    Quote Originally Posted by DenverD View Post
    remove inappropriate postings (personal attacks, unwanted language, adverts, spam, etc)
    Yes, let's censor all the posts in advance, we've seen how well that works. While we're at it, let's change the Geeko into Fox News icon.

    It's too much work to go through each and every post, especially in a forum that is going to eventually grow to host thousands, even tens of thousands of accounts - maybe even more.

    Once again the issue seems to be that it's causing problems for that small group of people.

  2. #12
    Join Date
    Jan 2008
    Location
    N40 44.977 W073 59.356
    Posts
    1,170

    Default Re: NNTP vs Web Interface

    Quote Originally Posted by DenverD View Post
    > we've never found a perfect way to ensure everyone posts in the right
    > place.


    well, it is rather simple actually:

    first, never let a thread originating post (from either the HTML or NNTP
    side become publically viewable until it has been vetted and approved by
    a forum moderator...
    That is a little easier said then done though. Take yesterday for instance. There where 160 new threads created. Staff would have to look at each of these threads and move them. Now what if there is no staff member logged in at the time and it takes an hour or 2. That is a disservice to the member as someone with the answer might have been able to answer it in 5 minutes if it was approved. As for the NNTP side, since I'm new there I'm not sure if moving the thread in NNTP before it gets posted is even possible.

  3. #13
    Join Date
    Jan 2008
    Location
    N40 44.977 W073 59.356
    Posts
    1,170

    Default Re: NNTP vs Web Interface

    Quote Originally Posted by DenverD View Post
    > The problem for NNTP users right now is, we don't
    > even notice when a thread is moved or closed.


    what does it mean "a thread being closed"?
    On the web side, if a thread gets too heated it gets closed. This effectively shuts off all posting ability to that particular thread. On the NNTP side, it doesn't see a change like that. Same thing with moving, NNTP will not see that the thread got moved to forum x from forum y.
    does it mean that i won't see it anymore with my newsreader?

    like, if i have a problem next week and KNOW i read the answer two
    months ago in (NNTP) /Hardware, but if i look for it and the thread was
    "closed" will it have disappeared?

    if it has vanished on NNTP, will i be able to find it in the Hardware
    forum on the net?
    No it won't disappear in either side.
    if it has _not_ vanished (to newsreaders) and i write a new (NNTP) post
    saying that what worked for PosterX two months ago doesn't work for me
    (and HELP!), what happens when i click send to a "closed thread"??

    --
    DenverD
    A Texan in Denmark
    It posts which is a problem since it was closed for a particular reason in the first place. Most likely you will not see a thread closed unless it became too heated and people started hurling personal attacks. I wouldn't worry about normal threads being closed.

  4. #14

    Default Re: NNTP vs Web Interface

    Call me an idiot but isn't the simplest way in moving a thread is...

    Mod sees thread to move, posts comment moving thread to xyz, goes makes a cup of coffee, runs around the block, twiddles his thumbs for 10mins etc..(isn't that how often the nntp gateway syncs?) then moves said thread.

    Now it won't stop someone replying to said thread if they've not got the mod post but would stop later ones. Then it could be found or be at least looked for in the correct forum even if a true link wouldn't exist till moved.
    Man first, have a try at Info, have a look at Wiki, if all that fails Scroogle!!!!!
    If I've helped click on the Rep button I don't know what it does but it sounds cool.

  5. #15
    Join Date
    Mar 2008
    Location
    Bochum, Germany
    Posts
    3,587

    Default Re: NNTP vs Web Interface

    * DenverD,

    the problem is, you *will* see a closed or moved thread and you cannot notice it has been closed or moved. Hence you'll reply to it, causing a mess on the web interface.

    Uwe

  6. #16
    Join Date
    Jan 2008
    Location
    N40 44.977 W073 59.356
    Posts
    1,170

    Default Re: NNTP vs Web Interface

    Quote Originally Posted by FeatherMonkey View Post
    Mod sees thread to move, posts comment moving thread to xyz, goes makes a cup of coffee, runs around the block, twiddles his thumbs for 10mins etc..(isn't that how often the nntp gateway syncs?) then moves said thread.
    My thoughts lately too. I've been trying to do this for moved threads lately.

  7. #17
    Jim Henderson NNTP User

    Default Re: NNTP vs Web Interface

    On Wed, 02 Jul 2008 14:06:11 +0000, DenverD wrote:

    > well, it is rather simple actually:
    >
    > first, never let a thread originating post (from either the HTML or NNTP
    > side become publically viewable until it has been vetted and approved by
    > a forum moderator...


    Would you be willing to do that as a moderator? I don't know that I
    would - approving thousands of messages a day is not a viable solution
    IMHO.

    Jim

  8. #18
    Jim Henderson NNTP User

    Default Re: NNTP vs Web Interface

    On Wed, 02 Jul 2008 14:36:04 +0000, 69 rs ss wrote:

    > Staff would have to look at
    > each of these threads and move them.


    This is the thing that I don't understand about moving threads,
    actually. If staff move them when posted in the wrong place, doesn't
    that encourage users to not think, because a mod will move the thread to
    the proper place regardless? That's the reason I prefer redirection,
    because it encourages the users to think about finding the right place
    *before* they post.

    Jim

  9. #19
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: NNTP vs Web Interface

    > Would you be willing to do that as a moderator? I don't know that I
    > would - approving thousands of messages a day is not a viable solution
    > IMHO.


    just MHO: if staff is not willing to view _thread_initiating_posts_ (NOT
    every reply) then they should not come along hours or days later and
    suddenly view a _thread_ and be so interested in where it _was_ posted
    that they are (now) willing to move it.

    --
    DenverD (Linux Counter 282315)
    A Texan in Denmark

  10. #20
    Join Date
    Jan 2008
    Location
    N40 44.977 W073 59.356
    Posts
    1,170

    Default Re: NNTP vs Web Interface

    Quote Originally Posted by DenverD View Post
    > Would you be willing to do that as a moderator? I don't know that I
    > would - approving thousands of messages a day is not a viable solution
    > IMHO.


    just MHO: if staff is not willing to view _thread_initiating_posts_ (NOT
    every reply) then they should not come along hours or days later and
    suddenly view a _thread_ and be so interested in where it _was_ posted
    that they are (now) willing to move it.

    --
    DenverD (Linux Counter 282315)
    A Texan in Denmark
    Which isn't what is actually happening. most of the time the threads that are moved are done right away, the issue is afterwards having to go back when an NNTP user posts to the old place of the thread. That I think is the main issue with what is going on.

Page 2 of 7 FirstFirst 1234 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •