last day (24 days later) » 
16:00 - 19:0019:00 - 00:00

user102937
16:23
@Catija: Is this the new normal now? Make unilateral changes, ask for feedback later? (or perhaps, not even bother?)
7
The fact that the post exists for the moderators' review kinda belies that, @RobertHarvey
user102937
Were the post notice changes run past the moderators first?
@RobertHarvey No, that's the old normal. They are actually sharing stuff now, which is certainly a step in the right direction.
2
user102937
@Catija I'll rephrase my question. Is the new policy to put proposed changes to the platform into the Mod Teams first for review? Or was that only done as a courtesy to the mods so that they don't get blindsided by their communities?
2
user102937
@terdon Someone leaked a Mod Teams post onto meta, using a disposable account.
16:33
I know.
user102937
Then you also know what I'm talking about.
It did say the change would happen the 13th of November, so the mods have more than a week to give feedback, even if the post didn't ask for any.
@RobertHarvey We do. And also, once again, a leak is only presenting one side of a story and clearly had an agenda.
4
..... Think it is time to go and buy some popcorn. Seems the next episode is about to get aired.
2
@RobertHarvey FWIW, it only got 11 (or so) views before it got zapped.
user102937
16:37
Most of them from this room, apparently.
It's a rough gauge.
user102937
I'm not here to stir up any more trouble. In a way, I'm glad that SE has decided to focus on the site mechanics for awhile, and the way they are doing seems to be really constructive. I just wish they would consider finding a way to clean up the Superfund site, that's all.
@PM2Ring It was also archived 8 seconds after being posted. Might've gotten more views after it got nuked. /shrug
@Tinkeringbell more like rants, but yeah... people are not happy.
@Hitodama You might need to wait a while. I assume nobody's going to perpetuate the leak in here.
16:42
@RobertHarvey then can we please drop it? We'll have plenty of time to discuss it, trying to do so now only stirs up trouble.
@Tinkeringbell up to you but might it be better if we move the previous discussion elsewhere?
Hey :)
20 messages moved from Tavern on the Meta
@Rubiksmoose hey! I took the advice from @Tink and moved that discussion here
Don't make it blow up ... cheers all
2
room topic changed to Room for a future discussion ;): The future is here [chat] [discussion]
user102937
Oh, look. A new room. :)
16:56
Yes, and you have power here ;)
user102937
Ah, nostalgia.
For the record, the leaker is obviously either deliberately misrepresenting things or has a vastly different take than every other mod I've seen talk in the room.
6
waffles
So, readers, take note.
user102937
Well, it might be worth SE's while to have an, erm, discussion with the folks in there about leaks. As in, don't.
16:59
Yeah, I assume the so mod team should be kept as private as the TL transcript.
@RobertHarvey That's putting it mildly...
@RobertHarvey We're just as pissed about it as SE could be I would think so it's not just SE that wants a ... discussion.
I really don't understand why anyone would do this. It seems like petty malice for no imaginable gain.
I don't get it either.
Also, @RobertHarvey, sorry for trying to shut you down there, but I really think that discussing this in the Tavern would be very counterproductive.
user102937
17:02
NP
Plus, I keep forgetting you don't have your diamond anymore. D'oh!
And honestly, the range of emotions on this change I've seen expressed ranged from meh, to full support. This shouldn't have been dramatic, and it needn't have been.
mag
mag
what happened in general
I was cycling home when the tavern discussion started
@mag something was leaked from the SO Mod team
mag
mag
sigh
really?
17:06
@Rubiksmoose Upgrading the CC license from 3 to 4 shouldn't've been dramatic either... This has way more potential for controversy.
@PM2Ring It really doesn't.
Doesn't mean it's not going to get it, but at it's core, there is no controversy here, it's all being manufactured.
Do I need to remind anyone about the bad vibes that arose with Documentation?
@Zoethetransgirl very risky business posting that link.
I have no idea what that is TBH. All I'm saying is that there's nothing controversial here.
17:14
@Rubiksmoose Fair enough. I guess I can't be more explicit without mentioning the topic of the leak.
@Script47 meh
And by "here" I mean in the actual facts. The leaker's controversial opinions/suppositions are not supported by any facts and seem to have been designed to create drama where there otherwise would be none.
@Zoethetransgirl I admit I kinda wish you hadn't. There really isn't any benefit I can see to starting drama over this before its time.
I didn't notice a link posted
it was in the comments
17:16
if I hadn't posted it, someone else would. I got notified about its existence thanks to the archive.org plugin, and given the link repairing activities of a lot of network users, I highly doubt I'm the only one using it
Is it ok to post the URL for the benefit of Mag & other 10k+ people who didn't see the post? I still have that tab open.
Rather not..
There's an archive plugin for SE?
No, there's a general archive.org plugin
Not a problem.
17:17
That deleted post didn't simply leak the information. It tried to frame the situation in a particular way.
Thank you :)
I mean... if the "source" it provided is the source, the post doesn't need to do much framing.
@Raedwald It straight-out manufactures things. The more controversial aspects have no factual basis and are purely speculative and designed to create drama.
12 messages moved from Tavern on the Meta
17:19
WTH is that
@M.A.R. What Tinkeringbell said :)
2 messages moved from Tavern on the Meta
@Thefuture
Wait, no, OBJECTION. They're not pingable.
Never been in the room :)
@KevinB And yet, it did.
Not to mention the "source" is also completely devoid of the context in which it was written which was in response to previous feedback.
17:33
I knew I wasn't going insane...
Exactly
I'm just nodding in affirmation so people think I know what they're talking about
@Script47 Whoa there, we haven't proven that yet. Just not in this case ;-)
18:05
Oops. They tried it again. This time it lasted about a minute.
Lol
This is honestly looking pretty sad on their part. What's the plan here eh?
I assume they want to stir up trouble.
I guess they're upset that SE want to roll out yet another change. Sure, they're showing the mods, but I get the impression that the change will happen, and that's not up for negotiation.
@PM2Ring I'm not sure any mods would have wanted to convince them not to change it. Well, I guess there's at least one. Seems like a fairly minor change overall, and the reasons for reverting it seem pretty solid.
This looks like a bit over the top resistance to change.
@Rubiksmoose Ok. Yes, it's a reversion. I'm not 100% convinced that it should be reverted, but it doesn't bother me too much. And my objections are impossible to state without spilling the beans.
18:21
> I'm not 100% convinced that it should be reverted, but it doesn't bother me too much.
I think a lot of people fall along this line (including me, really).
Regardless, it doesn't seem like the change itself that is trying to be weaponized in the leaks.
18:43
@Rubiksmoose True, it's not the change itself they seem to be complaining about, it's the alleged motivation for the change.
The worst thing about the leak is, from SE's perspective, they were punished for communicating the change to moderators
Which doesn't encourage future communication
Yup. It's honestly infuriating. SE is finally attempting to make some attempts to communicate with us (even if not in the way we want exactly yet) and them some doofus goes off and decides they don't care about any of that.
But what should we punish then
I mean, if the announcements were going to go public soon, then we can let them know loud and clear once that happens
I have no doubt the community will let their voices be heard
16:00 - 19:0019:00 - 00:00

  last day (24 days later) »