- If it were my decision to make I think I'd target October 30/31 - the week before the next anomaly date to grenade RES orga leading up to it.

- Most of those 56 are as trustworthy as we could possibly expect anyone to be.

- I'm sorry were we talking about something?

- A little more than a week. Ten days.

- Eh, depends on what you define as "news cycle". Probably about a week, roughly.

- I suspect we felt the effects a bit longer locally.

- At a week the "we will discuss it after anomaly. Anomaly is priority" use would work.

- That seems correct. And gives us plenty of time to plan.

- I'd want to see user list before finalizing that - if a lot of RES leadership is on it the end result could be unpredictable. (Circling the wagons or mass defection)

- Grenading the anomaly with this feels dirty and cruel to all of the people who aren't engaging in this behavior and just trying to go and enjoy an anomaly

- Like I know we want to do everything we can to win, but...does this need to be paired with a strategic goal?

- It's awful enough by its own accord

- I think the deciding factors on strategy will be the user list.

- I understand that point of view... and would respond that it is a point in time with maximum strategic value but also a point in time when there will be maximum communications regionally as people finalize anomaly prep. It will be unavoidable for them to discuss it internally.

- That is true

- The other part of that being that if they weren't being naughty it they woulnd't have a problem.

- I view the bomb drop timing with the anomaly not as a method to help win but a perfect time bring more eyes upon it

- I totally get where you're coming from. Color Me jaded but I think they would do exactly the same thing. Maybe I'm Wrong in this but I simply think in terms of strategy in everything we do in this game lately because I've seen them do the same

- Our release should be neutral. No sermonizing

- It was also mentioned that it would behoove us to remain as objective and impartial as possible, treating the data for what it is - data. We can't do that and also twist a strategic advantage.

- I would concede this point if it weren't for the RES attempt to kill the Houston anomaly, and simultaneous/subsequent recruitment push for Boulder. To me, this feels more like a riposte than a dirty trick. Especially if those are the anomaly dates we're targeting.

- Also this.

- That I'm less sure about. Info war is a valid tactic

- Yeah, I don't see how this makes it better? They did a bad sneaky thing, that has no bearing on our behavior.

- I'm not agreeing that it's bad/sneaky behavior; I'm saying it would feel more like that, and less like a neutral and valid infowar/psyop move if they hadn't been playing that game as well. I don't think it's dirty/sneaky at all. Optimizing the release time to our advantage, and to their disadvantage is fair play IMHO.

- Weaponizing thr information is a way of engineering consequences for the behavior.

We know thst the behavior will not change and that the bad actors will not be banned. But we can send a message that institutionalized cheating backfires dramatically.

- It's sharp, not nasty, or foul play. We're not manufacturing propaganda.

- It might also get lost in all the anomaly static to be honest.

- Not if we do it right

- Do we know yet whether the Whistleblower is a resistance agent, or an enlightened agent who infiltrated? I think that distinction makes a difference when we present the information. In my opinion, it's better if a resistance agent shared it with us as an act of good faith rather than RES being able to reverse the spotlight on how we were deceptive in infiltrating one of their chats.

- I think this is an important point - the information released without editorial content will be impactful on its own. We can certainly boost signal around it.

- I'm having a personal ethical issue about conflating the objective problem of cheating with anomaly strategy if the goal is to get Niantic to do something about it and not just make a bunch of people super mad. I agree and am on board with doing something with the information, I just don't like when the conversation moves from "this is bad and we should make this public in order to drive positive change" to "how can we both publicize this information AND use it to our strategic advantage?" If it's literally just me that takes issue with that nuanced distinction, I'll give it more reflection time. 💚

- I think you have a reasonable point. That being said, I still believe maximum impact is desirable if the user list heavily implicates RES leadership.

- I think you have a completely valid point on this. I think that goes without question. As of today we have nothing currently to release, that might change over time I expect it will. I don't think it's just you that is conflicted by the idea. They might have just worn me down enough that I want to hurt them back. I'm open enough to admit that. Just know that everyone here I'm sure understands what you're saying

- Okay! Good. Thank you 😄

- Agreed. As good as it may feel, we shouldn't be vindictive or game information release timing strictly for our advantage.

- That said, we are in anomaly season, and it sounds like we will need to release this shortly before an anomaly happens to be occurring.

- I mean, if we were satisfied that RES anomaly leadership were not in this Slack, I think there's a great argument for releasing it on November 6th. Immediately after the anomaly.

- I think we have to release it in an organized format before anything is leaked in an unorganized way.

- Not least of which is respect for Whistle Blower.

- Absolutely. My impression was that the goal of releasing it prior to the anomaly was to maximize the attention it receives, assuming that Whistle was correct about the involvement of anomaly leadership. Disrupting actual anomaly play/planning is just another tick in the "pros" column of using that timing, and another reason it's a strategically sound move.

