- HA

- what

- wait

- It would be hilarious though

- ::dancing on their graves::

- dont fuck with my feels

- no fake news today

- lol

- This would be fantastic!

- holy shit

- its real

- it is?

- dude, thats awesome

- That's nuts

- Remember not to poke around right now. They still probably have server logs.

- it's real

- Think bans could be following? Too much to hope for

- I've been looking for this and I can't find it. Do have the forward or know how it was marked? I tried pullquote

- so wtf

- Evidence, please

- but how could that be?

- Taking down a server is like a spoofer creating a new account.

- they fold and reopen?

- Well is it real that Niantic has control of it or are they playing us now that they know we know.

- load the page. riot.one shows it

- niantic cant get control of a url that fast

- Yes, I believe in the HTML

- someone inside had to do it

- But yeah

- yeah

- Depending on who owned it they could have repointed it today.

- No evidence that Niantic did it

- i bet it was "you down this now or youre all fucking banned"

- but it makes it look like Niantic is in control of it and taking action

- BUT if they control who owned it it implicates Niantic as complicit.

- What Kim said

- Just buys time

- Add that to having an employee on the list...

- Yea, it could be show

- Anyone have a DNS tracker to see if it has changed?

- Muddies the waters

- Niantic didn't have enough information to credibly make this threat.

- Yes, they did.

- You want to tell us exactly what happened?

- I missed it.

- Did you give them the files?

- preview access to the site

- Charlie will have a hell of a backlog to read.

- What's done is done. I think I would've given the group here a heads up tho

- NiaOps contacted me yesterday, saying that responsible release of the information to them would be the best way to ensure action. Charlie concurred and we gave them early access.

- TTL on the record for riot.one is 5 minutes. Doesn't mean anything itself as I use 5 minutes too but they could change the IP it points to quickly and put up a splash then move the interface to a new URL.

- Ah

- And it appears to have leaked to the RES...

- WOW. But yeah. I understand why, but I would have liked to know.

- Same

- And I assumed when it was said you were contacted, you meant recently as in today. Wow

- I see that. At the least notice that it was happening.

- probably a blown call there. im sorry.

- How did they know to contact you?

- i was the first to message krug

- THIS is what concerns me

- i believe

- Ah, ok, true

- What's TTL?

- If niaops is actually moving on this then that's more than I even expected to happen

- I don't know, I think it shows a direct link from Niantic to the RES - something my tinfoil hat has long suspected. Unless it is a legitimate Niantic takedown they'd have to explain how the news got to the RES.

- Well yes, we should have been told but I'm happy as hell if this means Niantic is actually DOING something

- Time To Live how long the DNS record should be cached or used without checking back with the server

- Speculating entirely, was their employee an admin? If so, they could have demanded it in exchange for keeping him employed?

- Why give a release time of noon today if you had let Nia in on it? It had to be known they'd blow it before then

- so heres how i see it. Niaops has the list, nia employees are on it, angel investors are on it.

- the ppl whose jobs depend on this give it up right away

- so then now what's the point of waiting to release - once Charlie joins the living

- They should have frigging thought of that before getting into it in the first place!

- So are we not doing the posting on G+ at 1 pm ET?

- At any given time there are multiple informants between Niantic, ENL, and RES. See previous conversation re: 50 people can't keep a secret.

- They made no promises, and we were a little sleep starved. I think charlie would have still said wait because its what we said wed do

- I am happy i decided to not work today.

- I don't mind a 1p release but we have to be very careful Niantic doesn't get the lead on this. That was my fear in going to Krug.

- can someone text or call charlie some more

- lol, good point.

- I still agree with 1pm unless Charlie joins us sooner

- This. They moved first to get a head start. Plain and simple

- If damage control is shutting this whole thing down

- then im ok with damage control

- Am I a pessimist in thinking this is like a terrorist cell...... kill the head of the snake and another snake appears...... type action...... riot down now..... but riot2.0 starts later tonight???

- yes

- Niantic isn’t the enemy. There is no course of action Niantic can take that hurts the release.

- With more paranoid security.

- I'm with ya

- Heh, tried to make it yesterday. :)

They have to somehow distance themselves from it and DAMN fast because they're essentially connected.

- This.

- They could publish a statement that this is all okay with them right now and the release is still effective:

- Yes, I'm glad they are taking action, but it has to be more than this. This has to be only a first step.

- Yup

- that's what I'm worried about. But, I guess, cheaters gonna cheat.

- Coming online now.

- i see it as this: if nia actually took control of the url and WB saying that the folks in the chat are like "oh, riot is down" . nothing out of the ordinary

- READ BACKLOG!

- AND FAST>

Prev
Next