[morningcoffee]

New AS27 message.

June 15th, sequence 39.165 -

Quote:

ENABLE POSITION REPORTING SYSTEM.

And new black OTP message.

18266

Quote:

Z 15071152Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/MXP20// SUBJ/MXP20// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ J, STILL NO BOOK RECEIVED ON MXP20. THEY ARE NOT ANSWERING MY CALLS. NEED HELP WITH THIS ONE. -RB //

We also left a new QX as Ai, simply saying that there may be difficulty with J's request and asking for further info about what's needed.

[Xkeeper]

I live in Las Vegas, so as long as it doesn't involve something stupid like hiding out on top of a mountain trail, I'm game

[morningcoffee]

Their mention of being "near the airport" got me looking at satellite images of Svalbard airport and surrounding area. Doesn't this look pretty similar to the SSTV image we received the other day?








The SSTV from HF:

[morningcoffee]

ytsemaddy wrote:

Just for fun, I checked to see what kind of Region 9 Las Vegas would be in. It turns out it's part of the standard federal regions grouping: "Region IX: Arizona, California, Hawaii, Nevada (American Samoa, Guam, Northern Mariana Islands, Trust Territory of the Pacific Islands)" Looking at the scrambled sat image, plus the mention of Las Vegas, the closest body of water would be Lake Las Vegas. Nellis Air Force Base and the usual civilian Las Vegas Airport would match the comment about "near airport" but it looks like the lake vs either airfield is way too far to go on an ATV... And SAR Activity, at least in terms of paperwork, is a "Suspicious Activity Report" Activity. Alternately, Search and Rescue.

Yep, they've been using the federal regions for drops etc. for some time now. Sometimes we've had an idea of where a drop will be in advance of getting coords because they've mentioned a region in advance (like mentioning region 10 in the phone conference before we got the Alaska drop info).

I don't think the other messages refer to Vegas - they are almost certainly discussing Svalbard. The message to Ai is separate to the conversation between J and A. J just happened to drop it in the middle of a string of messages, just to be confusing XD

Also worth noting that on Ai's instructions agent code (16041) it now says "18264" before giving the DROP2 TBD stuff, so they're pushing her towards that message. We're gonna have a think about how to respond as obviously, Ai's not gonna be showing up

[ytsemaddy]

[quote="morningcoffee"]New black OTP messages.


18264

Quote:

Z 14070106Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/AI// SUBJ/AI// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ WE NEED YOU IN REGION 9. SPECIFICALLY, LAS VEGAS. MORE SPECIFICALLY, WE ARE WATCHING YOUR EXPENSE REPORTS. WHEN WILL YOU BE ABLE TO ARRIVE? RESPOND VIA QX. -J //

Just for fun, I checked to see what kind of Region 9 Las Vegas would be in. It turns out it's part of the standard federal regions grouping:
"Region IX: Arizona, California, Hawaii, Nevada (American Samoa, Guam, Northern Mariana Islands, Trust Territory of the Pacific Islands)"

Looking at the scrambled sat image, plus the mention of Las Vegas, the closest body of water would be Lake Las Vegas. Nellis Air Force Base and the usual civilian Las Vegas Airport would match the comment about "near airport" but it looks like the lake vs either airfield is way too far to go on an ATV...

And SAR Activity, at least in terms of paperwork, is a "Suspicious Activity Report" Activity. Alternately, Search and Rescue.

[morningcoffee]

New black OTP messages.

18261

Quote:

Z 14061428Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/ROUTE// SUBJ/ROUTE// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ GOOD MORNING, HOW ACTIVE IS THE SURROUNDING AREA? H1 IS A DIFFERENT STORY, BUT WILL THE ATV BE UNUSUAL FOR THE AREA? THE BOAT? -J //

18262

Quote:

Z 14065342Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/ROUTE// SUBJ/ROUTE// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ ITS THE SUMMER. THE WEATHER IS NICE. PEOPLE ARE UP ALL HOURS RIDING, SO WOULD NOT BE UNUSUAL FOR LATE NIGHT ATV ACTIVITY. -A //

18263

Quote:

Z 14065937Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/ROUTE// SUBJ/ROUTE// /FORMAT/OBJ/00001/ASCII-/ /OBJ/00001/ PLEASE EXPLAIN THE LOCAL PERCEPTION OF H1 ACTIVITY. -J //

18264

Quote:

Z 14070106Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/AI// SUBJ/AI// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ WE NEED YOU IN REGION 9. SPECIFICALLY, LAS VEGAS. MORE SPECIFICALLY, WE ARE WATCHING YOUR EXPENSE REPORTS. WHEN WILL YOU BE ABLE TO ARRIVE? RESPOND VIA QX. -J //

18265

Quote:

Z 14070726Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/ROUTE// SUBJ/ROUTE// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ ITS NOT UNUSUAL. NEAR AIRPORT. SAR ACTIVITY IS COMMON. MILITARY ACTIVITY ALSO COMMON. IT WOULD TAKE A WHILE BEFORE ANYONE WOULD BE CONCERNED. INCLUDING NO. NO AIRSPACE CONCERNS. -A //

[TonyTwoFish]

bobdamnit wrote:

To be honest, the PM has never made a mistake like that. I'm more inclined to believe that the message you intercepted is nothing but a test message or that the means of your decoding were funky. Someone should definitely try before we call it the PMs problem, because there are definitely mistakes. However, the PM is indeed only human. Mistakes are bound to happen on both the coded and the decoded side. Also, half the message looks correct, and half does not, which makes me think the PM is either getting sloppy or your method of decoding was off a bit. Then I saw that the rest of the messages were decoded perfectly, so I don't know. How can one message be so far off, but later messages decoded the same way are perfect? Either way, a second opinion can't hurt. Thanks for the update Tony!