- If it's just a bunch of salty GHs, there's not as much strategic value or reason that releasing it beforehand would get more signal.

- The more I think about it the more I agree with @OneEyedCat I think the best time to release it maybe when everything is just ready to go and compiled. Additionally with the approval and go ahead of the whistle blower. I can't let my anger be a part of something that I feel like really just needs to go away in the right manner

- To be clear, I think infowar is valid and my intention was to use the data in order to disrupt res orga and reduce their anomaly effectiveness

I'm happy considering other viewpoints. I mean, this is why I asked for feedback and help.

- We released the day we received our information. We discussed the value of disruption briefly and agreed that it might have a negative effect on their anomaly performance. We flagged RES leadership 48 hours in advance. No action was taken, so we released the information.

- WB has already mentioned the presence of KC and Nashville POCs and a res trusted reporter.

- I think it's also worth noting that we might be getting just a little bit ahead of ourselves at this point. We don't even know what we may have yet

- Maybe Chris, but it's worth being ready, and WB has given us enough to establish trust

- Did i miss the answer to this question? I think it matters too. Sorry catching up fast between meetings,

- You're right, I guess I'm just waffling with my own personal demons. Sorry

- We do not know yet. I have avoided those kinds of questions and will continue to do so until the data is in hand.

- Again asking because i honestly don't know. But how much difference does a 10/23 versus a 10/31 release make? it seems like we will certainly be asked "how long have you known about this"

- No worries. It's interesting and difficult content to process.

- Strong reason for early release.

- There is a cycle to this stuff. Releasing it a time designed to maximize the volume and awkwardness of internal RES conversations at anomaly time would be strategically useful.

- Also the whistle blower might be less happy if we're clearly playing strategic games.

- I do this stuff for work all the time.

"We released as soon as we had completely vetted the data and the source and felt confident that we were delivering a responsible and accurate message."

- Even if we released it today it would impact 11/3 anomalies.

- Ha, OK. Recognizing and respecting expertise.

- If we didn't want to impact an anomaly it would have to be 11/6 or shortly thereafter.

- But could still have impact on the 12/2

- Anytime you're considering my ethical character, recall that I am a professional extortionist.

- Waiting three weeks seems like a stretch

- I get that part, just was not sure how much difference a few days makes. But you answered with your spin response.

- Hi, I'm a professional liar/lie detector. No wonder we get along so well.

- This is so important. I know there's a lot of relevance to the Guardian issue, but from the discussion here today if nothing else, it's evident that ENL have scraping tools being used for the same purpose. But if anomaly leadership and faction ambassadors to Niantic are involved, it really needs to be accompanied by some noise, and interfering with anomaly mechanics will do that. It's really a good thing if that Noise is more distracting to our opponents than us, especially if it's because their leadership is more deeply involved in shady shenans than ours. Of course, this strategy heavily depends on that being true.

- We are a team on this. I am not advocating any particular approach very strongly, and I'm listening hard.

- We clearly have some if-thens going here.

- We could play some really awful games like releasing 5 names a day and telling them ahead of time that's what we're doing. If you don't own up to it yourself, you will be outed publicly.

😈

- When the sinkhole opens up, you two can come stay at my place.

- The useful takeaway for now is that the WB data is decoupled for now from any digging that might be done on equivalent ENL tools.

- Liam Neeson memes would be the correct format for this, I think

- That would significantly amplify the signal by stretching it out over a long period.

- This is kinda evil and I like it.

- Who's going to pop up on the list today? Log in to find out!

- Too slow. But the entire list in equal increments over the course of a week? Maximum carnage.

- Should we register thebrokersguild.party?

- 😂

- Can you imagine how many people will be sitting on the refresh button for Google Plus waiting for that post everyday? That would be the most action Google Plus has had in its entire existence

- 😂😂 Spat my coffee.

- Our posts would become more anticipated than Krug's AMA.

- I was joking with another TGR agent about starting a twitter for this...

- Especially if you posted a companion list of people who had left the group since the prior post. Assuming it wasn't immediately completely shut down.

- LOL if each one of us does it on a different day.

- [[GIF, size 76'206 bytes]]

- How many bleeps and bloops will Semiotiq's video contain??? guess now and you might win.

- 10 +/- 3

- It would be really awesome if they had some discussions in that Slack about the res War implementation

- and/or links to other tools we may not know about

- God I hope this is real
.....17.10.2017 17:19:39, VAIN: >>unsupported service message type: messageActionChatJoinedByLink<<

- oh, gosh did you look at this one closely?

- [[Photo]]

- The prior request to the example was in France

- I did in fact catch that

- Spooky

- Yepper. Global, eh.

- This wasn't the first time I had heard of the Brokers Guild

- I had heard it was Global but I just had no evidence

- Yeah?

- Someone from Europe came to New York City and he was invited to Farms by the resistance, and somebody had mentioned something about Brokers Guild that one of our guys overheard

Prev
Next