unforum

[OTPGwraspe]

A minor correction to the previous post by bobdamnit, 3033090004 isn't playing Emtanon history, it's playing a piece of music with an FSK transmission at the end which reads as below;

CQ BRAMBL
WE THINK ABOUT YOU EVERY DAY. YOU ARE BEAUITFUL AND SPECIAL TO US.

[bobdamnit]

[morningcoffee]

Nothing new to report. There are no changes on any numbers. AS27 messages continue to be "0 0 0 0" daily.

For the Milford number, we've tried inputting 150 different numbers into it as "employee identifier", gone through every old message and the entire old thread to look for an employee number, and nothing we've tried has worked. We are considering an attempt to bruteforce the Milford system by wardialling it with every possible number.

[bobdamnit]

My opinion might not matter much because I can't be in the main discussion all the time, but I have a few hours under my belt on this ARG, and I'd like to voice it.

Personally, I'm against it for a few reasons I will outline below.

We knew this was coming. I haven't been active for a while, but I followed it on the sidelines and even I knew it was coming. We have been locked out as promised. This is simply a corrupted bootloader and we need to figure it out.

They switched to the Milford system. OK, that's fine. Now we need an employee identifier. OK, that's fine too. Something tells me we have the information we need to get the EIN. We are just overlooking it somehow. The way this has gone, even attempting hasn't gone unnoticed. If we can't figure it out, hints will drop after a while. PM's have been pretty consistently helpful about this, truthfully.

We've been in longer lulls than this. Impatience has proven time and again in this ARG that it doesn't help. The last time we bruteforced the Agent System, we were down for months. Yet we held until it came back almost 3/4 of a year later. A few weeks/months of the Emtanon history/boss song aint squat. And to be honest, would we have been down that long if bruteforcing wasn't attempted?

As of now, Milford might be our only and last hope to obtain access to their systems again. Seriously, what if the black book with a buttload of hex was all a friggin EIN? Then we go bruteforcing Milford and make the PM's angry because we were just bad about transcribing some hex to figure out a puzzle.

All I'm saying is that we need to really consider our options before we just go knocking down doors.

[CrAzYPiLoT]

I am not an experienced agent, but if my opinion matters, I say no. With all the downtime this seems like just another holdup for whatever reason PM has. I don't want to make a longer wait out of all this.

[supermidas]

I too am against the bruteforce, from what I have read it seems like it will just piss of the PM's and make us wait longer. The numbers are becoming active again and I say we should try a different route of figuring it out.

Just wanted to throw my 2 cents in

[Xkeeper]

Given that nothing has happened for, indeed, weeks, at this point I am leaning towards just going for it. There has not been any actual development in a while other than this empty prompt with numbers.

[TonyTwoFish]

I don't think the system is "real" in the sense that it would make any kind of system malfunction. I believe that every error and downtime we've had is just PM biding his time until he can come up with something/get off of vacation.

[L0j1k]

We have had regular, seasonal downtime like this every year since it started, except for 2012. Every year since has had this post-melter seasonal downtime that lasts some months until after the New Year. OOC it could just be that PMs don't have the time for OTP22 during the holidays. IC I'm not sure what their reasoning is, but this long silence is not unique. And maybe I should remind everybody of the last time we tried a bruteforce during downtime. We brought the system down and it stayed down for months. OOC that's what happens when you blow through PMs Twilio budget placing ten thousand sub-one-minute calls to [system like AS36].

[bobdamnit]

I agreewith L0j1k, but it doesn't matter now because Milford is now:

"You have reached a non working number, blah blah blah".

So wardialing it is out lol.

[morningcoffee]

The Milford number has come back up after a brief outage.

The Milford system (tape retrieval system) has been accepting input for some time but has been largely ignored.
People can help by entering numbers into Milford (302-725-0004) to try and find an "employee number" (record all calls!!) and then listing what they've tried here: http://piratepad.net/XRvu3A6FKu

You can look through old messages, ExcitingBooks covers, WORM books, old numbers etc. for any potential numbers to try if they've not been tried before or you can even just enter random numbers. Just make sure you record your calls and add any number you try to the piratepad. Thanks!

[morningcoffee]

A couple of things to report.


Firstly, we have a working employee number for the Milford tape system. It was found with this...





Yep, Robby left a note on our piratepad with a working employee number. Thanks RB


The system then asks for a tape number. Tape numbers that have been mentioned in the past (22100 among others) don't work. We've tried a few others but each one gives "tape load error". We'll keep trying.
There is a new piratepad where you can enter tape numbers you've tried: http://piratepad.net/M9A7sFUnlj
Don't forget to always always record your calls to any OTP22 number or system.


Secondly, after we finally accessed the tape system, AS27 updated for the first time in weeks.

Sequence 40.333 -

[bobdamnit]

You know this implies RB reads the thread.


HI BRAMBLE! WE LOVE YOU!

[morningcoffee]

New AS27 message, sequence 40.334 -

[TonyTwoFish]

AS27 40.335