• This forum is strictly intended to be used by members of the VS Battles wiki. Please only register if you have an autoconfirmed account there, as otherwise your registration will be rejected. If you have already registered once, do not do so again, and contact Antvasima if you encounter any problems.

    For instructions regarding the exact procedure to sign up to this forum, please click here.
  • We need Patreon donations for this forum to have all of its running costs financially secured.

    Community members who help us out will receive badges that give them several different benefits, including the removal of all advertisements in this forum, but donations from non-members are also extremely appreciated.

    Please click here for further information, or here to directly visit our Patreon donations page.
  • Please click here for information about a large petition to help children in need.

Code for Anti-Necroposting (Staff only)

Status
Not open for further replies.

Bobsican

He/Him
Messages
21,648
Reaction score
6,290
I was passing around the Spongebob wiki, and then I saw this:

Anti necroposting
(Source: This forum post at the Spongebob wiki)
As we can see in the picture, there´s a message that indicates that a post has been inactive over a noticeable period of time.

I was told to make the thread in this board as the subject is obviously important for this board, despite not being an staff member myself.

It´s to be noted that there´s the Lock Forums JavaScript and the others code which were used by the spongebob wiki as a hint.

Note: Because this is often brought up, the premise of this code is not to disable the comments themselves as if the thread was closed automatically, but rather just display a message like in the picture above.
 
Honestly, it can works and it does help solve necropost.

We could add the Lock Forums JavaScript main code in JSPages.

Within the Common.js, we could edit the expiry days to our standards 30 days.

Code:
window.LockForums = { lockMessageWalls: true, expiryDays: 90 };
 
I've seen some variants that stop replies, but idk if that specific code does.
 
I think the messages can be edited and warning about replying can added as stated on Lock Forums JavaScript, @DontTalkDT.

I think we should edit the messages if we are able to able to fit our wiki standard.
 
I agree with what Prom said. Definitely messages are allowed, especially if it's an important thread or an ongoing debate that was simply halted. But just a simple displayed text to notify people that necroing threads is ill-advised is fine.

The suggestion does say it's simply displays that and does not prevent messages, so it's fine by me.
 
I agree with Promestein, DontTalkDT, and Medeus. This is fine if we only add an automatic warning message after 90 days, but not if the threads are automatically locked.
 
This is fine. Although we decided that it's not an issue with vs threads, so can we pick and choose in which board we want to apply this?
 
I do not know, but I doubt that the script is that specific.
 
I also don't think that the script can work for a specific board only. As far as I know, it works globally.
 
Well, is there any script that works as board-specific?

Some of such code may be translatable to bring a board-specific version of the "Anti-Necro" script.
 
Well, maybe we could simply use the following code?

Code:
window.LockForums = { expiryDays: 90, expiryMessage: "This thread has not been commented on for over <expiryDays> days. There is no need to reply, unless it is part of the versus forum." };
Or something like this, if we want to include message walls:

Code:
window.LockForums = { lockMessageWalls: true, expiryDays: 90, expiryMessage: "This thread has not been commented on for over <expiryDays> days. There is no need to reply, unless it is part of the versus forum." };
 
That looks good TBH.

Others still have to give input, of course.
 
Yes, we need more input first.
 
Code:
window.LockForums = { expiryDays: 90, expiryMessage: "This thread has not been commented on for over <expiryDays> days. There is no need to reply, unless it is part of the versus forum." };
This variation works?
 
I suppose so.
 
Shouldn't we change the experiryDays to our standard 30 days since Necro start after one month?
 
I am not sure. It seems a bit too strict.
 
I think that should probably be fine, yes.
 
I wanted to check for the day limit to get a necro. Apparently, we don't really have a strict day basis for necro from VS Battles Glossary:

  • Necro: To post in a discussion thread that has been inactive for a long time. In most cases, it is probably best to create a new thread instead.
Well, 90 days is fine with me now.
 
So do we have enough support to apply this change now?
 
AKM sama said:
This is fine. Although we decided that it's not an issue with vs threads, so can we pick and choose in which board we want to apply this?
TBH That thread wasn't finished on the decision, so it should be bumped and fully included
 
I think @Skalt711 has answered @AKM sama's question, @Schnee One. The javascript is not board-specific.

Also, @Bobsica , I don't believe there are board-specific Lock Forums since this one looks to be only javascript on the topic.

Moreover, there likely won't be board-specific option since the update to the javascript have been discontinued and the fact that Fandom disable the Forums in most wiki further make this option more unlikely to work on.
 
What Skalt answered has nothing to do with what I said

Our descision that necroes on versus threads aren't a problem was never truely decided.

We have a thread already made however, I can bump it so the descision can be made
 
Can you please link such thread in that case to get more context?
 
Trying to go through thousands of threads to find one is a bit of a time waste

Most people agree on it though, so I can make it.
 
Andytrenom said:
You should probably just recreate it
I think there is no need recreate it now since I think @Schnee One recreated the thread. I will just the past the past thread link thread on his for additional informations, @Andytrenom.
 
Status
Not open for further replies.
Back
Top