- Did your portals there go down?

- I'm thinking he looked you up, saw where he had to go, and was just also looking up the zip code in the area to see what else he could pop while he was there

- [[Webpage]]https://en.m.wikipedia.org/wiki/Whataboutism

- Backlogged ... ish, finally. Req’d access.
If this is the same tool I was shown last year at a glympse, it’s referred to as a hive mind for them. As well as that, there should be an associated map that ties into one’s requests.
I request X agent’s details
It is fed into slack & also into a map (i think through an iitc plugin)

- Possible, or queried a list for another more local broker. This query ostensibly happened within the last 48 hours. On Sunday, Wanderer68 (screenshot also exists in our files of him checking his GH score) took out a portal in Central PA that was slightly older. So it would make sense that they would check on these, as they're next on the list and would show up on my "oldest owned portals". But they have many weeks to go still before they mature fully, so no idea if they'll be taken now or wait until 147 days, etc

- Your boy is on there, obvs

- Hes the one who showed it to me.

- I figured

- Req’d access, btw.
I wanna see if a few more are on there.

- Tollermom

- Heh .. im seeing her today

- Will make 0 word of this

- Yeah. Sinisterkitten should be in there too. Likely maggie.

- Wow. All of my state BRRN reps are in it. And to think I thought it was somethin of moral stature.
Pfffft.

- We need a gossip channel

- Sorry for the minutiae, it's just that a bunch of our current usage screen shots involve Res from my area. I'm done. ☺️

- To not distract from actual work

- Point is, we need more screen shots .

- That was my 2 cents of social work.
Yeah, that’s THE network / hive mind. Work it.

- Id like to see that fall.

- The WB needs a UPS box and I'll pitch in for Glenlivet 25.

- I know I am in the 130s right now, so if they haven't already looked me up in taking my data they will soon

- I would kill to get that screenshot

- I'm garbo, lol

- Let's use this chat to talk about how mad we are

- And leave in here for business

- [[Photo]]

- Sorry, upgraded to supergroup and it changed the link

- On Niantic: we're not making demands of them.

- Also, not mad--talking about strategy and whether we should delay the plan of release at all based on Nadia's point of view. But if you'd rather keep this strictly to webiste building/spreadsheet building logistics, that's ok too.

- We're saying "hey, we're about to release this information we just got. We noticed one of your employees used this tool; as a courtesy we wanted to give you 48 hours to formulate any public statement you may wish to make."

- @Strandit yeah, that came through clearly to me. It's also about letting them potentially speak to the devs involved and do something internally before we release.

- Yeah, but you don't tell them that, you don't couch it as "we caught you."

- for sure

- This is why the whole evidence thing is irrelevant. You don't need more evidence; you're warning them about the shitstorm, and there's plenty for that.

- I wouldn't bother with the LinkedIn material.

- lol, fair point.

- In fact I'd delete it — it's doxing.

- But doxing is so sweet

- I agree that that should not be published

- Power words everywhere

- I absolutely would not give anyone early warning especially Niantic. It provides far too much opportunity for them or the res to try to get ahead of this.

- Just sent requests for the pieces I can't see yet.

- What can I help with? Do we have screenshots that need the text pulled out of them? Our software has OCR capabilities...

- If someone's IRL job is likely to be on the line, I think a courtesy heads up is a reasonable thing to do.

- @Aneristic, shall I update the Bot Members List spreadsheet if I have additional information?

- @SKSM5966 yes

- 👍

- Participating in a group that explicitly violates the terms of services of your employer’s application creates a foreseeable event that your employer could find out and be unhappy about it.

- IMO there’s too much risk in letting someone else get ahead on the story.

- It's also about maintaining good relationships with Niantic.

- Enl have spent a lot of time telling Niantic they're making a mistake recently.

- It's accurate

- this is a place where Niantic hasn't made a mistake directly.

- Yes it is.

- Is that true, though? Wouldn't employee activity be monitored?

- And... it's the right thing to do. It's like security disclosure; you tell companies first so they have time to fix it.

- TBH I don’t trust Niantic. It will embarrassing and they’ll want to control it.

- jesus, I'm scared of your workplace. 😂

- when there's an expose that's about to happen in the news, journalist usually call the person in question up for a quote for a comments before it's published. I think it's only fair that in that same sense of seriousness of what we are going to be publishing in terms of this person's livelihood, that we do the same I get what Scott is saying, so maybe we only give them a certain amount of time with notice

- Yeah, nobody's watching what the kid does on Slack.

- We're not saying "you can stop this release," we're saying "something that will make people mad at one of your employees will come out in 48 hours."

- This. If you ever want anything but the most acrimonious of relationships with Niantic, you have to give them the basic courtesy that suits this circumstance

- That’s pretty vague. If you’re hellbent on telling Niantic first then perhaps sending it to them at 8a Pacific with a release of noon is reasonable. They’ll have four hours but won’t be able to get far enough in front to control the narrative.

- Yes, what would be the way to get out in front? Declare that scraping is not against TOS?

- Isn't telling Krug the same thing as telling Niantic or do you mean a second message?

- Side note — adding another tab for listed brokers.

- A public release from Brokers Guild that some bad actors co-opted their chats for cheating. They are very upset and will root it out.

- I don't know that we should put this all on krug's shoulders. There has to be somebody else to reach out to as well right?

- Boy, that would be *fascinating*.

- Learning that Niantic is willing to leak that hard to a Res organization.

- Agreed exposing a wrong doing that may jeopardize one job when it violates employer policy is not my concern, it is a position that the employee put themselves in and we cannot compensate action for that

- One of their devs is in it. Do you think he wouldn’t tell them the instant he knows?

- If they do that, it just proves what we're really up against

- I don't even think it mutes the impact much.

- I'm not sure there's a viable way for anyone with advance notice to control the narrative.

- It's not like you can mitigate a boatload of screenshots and documents.

- I mean, I can't even conceive of a "worst case scenario" where they could usefully circumvent a raw data dump. Maybe I'm short-sighted.

- I think there’s too much risk to lose the initial impact of the message. There’s a certain benefit to catching them flat footed and watching the response.

- Like "some bad actors" doesn't work with a 900 person member list.

- Eh, I'd caution you against letting bloodlust rule your decisionmaking.

- And that's coming from someone who *really* loves to light shit on fire.

- but y'know

- I like the cut of your jib

- [[👶 Sticker, size 49'844 bytes]]

- It’s not bloodlust. I occasionally wear the tinfoil hat that has Niantic in the bag for the res. Finding a Niantic employee on the user list is troubling and leads to questions about how much information was flowing there. Giving advance notice gives them a chance to come up with something to try to mitigate it.

- He lit his jib on fire weeks ago

- What do you think they would do that would stop the momentum underway?

- Yeah, I'm trying to give that fear an honest shake, but I can't creatively conceive of something that would mitigate it. Help me out.

- Not to change the subject, but this is a legitimate story for a Gaming website like Kotaku.

- That is absolutely worth thinking about when we go to publish

- For as many eyes as we can get on all of our G+ posts, they'll have it beat in the first 5 minutes

- Impact like that would be tremendous

- This is pretty esoteric for general audiences, though

- The people that read Kotaku would eat this up

- I'd pitch it.

- Lol, publish it to æ

- Is that still a thing?

- If Kotaku actually runs with a post on this, other websites specifically catering to gaming culture would also pick up on it