Damage, please don't give people misleading approvals like this.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Well yeah why would you? Posting Discord DM's is cringe as **** and I'd rather not drop me and M3X's convo's that go over a bunch of shit, not just some random hobby thread, some of which def ain't suitable for the wiki, every other post.but I can't find any evidence of you having done so for the latest flurry of posts. And I'd think you didn't since you pointed to this old post to justify it.
Except that isn't what's happening here, it's more "OP invites the co-creator of the thread to partake and actively tells him to do so and OP".I think you're missing the wack-ness of this precedent. If we just let the OP of staff-only threads invite whoever they want to freely participate in it, then it's not a staff-only a thread, it's a "staff and as many of the OP's friends as they want to include" thread.
Of that text, I told Deagon, and now I'm telling you, don't misconstrue what I actually said. just because I didn't ******* write out an encyclopedic level worth of text, admittedly, barebones as **** page, doesn't mean I wasn't involved at all. Hell didn't M3X literally say I'm the person who brought it up to begin with? I obviously helped, gave ideas, pointers, and suggestions and had to listen to this shit while it was being done.I was letting it slide earlier, because it sounded like you contributed a lot, but now you're saying that you just edited two lines.
If they're knowledgable, unironically tbh, whether it be 1 or 100. Especially for massive verses, I'd rather the opinion of people who know what the **** they're even talking about than those who don't, staff or not.I don't want CRTs for massive verses giving 12 people permission because they each contributed a few scans to it.
Well that's what's going to have to happen now because goddamn lmao.And yeah, you could make it a non-staff thread next time if you want non-staff participation. That's what I tend to do. It's just that if it becomes a shitshow, it'll be remade into a staff only thread regardless.
Yes, and?Yeah, that's why I said the wack-ness of this precedent, not the wackness of this case. Especially since, as you said later, you're fine with the precedent being extended like that.
Then don't talk about it as if you were?Yeah it's just hard to weigh up how much that matters, since I wasn't there.
Tedious, extra effort, can easily be misconstrued, requires a middleman who might not be always available to do so given people have lives, and could easily get lost in shit, it shouldn't be up to OP to speak for others especially if they don't want to, OP can easily just go "nah man i dont wanna".If it's their knowledge we're mining, they have a lot of options to get that through:
The OP of the thread can post it.
I mean apparently, that isn't good enough as we can see here.They can ask a staff member for permission on a per-post basis.
If they're busy? If the bureaucrat doesn't give permission, not because they shouldn't, but because of their own lack of knowledge around the situation, the people in question, and so on? Or should they pester them to get permission even if other lads said "yeah man it fine"?They can ask a bureaucrat for permission to post as many times as they want.
Jesus Christ I'm going to ignore you legitimately just said "lmao they can just go out of their way and DM who knows how many staff and then proceed to take it up with them all simultaneously".They can start a DM with all the staff members in the thread, and post their arguments there.
because people definitely like being pestered on their walls, and see the above point. Wouldn't it be magnitudes less of a hassle if they just post in the actual thread and can do it all simultaneously assuming they have the actual credentials to do so?They can post on the message walls of any staff member they want to convince.
No, they can't, because we don't give a **** what happens off-site, we only care about what happens on-site, even you should know this.They can talk to staff-members off-site.
And I'm saying if people with the proper credentials, are more knowledgeable than the staff in question even, and have even been given a general ok to do so, should by all accounts be able to post instead of going through the dozen hoops you think is somehow a decent alternative.The purpose of these staff only threads, as I see it, is to distill the arguments so staff (who are expected to know a lot about our standards), can evaluate whether those arguments meet our standards or not.
No offense, but that's actively detrimental regardless of what your justification is, that isn't how you avoid shitshows (which, btw, you're once again missing the point). All I'm getting from this, and something I'm pretty sure you basically just made admission to that, is "We want shit to be extra ******* annoying to disincentivize others to post", which is how you get shit half-assed and lose vital information that might've made a major difference.We want this sorta shit to take extra effort. The point is to avoid low-effort comments that made the initial non-staff thread a shitshow in the first place.
Lad, the alternatives you gave aren't just "takes a bit longer", it's bordering on being a flat-out nuisance, it only works if there happens to be a mod that is even willing to do some of that shit, is unbiased, completely free, and even willing to do it with multiple parties in some cases.Taking time isn't much of an issue, these threads shouldn't be blitzed through in 6 hours.
Ah I see, you must've missed the part where I said I was informing mods of my posts, got the okThat is good enough, but that's not what happened here! Damage gave permission days ago, which is only applicable for one post, yet you kept commenting after seemingly only "getting permission" from someone who's not allowed to give it.
Disagreements, needing multiple middle men, a bunch of shit?Why would they need to have the same convo twice?
Except what if a Staff disagrees with them for whatever reason, whether it be ignorance, not buying it, lack of knowledge or context, or anything really? Yeah it won't be that easy, and let's not pretend staff are infallible, I've been here long enough to see some oddly malicious acts when it comes to vetoing shit. (I should make it clear I'm not going "staff bad lol", obviously not the case, goddamn a few of my favorites lads here staff, I'm just saying people be people and there's been some suspect stuff before).You're talking about verse experts being able to provide important info from the verse. The staff would just debate with that info in the thread, and get corrected by knowledgeable members in DMs if they get something materially wrong. They wouldn't need to re-debate it in DMs.
No offense, but I don't think you get the scope of what your alternatives entail.Yeah, and those credentials can come from asking a thread mod/admin/bureau for permission to post, or by making the thread yourself. I'm giving alternatives if someone doesn't want to do that, or thinks they were unfairly denied.
No, we don't care about that shit, at all.What? We don't care about what happens off-site in terms of rule violations.
I don't know a single staff member that will pretend they didn't hear arguments made off-site, and insist they be made on-wiki instead.
And I can assure you just as much has been lost to the void.A shitton of things have been discussed off-site, which has moved conversations forward.
That's why you have the ability to tell blues to **** off and delete posts brotherBut the general okay has to come from bureaus. Other than that, we want staff vetting posts one at a time, to make sure that users don't overstep their bound from just sharing knowledge about the verse that only an expert in it would know, to debating over whether site standards that all staff should know would apply.