Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[F.Rq.] Warn when necro-posting #1996

Open
YoshiRulz opened this issue Sep 28, 2024 · 7 comments
Open

[F.Rq.] Warn when necro-posting #1996

YoshiRulz opened this issue Sep 28, 2024 · 7 comments

Comments

@YoshiRulz
Copy link
Collaborator

YoshiRulz commented Sep 28, 2024

Edit by @Masterjun3 :

necropost: To post to a long, inactive discussion thread on a forum.


Game tech discussion tends to be very asynchronous, so maybe limit this to certain subfora.

I think having a modal appear when clicking the "New Post" button would be ideal, but it would also work as plain text beside the button, and using either approach on the editor page would also work.

see also #1460, #1596

@vadosnaprimer
Copy link
Collaborator

I don't understand this request. First of all, necro-posting is encouraged, to keep everything in one place. Second, what does "game tech" mean, and how to we detect it? Third, I don't know what a modal text should be saying.

@YoshiRulz
Copy link
Collaborator Author

re: 1) and 2), I appreciate that necro'ing is encouraged for topics about individual games, hence my suggestion to conditionally show the warning based on the subforum.

The text could be as simple as "The last post in this topic was X years ago, are you sure you want to post? [Cancel] [Post]"
or maybe with three options "[Cancel] [Post in new topic] [Post here]"

@bigbass1997
Copy link

bigbass1997 commented Sep 28, 2024

Can you give some examples of subforums this would apply to, and why necro-ing threads would be bad in them?

@vadosnaprimer
Copy link
Collaborator

Sorry I still don't know what this request is meant to accomplish. Creating a new topic for something that already has one is bad, we've been merging similar threads at mass in the past.

@YoshiRulz
Copy link
Collaborator Author

YoshiRulz commented Sep 28, 2024

Anywhere topics are typically in a question-and-answer format, but locking the topic feels too heavy-handed (or is too much moderation work): The Newbie Corner and all the emulator subfora, maybe Encoders' corner and Site. Once the problem/inquiry has been resolved, the participants would probably expect no further notifications from the topic.

I don't mind being overruled here since my forum usage patterns involve having most notifications off.

@vadosnaprimer
Copy link
Collaborator

vadosnaprimer commented Sep 28, 2024

Once the problem/inquiry has been resolved, the participants would probably expect no further notifications from the topic.

Doesn't feel like a common problem. Some threads are for basic questions, but if someone finds a 5 year old thread with a basic question and makes a post in it, I've never seen that post contain an entirely different unrelated question. Usually it's either a new thread for a new question, or reusing an old thread for asking for further details.

And if a user is so annoyed by further details to the point of not wanting anything to do with their former question, they can just unsubscribe from that thread.

@Spikestuff
Copy link
Contributor

Agreeing with feos here, since we should be encouraging necro-posting.

Doing what you want will still have the post to be merged in the end, why warn something when it will become inevitable that it will be merged to the older thread, bumping that back up front.

To me, this is an unnecessary request, and not a thing that should be implemented.


However in saying that, this works in only three forum sections:
Playground, Published Movies and Gruefood.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants