Code for Anti-Necroposting (Staff only)

Bobsican · Jun 28, 2019

I was passing around the Spongebob wiki, and then I saw this:

(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.

Elizhaa · Jun 28, 2019

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 };

DontTalkDT · Jun 28, 2019

Is it just displaying a message or does it stop you from repying to the thread?

Wokistan · Jun 28, 2019

I've seen some variants that stop replies, but idk if that specific code does.

Bobsican · Jun 28, 2019

DontTalkDT said:
Is it just displaying a message or does it stop you from repying to the thread?

The former, as the latter is too drastic if you ask me, especially considering even staff sometimes have to do it for clarifications.

Elizhaa · Jun 28, 2019

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.

DontTalkDT · Jun 28, 2019

If it just dispays a message this seems like a good idea.

Promestein · Jun 28, 2019

Yeah, I don't think it should prevent replies but just displaying a message is fine.

Bobsican · Jun 28, 2019

I think more staff input is needed, right?

DarkDragonMedeus · Jun 28, 2019

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.

Antvasima · Jun 29, 2019

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.

AKM sama · Jun 29, 2019

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?

Antvasima · Jun 29, 2019

I do not know, but I doubt that the script is that specific.

Skalt711 · Jun 29, 2019

I also don't think that the script can work for a specific board only. As far as I know, it works globally.

Bobsican · Jun 29, 2019

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.

Bobsican · Jul 2, 2019

Bump.

Antvasima · Jul 2, 2019

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." };

Bobsican · Jul 2, 2019

That looks good TBH.

Others still have to give input, of course.

Antvasima · Jul 2, 2019

Yes, we need more input first.

Skalt711 · Jul 2, 2019

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?

Antvasima · Jul 2, 2019

I suppose so.

Elizhaa · Jul 2, 2019

Shouldn't we change the experiryDays to our standard 30 days since Necro start after one month?

Antvasima · Jul 2, 2019

I am not sure. It seems a bit too strict.

Skalt711 · Jul 2, 2019

90 days should stay as a default.

Antvasima · Jul 2, 2019

I think that should probably be fine, yes.

Andytrenom · Jul 2, 2019

I'm fine here as well btw

Elizhaa · Jul 2, 2019

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.

Antvasima · Jul 2, 2019

So do we have enough support to apply this change now?

Schnee_One · Jul 2, 2019

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

Elizhaa · Jul 2, 2019

To be honest, I would prefer more staff's input, I think place the thread in the highlighted thread would help: Official highlights thread. All members should subscribe to it.

Andytrenom · Jul 2, 2019

Allow me

Elizhaa · Jul 2, 2019

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.

Schnee_One · Jul 2, 2019

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

Bobsican · Jul 2, 2019

Can you please link such thread in that case to get more context?

Schnee_One · Jul 2, 2019

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.

Schnee_One · Jul 2, 2019

https://vsbattles.com/vsbattles/3221121?useskin=oasis

Elizhaa · Jul 2, 2019

Oh, @Schnee One, my mistake then and I see your point.

Also, I think I found the old threads: Question About Bumping and Vs thread rule about bumping old threads (staff only)

Andytrenom · Jul 2, 2019

You should probably just recreate it

Andytrenom · Jul 2, 2019

....You were posting a link to your thread. ~~I'm dumb~~

Elizhaa · Jul 2, 2019

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.

Code for Anti-Necroposting (Staff only)

A Fossil at This Point

Bioluminescent African American Working At The CIA

A Fossil at This Point

Resurrection Lily

Hard Working Individual

Maintenance worker

Waifu Connoisseur

Maintenance worker

Maintenance worker

Maintenance worker

Maintenance worker

Maintenance worker

Maintenance worker

Maintenance worker

Similar threads