Hey ChiefsPlanet. Can we all agree that, at least at some level, megathreads suck? I mean, if you want to have a megathread in the media center to talk about a TV show, a megathread about a sports team/league other than the Chiefs, etc., that's just fine.
But about Chiefs discussion? A vast majority of the time, those quickly turn into a shit slinging contest from a handful of opinionated posters. A lot of people just avoid them for that reason, yet people feel like they can't post a thread about a topic that was already buried in some sort of megathread because people will just bitch at them for the "repost". It's one of the most frequent complaints we hear from people who aren't on here all the time - it's just hard to keep up in that format. Hell, I'm theoretically on the leadership team around here, and I find myself pretty much just going to Arrowhead Pride or the Star for my Chiefs news and coming here almost out of habit.
The problem is that it's hard to really set "rules" in place that wouldn't feel obnoxious. No threads above 500 posts? That would kill game threads and all of the "legit" megathreads out there. No megathreads on Chiefs topics? Well, what's your definition there?
Until we can come up with a better idea, can we all just agree to try and collectively encourage people to post individual threads on Chiefs topics? That could mean:
If someone posts a thread, and particularly if they take the time to format an article from a different source so that it can be easily read here, say thanks. Give people positive rep. It takes effort (and a tiny bit of thick skin) to post a thread around here, so we should try and appreciate the time it takes.
If there's a thread that is about news that hasn't had its own thread already posted, it's NOT A REPOST. If a mod is having a bad day, we might even boot you from the thread if you gripe at people for a "repost" that is buried in a megathread. And, megathread haters, feel free to discourage this kind of thing in whatever fashion you feel personally suits the situation.
Try not to feel like a Chiefs topic isn't important enough for a thread. I would have loved to have a daily discussion thread on training camp to be able to hear about which scrubs look promising and which should hit the road. Is that in the megathread somewhere? Probably. But I'd have to wade through hundreds of penbrook posts to find it. And no one should have to do that.
If someone posts an ACTUAL repost (where there's another thread specifically on that topic), give them the benefit of the doubt, and try not to be an ass about it. Report the thread to the mods if it bothers you, and we can merge the threads together.
There's a balance somewhere beyond which the whole place would be filled with shit threads and reposts, but we're so far away from that that it's hard to imagine we'd go too far any time soon. So...post more threads, you fucking assholes. And if someone gives you shit about it, tell them the mods tell them to fuck off. [Reply]
But that's the whole point. If a megathread is derailed, all discussion basically stops. If one of 5 threads on individual topics is derailed, the others are fine. [Reply]
I don't like megathreads on Chief related subjects. While I do have the time to wade through pages of pro-Alex vs. anti-Alex (the beauty of retirement), I don't want to. [Reply]
I made the training camp megathread, because daily threads don't work. I suggested weekly threads though. Mods can close the thread and I will start a new one with the twitter feed.
I also explicitly said it was a repository for info and individual threads can and should be pulled from info inside the mega. [Reply]
I hate long posts much more than a mega thread, especially if it's the OP.
Several of our members, particularly in DC are posting copies of "War and Peace" every time they are trying to make a point. Mayb e they think they are being judged by how many words they can post.
WHAT EVER HAPPENED TO WRAP SPOILER TAGS AROUND LONG ARTICLES?!?!?
Bring back some rules on this! [Reply]
Megathreads make sense for niche discussions -- Mizzou basketball, cooking tips, luv's romantic life, etc.
For Chiefs discussion, there should not be megathreads. Every article that is posted about training camp deserves its own thread (most days).
I like this idea. Megathreads are needed for non Chiefs stuff like the Cardinals and gear-head threads but the Chiefs info and discussion shouldn't be in a mega-thread. [Reply]
Originally Posted by saphojunkie:
I made the training camp megathread, because daily threads don't work. I suggested weekly threads though. Mods can close the thread and I will start a new one with the twitter feed.
I also explicitly said it was a repository for info and individual threads can and should be pulled from info inside the mega.
Perhaps break them down by QB, O, D, RB's, Receivers, etc. I can't make my way through you training camp one sometimes as is and I think there is a lot of info that is missed and not even posted. [Reply]
Originally Posted by DaFace:
But that's the whole point. If a megathread is derailed, all discussion basically stops. If one of 5 threads on individual topics is derailed, the others are fine.
And, if the megathread derails, you have to wade through the derailment until the next actual news shows up. If each Chiefs news item gets it's own thread, you can catch all the news and the relevant posts that appear early in the thread and just bail when the derailment happens.
Kudos to you guys for recognizing this problem and for trying to avoid being heavy handed with a solution. If a voluntary approach doesn't work though, take a poll asking whether we like or dislike megathreads and perma ban everyone who says they like them. :-) [Reply]
Originally Posted by saphojunkie:
I made the training camp megathread, because daily threads don't work. I suggested weekly threads though. Mods can close the thread and I will start a new one with the twitter feed.
I also explicitly said it was a repository for info and individual threads can and should be pulled from info inside the mega.
Ban saphojunkie to make an example of him. :-) [Reply]
