Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
I think that we have conflicting rules here on the forums. While I already made a thread about proposing a change how the rules are stated, even if that happens, the de facto enforcement is what Im worried about now.
Problem:
If someone gravedigs they get a warning.
If someone posts a thread that already exists they get a warning.
So what do I do if I want to post about something that someone has already posted about but the thread has died?
For example: http://eeforumify.com/viewtopic.php?id=193
Last edited by BEE (Mar 1 2011 1:37:17 pm)
Offline
Gravediggging is only allowed if it adds valuable information
And you aren't getting a warning fro creating a duplicate topic IIRC
Offline
Excluding one, the replies to that topic were relevant and discussion adding, yet people kept saying "Stop posting!!!"
As for warnings, the system here is loose so its difficult to tell what warrants what consequence. Not a problem, just an observation.
Offline
http://eeforumify.com/viewtopic.php?pid=60569#p60569
That was the post that made started the revival, not very valuable is it?
Offline
Yes, I understand that *that* post is spam, but once it was bumped up, why aren't we allowed to keep posting on it
Offline
ARRGGHH STOP POSTING. PLEASE.
I rest my case.
Zoey? You can't rest your case on Zoey
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Here's what we'll do:
A useless post on a topic older than 2 weeks is considered gravedigging and will result in 1 warning.
(Even though a useless post anywhere counts as spam and results in a warning anyway).
Valuable, ON-TOPIC posts on a dead (or once dead) topic are allowed.
Poor zoey, gotta case resting her. D=
Are you gonna put this in the rules, then? I'm too lazy to look for myself.
Last edited by Chimi (Mar 3 2011 2:55:42 pm)
[ Started around 1746046622.696 - Generated in 0.058 seconds, 12 queries executed - Memory usage: 1.46 MiB (Peak: 1.6 MiB) ]