But the goal is not to stop them. We have, in fact, recently relaxed the rule on zombies, so that we no longer reflexively lock them. One result of this is that a revived thread, once revived, can end up having a whole new second round of discussion. What’s upsetting people is that they don’t realize it’s a second round.
And, to be quite blunt, if it upsets them it is their own fault.
Moderators adding the word “ZOMBIE” to thread titles won’t do much to make new posters feel welcome in the same way mentioned above about other posters dissing them for it in the thread. Having a mod step in and edit the thread title to warn off possible readers that something might be wrong with it seems like an even less friendly welcome than individual posters making snide comments about it in the thread as is often the case now.
It wouldn’t be accurate to do so anyway. Once the thread has been revived if it is getting new reads and replies with on-topic information it has successfully passed from that otherworldly place it existed back into the world of the living, and is once again a current, active, thread. Why should it be branded by moderators or other posters as something to avoid just because a few people have a knee-jerk reaction and resent any participation in any thread that has been inactive for some undefined amount of time? How long is too long? Once it has been bumped off the front page? Six months? Two years?
Since this is such a big issue for some I do agree the date stamp could be displayed in something other than a tiny, light gray font. If the date stamp were as visible as the posters name, for example (about 6 times bigger, bold, and underlined) it might help prevent a few zombies from being unintentionally revived, and maybe more importantly it would provide those who are annoyed at reading zombie threads an even more obvious indicator than the current date stamp already provides to them.
That seems to be what the zombie haters in this thread are asking for: something to just reach off the page and remind them that they have failed to notice the dates that are already displayed right at the top of every post. Making the date display more prominent might make it easier to notice it for those who just can’t be bothered to read them as they are now (but somehow still resent it when brand new members, making their first-ever posts to the board, don’t read them either)
Works great!
For someone who’s never played with other than click and it’s installed GMS it was pretty damned painless.
But shouldn’t the instructions (for n00bs like me ;)) be;
Highlight and copy the code in the box.
Paste the code into a text editor like Notepad.
Save the text file (somewhere you can find it, the name doesn’t really matter).
Right-click the .txt file and rename it SDMB highlight old threads.user.js.
Drag it into an open browser that supports GM.
Click “Install” on the screen that pops up.
Enjoy!
CMC fnord!
I tweaked the text size :). Which made me curious, what would need to be changed to have it show the number of months too (YMD instead of YD)? I assume it would be a lot easier to use 31 day months, or could you use 30.436875?
QFT.
I’ve posted comments in threads only to realize after posting that they were Zombies. After doing it a couple of times I’ve been trained to notice the dates now. The problem will solve itself.
Also, a quick tip: if you’re reading through the thread (which I’m sure you’re doing before you post) and you notice someone posts a comment about how you just HAVE to run out and see this new movie that just came out in theaters called Spider-Man because it’s “the shizzle,” or how President Bush (either one) is doing a kick-ass job but his VP is a bit of a jerk, you might want to check the date of the thread before posting.
Thanks for saving me the trouble. I was about to look into that today. If you want, you can convert that to a regular Firefox addon by uploading it here.
Greasemonkey is my answer for pretty much every annoying thing about the Internet. It works a lot better than trying to convince anyone to actually change anything.
ETA[sup]2[/sup]: LOL @ Shark Sandwich
Why don’t you promote the people who don’t think adding the Zombie tag is very much work to Zombirators and give them thread title editing privelges and let them do it?
Perhaps we could change, “Read first unread”, to say, “Read first UNDEAD”
Aaarrrggghhhh. “View First Unread” to “View First UNDEAD”.
I missed your tiny text. Maybe I can at least be of some assistance. Just find the first line below, and add the next two lines below it.
diff_days = diff_days - 365*diff_years;
var diff_months = diff_days / 31;
diff_days = diff_days - 31*diff_months;
Then change the line that start with “warnStr =” to
warnStr = "<div style=\"font-size:36px;text-align:center;color:#ff0000;\"> This thread is " + diff_years + " years, " + diff_months + " months, and " + diff_days + " days old!</div>";
And, yes, you could replace 31 with 30.436875, though I wouldn’t. If you really want to be that exact, you might as well recode that part to handle all the months individually.
Where the hell is Capitaine Zombie? Shouldn’t he be taking care of this?
Is there a way to make the greasemonkey script appear on subsequent pages of a thread? For instance, this thread is a zombie, but the last couple pages don’t trigger the script because the posts on those pages are within the last year.
Oh that’s why all my posts get taken off, I was wondering. A shame, there were some real treasures of wisdom in the latest ones.
I concur.
I’ve suggested this many times. A small, back-end script that runs on the SQL server nightly or weekly. It looks for open threads where the last message is dated more than XX days ago and marks it closed. It’s an incredibly simple thing to do.
But, and this is the big thing (though personally I wouldn’t see anything wrong with it), they don’t want to lock the threads. And apparently there is no easy way to mark them and leave them open (again, I personally don’t see a reason to mark them either).
I wanted to expand a little on something related to this, if I might…
Before the boards were search-engine indexed, it required a reasonable amount of effort to actually find them in the first place (assuming you weren’t a regular reader of the column if your local paper ran it), so the people that (for the most part) did find their way here had a reasonable knowledge of how discussion boards worked and so on. And because individual threads weren’t as easy to find (unless you were a member), by the time you’d signed up, done a search, found the topic… it just seemed a bit more “obvious” that the topic was old by that point.
I’m not saying we shouldn’t encourage new members (quite the opposite!), but I’m sure I’m not the only one who’d like to encourage them to read a bit more of the boards before blithely wading into a five year old discussion that the key players have long since moved on from.
Or that the revived discussion involves a lot of people who are no longer here, have changed their opinions, or simply don’t wish to be reminded of (or re-involved in) something they thought was concluded a long time ago.
If it involves a lot of back-and-forth, esp. with people no longer here, we will close them – most of those, however, would be in the category of contentious threads I referred to earlier. (If not in this thread, in one of the many others on the topic over the last few months.)
Most of the threads that are revived don’t really require the continued participation of the people who posted in its first life. When they do, if that fact is brought to the attention of the mods, we close them.
It would also be cool if there was some way to mark a thread as having a very early OP on the “forumdisplay” list, so you can see it before you click on the link, but that may be impossible if the variable isn’t accessible from that page.
You covered the problem for both of these in one. AFAIK, the information about the first post can only be found by finding it on the page. If it’s not there, Greasemonkey can’t get it.
Granted, it wouldn’t be impossible to open the first page of the thread in the background, so Munch’s suggestion is not too hard. But to do your (GuanoLad’s) request, you’d have to open every thread (or at least the first post) to note when the OP started. It’s a useful suggestion, but highly impractical to actually perform client-side.
My reluctance to look at Munch’s request is that it’s kinda against the script’s purpose, as I understand it. The point is to keep you from responding to posts that are older than a certain date. If the first post you see is later than that date, then there’s no problem. It’s a complicated fix without much, if any, benefit.