Thanks bob, went back and listened and found that what sounded like 100 35 was actually 135
This is the correct message
18259

Quote:

Z 13201723Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/ROUTE// SUBJ/ROUTE// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ VERIFIED DOCKING, ROUTING AND LANDING LOCATION. THIS WILL WORK. WE'D NEED TO BE FAST WITH H1 THOUGH. IT WILL GET A LOT OF ATTENTION FAST. -A //

[bobdamnit]

To be honest, the PM has never made a mistake like that. I'm more inclined to believe that the message you intercepted is nothing but a test message or that the means of your decoding were funky.

Someone should definitely try before we call it the PMs problem, because there are definitely mistakes. However, the PM is indeed only human. Mistakes are bound to happen on both the coded and the decoded side. Also, half the message looks correct, and half does not, which makes me think the PM is either getting sloppy or your method of decoding was off a bit.

Then I saw that the rest of the messages were decoded perfectly, so I don't know. How can one message be so far off, but later messages decoded the same way are perfect?

Either way, a second opinion can't hurt.

Thanks for the update Tony!

[TonyTwoFish]

18259

Quote:

Z 13201723Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/ROUTE// SUBJ/ROUTE// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ VERIFIED DOCKING, ROUTING AND LANDING LOCATION. THIS WILL WORK. WE'D NEED TO BE FAST WITH H1 THOUGH. IT WILL GET A LOT OF ATTENTION FAST. -A //

I am pretty sure the mess up is on their end. I listened a few times. Someone else should try just to be sure

18260

Quote:

Z 13202338Z JUN 14 SECRET//PRJMLPL//75X5 MSGID/// SUBJ/// /FORMAT/OBJ/00001/ASCII// /OBJ/00001/ /? EXIT QUIT ? Q /Q +++ NO CARRIER //

39.164

Quote:

PROVIDE REPORT ON ROUTE FEASIBILITY SPECIFIED IN MESSAGE ON COLLECTOR 1 .

[drawbars]

Maybe Julie is J...


NOT FUNNY.

[bobdamnit]

So i called the Vaughnsville Telephone Company.

I explained that we are playing an online ARG (She got excited at this, like she plays them too!) and that it involves telephones. I explained how we think that one of the numbers we call are from their telephone company. She said

"Sure, what can I do for ya?"

and I replied

"Can you look up the owner of that phone number?".

She asked for the number and i gave it to her. She looked the number up and said that they don't own that number. Their numbers start 419-646-3XXX and end in 419-646-9XXX. She even went on to explain that she's never heard of someone having a number ending in "0004" and how unusual it was for us to be contacting a number like that. She asked what else she could do, and I asked if she could point me in the direction of someone who could help us. She said (and I quote) "I honest to god have no idea where to even begin with that. There's probably nothing I can do to help you out there. I'm sorry.". I politely thanked her, and we disconnected.

She was very helpful and willing. Thanks, Julie from the VTC!

[arthurdent11389]

Keeping an eye on Exciting Books:

The Jun 9, 2014 and Jun 10, 2014 entries

Creeping Numeralism: A People's History of the Anti-Digit Dialing League
pic.twitter.com/IOXzerdhEZ

and

Creeping Numeralism: A People's History of the Anti-Digit Dialing League [bis]
pic.twitter.com/GZLmnBxUWe

both offer so much reason to believe that there is a hidden message encrypted.

First, the capitalisation of the first 2 letters in all the random names. Put them together and then solve using simple letter substitution ? A lot of work if no message there - I wish creator would have changed the ISBN or bar code to hint when a message is in the cover.

Second, the "dimming" of the second cover might indicate steganography is being used.

[morningcoffee]

The SSTV image bobdamnit linked on previous page. Could this be Svalbard? Looks like a snowy landscape...



---

New AS27 messages.


June 10th, sequence 39.160 -

Quote:

ALL AGENTS, ON INSTRUCTION RECEIPT, EXECUTE.

June 11th, sequence 39.161 -

Quote:

ALL AGENTS, PROVIDE RESULTS INTO COLLECTOR 1.

June 12th, sequence 39.162 -

Quote:

ALL AGENTS, READ PAGE 45, LINE 1, 2, 3, 4, AND 5. READ 6 AND EXECUTE IF REQUIRE.

[Xkeeper]

There's also ABISM on 17001, 17002, and 17004, which is all (to my knowledge) just "ERROR ==>". 17003 has the usual ABISM tune message.

[bobdamnit]

New HF was broadcast today. We were ready for it. (Thanks Tony and Morningcoffee!)

Link to audio: http://dialer.otp22.com/2014-06.dir/2014-06-11%2016-00%20UTC%20-%20303-309-0004%20-%20150120587%23.wav

Oddly enough, it wasn't just a random string of numbers that we don't know what to do with! It was an SSTV image that Tony has managed to get fairly clean. We currently do not know what it means or even where it is. Link to image: http://imgur.com/ZKPZJHB

I found ABISM on agent codes 37, 38, and 39. User Xkeeper has been cool enough to decode these. They are test messages, and here are the messages:

37: VERSION 2.1
38: 1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ
39: FIXME.FIXME.THIS IS BROKEN

Thatisall.