3PGroupwareManager: Difference between revisions

From Perplex City Wiki
Jump to navigationJump to search
m (Fixed word wrapping in pre.../pre blocks)
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Season1}}
== The Website ==
== The Website ==


[http://www.therecedaapproach.com/remembrance Groupware Manager] was found on the [[22-OCT-05 | 22nd Oct]] from the live event/online support.
[http://www.therecedaapproach.com/remembrance Groupware Manager] was found on the [[22-OCT-05 | 22nd Oct]] from the live event/online support.
For more information on the people discussed, See: [[3PDossier]]


=== Auditor ===
=== Auditor ===


The Auditor page held a short piece saying that in 48 hrs it would go live.
The [http://www.therecedaapproach.com/remembrance/auditor/ Auditor] page held a short piece saying that in 48 hrs it would go live.


On Oct 24th at ~6:00pm BST the site changed.
On Oct 24th at ~6:00pm BST the site changed.
Line 11: Line 16:
It now contains the following text:
It now contains the following text:


<pre>
{| border="0" cellpadding="10" width="70%" style="border: 2px solid #ddddff;" bgcolor="#f3f3ff"
|<pre>
  Select an Account  
  Select an Account  
Select an account to the right to view the enabled modules.
Select an account to the right to view the enabled modules.
   
   
  Enabled Modules   
  Enabled Modules   
Line 37: Line 41:
  *alarms/reminders   
  *alarms/reminders   
</pre>
</pre>
 
|}
----


On the right of the page is a drop-down list of usernames (O1 to O8) referring to each of the operatives (excluding V and the "Big Boss").
On the right of the page is a drop-down list of usernames (O1 to O8) referring to each of the operatives (excluding V and the "Big Boss").
Line 44: Line 47:
Each Operative's page requires a different password.
Each Operative's page requires a different password.


----
== The Passwords ==
''Notice: those are Letter Ohs, not the Number Zeroes.''


=== The Passwords ===
O1 - password
O2 - star
O3 - power
O4 - dream
O5 - joy
O6 - head
O7 - wind
O8 - watch


<pre>
These were all determined based on information from [[The Receda Trail]].
O1 - password
O2 - star
O3 - power
O4 - dream
O5 - joy
O6 - head
O7 - wind
O8 - watch
</pre>
 
----


== The Emails ==
== The Emails ==
''Much reference is made to [[The Receda Trail]] in these messages.''


=== Emails To and From O1 ===
{| cellpadding="10" width="70%" style="border: 0px; background: OrangeRed"
 
| [[Emails To and From O1]]
==== Inbox ====
|}
 
<code>
Date: 19 September 2005 2:49pm<br>
From: O2 <br>
To: O1 <br>
Subject: London here
 
 
 
 
Checking in.
</code><hr>
 
<code>
Date: 23 September 2005 11:18pm<br>
From: O3 <br>
To: O1 <br>
Subject: On
 
 
 
 
Toronto online.
</code><hr>
 
<code>
Date: 29 September 2005 11:57pm<br>
From: O4 <br>
To: O1 <br>
Subject: Budapest
 
 
 
 
Check.
</code><hr>
 
<code>
Date: 30 September 2005 4:15pm<br>
From: O5 <br>
To: O1 <br>
Subject: Checking in
 
 
 
 
New York has come online
</code><hr>
 
<code>
Date: 5 October 2005 3:34am<br>
From: O6 <br>
To: O1 <br>
Subject: Moscow ready
 
 
 
 
Checking and and waiting for orders
</code><hr>
 
<code>
Date: 5 October 2005 4:38pm<br>
From: V <br>
To: O1 <br>
Subject: Problem
 
 
 
 
Which keywords?
 
V.
</code><hr>
 
<code>
Date: 5 October 2005 4:55pm<br>
From: V <br>
To: O1 <br>
Subject: Problem
 
 
 
 
Please calm down. I was not aware of them either; however, it is your role to check for such possibilities. You should have detected them earlier. At least we found out now, rather than later. Are they aware that we know about them?
 
V.
</code><hr>
 
<code>
Date: 5 October 2005 5:16pm<br>
From: V <br>
To: O1 <br>
Subject: Problem
 
 
 
 
Very possibly. This presents us with a useful opportunity. I want you to find out as much about them as possible - who they are, what they know, how they think. They're clearly not stupid, so you should organise something believable. If you can perform this task properly, then it will make up for your earlier mistake. If not, then we will have to have a talk very soon.
 
V.
</code><hr>
 
<code>
Date: 8 October 2005 8:58am<br>
From: O8 <br>
To: O1 <br>
Subject: Sydney
 
 
 
 
I'm ready.
</code><hr>
 
<code>
Date: 8 October 2005 10:02am<br>
From: O8 <br>
To: O1 <br>
Subject: Sting
 
 
 
 
Sounds good. I'll help in any way I can.
</code><hr>
 
<code>
Date: 8 October 2005 10:46am<br>
From: O8 <br>
To: O1 <br>
Subject: Sting
 
 
 
 
Okay. How will you arrange the meeting? Through the holiday website?
</code><hr>
 
<code>
Date: 8 October 2005 11:12am<br>
From: O8 <br>
To: O1 <br>
Subject: Sting
 
 
 
 
I see what you mean by double-bluff now. I'll arrange transport to London to arrive in good time. If you want to know the capabilities of this network, then I recommend that we set them a number of tests preceding the rendezvous; tests of their intelligence, imagination and organisational abilities. After all, we want to make sure that only our agent (me) can get through to the rendezvous! Those fools will just be helping us...
</code><hr>
 
<code>
Date: 9 October 2005 8:21am<br>
From: O8 <br>
To: O1 <br>
Subject: Sting
 
 
 
 
I've examined the reports on this enemy network, and mainly their unexpected participation in the 'Receda's Revenge' event. They seem extremely unprofessional. I study psychology - I assure you that these people will go along with our tasks. They think it's all some kind of game.
</code><hr>
 
<code>
Date: 9 October 2005 2:31pm<br>
From: O7 <br>
To: O1 <br>
Subject: For real?
 
 
 
 
Manchester online. Is there anybody out there?
</code><hr>
 
<code>
Date: 10 October 2005 10:00am<br>
From: O8 <br>
To: O1 <br>
Subject: Sting
 
 
 
 
Good. I'll be in London in a few days to decide on a location. Clapham in south London seems suitable. I've been there before, and I can set things up appropriately. It's almost a shame they'll never know how well we outmanoeuvred them. They'll just get to the end at the heliport and bang their heads against the wall trying to solve an impossible puzzle.
</code><hr>
 
<code>
Date: 12 October 2005 2:46pm<br>
From: V <br>
To: All operatives<br>
Subject: Successful completion
 
 
 
 
Both unstable links in the chain have been eliminated. We were fortunate in several respects. It is vital that no other mistakes are made. Contact between operatives is only to be through established channels.
 
V.
</code><hr>
 
===By Conversation===
 
====Checking In====
 
<code>
Date: 19 September 2005 2:49pm<br>
From: O2<br>
To: O1<br>
Subject: London here
 
Checking in.
</code><hr>
 
<code>
Date: 23 September 2005 11:18pm<br>
From: O3<br>
To: O1<br>
Subject: On
 
Toronto online.
</code><hr>
 
<code>
Date: 29 September 2005 11:57pm<br>
From: O4<br>
To: O1<br>
Subject: Budapest
 
Check.
</code><hr>
 
<code>
Date: 30 September 2005 4:15pm<br>
From: O5<br>
To: O1<br>
Subject: Checking in
 
New York has come online.
</code><hr>
 
<code>
Date: 5 October 2005 3:34am<br>
From: O6<br>
To: O1<br>
Subject: Moscow ready
 
Checking and and waiting for orders.
</code><hr>
 
<code>
Date: 9 October 2005 2:31pm<br>
From: O7<br>
To: O1<br>
Subject: For real?
 
Manchester online. Is there anybody out there?
</code><hr>
 
====Pesky UEN====
 
<code>
Date: 5 October 2005 4:34pm<br>
From: O1<br>
To: V<br>
Subject: Problem
 
I've received some possibly bad news about our operations - it seems like we have some people trying to intercept our communications. We think they've already found some of our keywords and signs.
</code><hr>
 
<code>
Date: 5 October 2005 4:38pm<br>
From: V<br>
To: O1<br>
Subject: Problem
 
Which keywords?
 
V
</code><hr>
 
<code>
Date: 5 October 2005 4:45pm<br>
From: O1<br>
To: V<br>
Subject: Problem
 
All of them, starting from the Receda Approach to yesterday's. This wasn't my fault! I followed the agreed plan for activating our people, and I was not informed of any other network that was acting against us.
</code><hr>
 
<code>
Date: 5 October 2005 4:55pm<br>
From: V<br>
To: O1<br>
Subject: Problem
 
Please calm down. I was not aware of them either; however, it is your role to check for such possibilities. You should have detected them earlier. At least we found out now, rather than later. Are they aware that we know about them?
 
V.
</code><hr>
 
<code>
Date: 5 October 2005 5:11pm<br>
From: O1<br>
To: V<br>
Subject: Problem
 
Judging by traffic analysis and their behaviour, no, they don't know we're on to them. Are you thinking what I'm thinking?
</code><hr>
 
<code>
Date: 5 October 2005 5:16pm<br>
From: V<br>
To: O1<br>
Subject: Problem
 
Very possibly. This presents us with a useful opportunity. I want you to find out as much about them as possible - who they are, what they know, how they think. They're clearly not stupid, so you should organise something believable. If you can perform this task properly, then it will make up for your earlier mistake. If not, then we will have to have a talk very soon.
 
V.
</code><hr>
 
<code>
Date: 5 October 2005 5:32pm<br>
From: O1<br>
To: V<br>
Subject: Problem
 
I understand. I'll make sure we find out about these people. I'll be in touch as things develop.
</code><hr>
 
<code>
Date: 8 October 2005 9:15am<br>
From: O1<br>
To: O8<br>
Subject: Sting
 
I apologise for the change in arrangements for your activation, but our normal route of communications was compromised. We are going to turn this to our advantage. I need your assistance to set up a fake holiday website to coincide with the sixth sign in Manchester.
 
We're going to perform a double-bluff - the website will pass itself off as being the last in the series of keywords. The enemy network will then crack a puzzle-password we've set there in order to access our 'secret mainframe'; they seem to have a very low opinion of our security and so we're confident they'll believe they've really cracked through. We will use this holiday website to feed them false information.
</code><hr>
 
<code>
Date: 8 October 2005 10:02am<br>
From: O8<br>
To: O1<br>
Subject: Sting
 
Sounds good. I'll help in any way I can.
</code><hr>
 
<code>
Date: 8 October 2005 10:31am<br>
From: O1<br>
To: O8<br>
Subject: Sting
 
Good. I've decided that I want you to meet the members of this network face to face. It's a risk we haven't taken so far, but I have no reason to believe they suspect us.
</code><hr>
 
<code>
Date: 8 October 2005 10:46am<br>
From: O8<br>
To: O1<br>
Subject: Sting
 
Okay. How will you arrange the meeting? Through the holiday website?
</code><hr>
 
<code>
Date: 8 October 2005 10:50am<br>
From: O1<br>
To: O8<br>
Subject: Sting
 
Yes. The idea is that we do know about them, but we don't know that they've broken into our 'secret mainframe'. Using the mainframe, we'll set up a rendezvous for the seventh and final keyword in London on 22nd October. No doubt they'll attempt to disrupt this 'rendezvous' - we're going to encourage them to come along, in fact, with some coded adverts and a fake website of someone who's infiltrated our organisation. When they come, we can watch them.
</code><hr>
 
<code>
Date: 8 October 2005 11:12am<br>
From: O8<br>
To: O1<br>
Subject: Sting
 
I see what you mean by double-bluff now. I'll arrange transport to London to arrive in good time. If you want to know the capabilities of this network, then I recommend that we set them a number of tests preceding the rendezvous; tests of their intelligence, imagination and organisational abilities. After all, we want to make sure that only our agent (me) can get through to the rendezvous! Those fools will just be helping us...
</code><hr>
 
<code>
Date: 8 October 2005 11:21am<br>
From: O1<br>
To: O8<br>
Subject: Sting
 
Wonderful. But will they really believe that *any* organisation would set up such a byzantine series of tasks just to get two agents to meet.
</code><hr>
 
<code>
Date: 9 October 2005 8:21am<br>
From: O8<br>
To: O1<br>
Subject: Sting
 
I've examined the reports on this enemy network, and mainly their unexpected participation in the 'Receda's Revenge' event. They seem extremely unprofessional. I study psychology - I assure you that these people will go along with our tasks. They think it's all some kind of game.
</code><hr>
 
<code>
Date: 10 October 2005 9:12am<br>
From: O1<br>
To: O8<br>
Subject: Sting
 
I read the report you sent over separately - it seems fine. We'll be implementing most of your suggestions. As I mentioned earlier, you'll be pretending that you're a member of the enemy network. On the 22nd, you'll be monitoring their progress in our tasks and reporting back in real time. I'll station people nearby so if there are any upsets, then we'll get you out.
</code><hr>
 
<code>
Date: 10 October 2005 10:25am<br>
From: O1<br>
To: V<br>
Subject: Problem Solved
 
I've organised an operation to find out about the enemy network, with a little help from O8 in Sydney. We're performing a double-bluff and setting them a series of tasks to test their abilities. O8 will be posing as one of their members and providing us with intelligence.
</code><hr>
 
====Tetchy V====
 
<code>
Date: 10 October 2005 12:03pm<br>
From: O5<br>
To: O7, O2<br>
Subject: V
 
V's kind of tetchy today, isn't he?
</code><hr>
 
<code>
Date: 10 October 2005 12:05pm<br>
From: O7<br>
To: O5, O2<br>
Subject: V
 
Probably his *boss* has been on his tail.
 
Date: 10 October 2005 12:08pm<br>
From: O5<br>
To: O7, O2<br>
Subject: V
 
His boss? You mean the Big Boss?
</code><hr>
 
<code>
Date: 10 October 2005 12:13pm<br>
From: O7<br>
To: O5, O2<br>
Subject: V
 
No. I mean his boss at that job.
</code><hr>
 
<code>
Date: 10 October 2005 12:14pm<br>
From: O5<br>
To: O7, O2<br>
Subject: V
 
V has a job?!
</code><hr>
 
<code>
Date: 10 October 2005 12:15pm<br>
From: O7<br>
To: O5, O2<br>
Subject: V
 
Yeah, you didn't know?
</code><hr>
 
<code>
Date: 10 October 2005 12:17pm<br>
From: O5<br>
To: O7, O2<br>
Subject: V
 
No! Why does he have a job? Where?!
</code><hr>
 
<code>
Date: 10 October 2005 12:18pm<br>
From: O7<br>
To: O5, O2<br>
Subject: V
 
I can hardly say *where*, can I? It's absurd anyway. He works at this stupid little job - says it's good cover, gives him a normal life. More like it gives him a chance to indulge his kink....
</code><hr>
 
<code>
Date: 10 October 2005 12:19pm<br>
From: O2<br>
To: O7, O5<br>
Subject: V
 
Uh, guys? You know V can read these mails, right?
</code><hr>
 
====Successful Completion====
 
<code>
Date: 12 October 2005 2:46pm<br>
From: V<br>
To: All operatives<br>
Subject: Successful completion
 
Both unstable links in the chain have been eliminated. We were fortunate in several respects. It is vital that no other mistakes are made. Contact between operatives is only to be through established channels.
 
V.
</code><hr>
 
<code>
Date: 12 October 2005 3:51pm<br>
From: O3<br>
To: All operatives<br>
Subject: Successful completion
 
What about the fourth member of the original group?
</code><hr>
 
<code>
Date: 12 October 2005 7:42pm<br>
From: V<br>
To: All operatives<br>
Subject: Successful completion
 
For the time being, she poses no threat.
 
Date: 12 October 2005 7:48pm<br>
From: O6<br>
To: All operatives<br>
Subject: Successful completion
 
I would favour a thorough eradication operation.
</code><hr>
 
<code>
Date: 12 October 2005 7:49pm<br>
From: V<br>
To: All operatives<br>
Subject: Successful completion
 
I am unconvinced that the risk of exposure would be worth the gain in security.
 
V.
</code><hr>
 
<code>
Date: 13 October 2005 2:05am<br>
From: O6<br>
To: All operatives<br>
Subject: Successful completion
 
The very existence of the fourth member constitutes a risk of exposure. The behaviour of K and Q confirm this. I suggest immediate elimination.
</code><hr>
 
<code>
Date: 13 October 2005 2:28am<br>
From: V<br>
To: All operatives<br>
Subject: Successful completion
 
You presume too much on your position. She will be eliminated as soon as practical. I will determine when that point is reached.
 
V.
</code><hr>
 
====O2 Status and Package====
 
<code>
Date: 18 October 2005 10:05am<br>
From: V<br>
To: O2<br>
Subject: Status request
 
How is your assignment progressing? Have you made contact?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:56am<br>
From: O2<br>
To: V<br>
Subject: Status request
 
Nothing short of brilliant, actually. I got in deep with that one, if you know what I mean, and it's a keeper. I've already got something you positively must see.
</code><hr>
 
<code>
Date: 18 October 2005 11:03am<br>
From: V<br>
To: O2<br>
Subject: Status request
 
Excellent. You know how to send it to me, I assume?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 11:14am<br>
From: O2<br>
To: V<br>
Subject: Status request
 
Yeah, of course, no worries there. You'll have it by midday tomorrow, I'd expect.
 
By the by, I've been meaning to tell you to keep an eye on O8. I've not got much to give you in support of that yet, call it a gut feeling for now, a hunch. But I'll follow up on it as well, and let you know when I know.
</code><hr>
 
<code>
Date: 18 October 2005 11:21am<br>
From: V<br>
To: O2<br>
Subject: Status request
 
Don't get distracted from your primary focus. I will tell you if and when I want that kind of advice.
 
V. </code><hr>
 
<code>
Date: 18 October 2005 11:41am<br>
From: O2<br>
To: V<br>
Subject: Status request
 
At your pleasure, by all means. Just don't blame me if the pot boils over while your back is turned.
</code><hr>
 
<code>
Date: 18 October 2005 11:48am<br>
From: V<br>
To: O2<br>
Subject: Status request
 
Whether or not you are happy with this situation, I expect you to act like a professional.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 12:12pm<br>
From: O2<br>
To: V<br>
Subject: Status request
 
Aye-aye, cap'n.
 
Package is away.
</code><hr>
 
<code>
Date: 19 October 2005 6:36am<br>
From: V<br>
To: O2
Subject:
 
That was certainly unexpected.
 
V.
</code><hr>
 
<code>
Date: 19 October 2005 8:41am<br>
From: O2<br>
To: V
Subject:
 
Pretty though, ain't it?
</code><hr>
 
<code>
Date: 19 October 2005 8:49am<br>
From: V<br>
To: O2
Subject:
 
That might just be the understatement of the new century.
 
V.
</code><hr>
 
====O3 Status====
 
<code>
Date: 18 October 2005 10:06am<br>
From: V<br>
To: O3<br>
Subject: Status request
 
How is your assignment progressing? Are you ready?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:10am<br>
From: O3<br>
To: V<br>
Subject: Status request
 
Always. Point me and pull the trigger.
</code><hr>
 
<code>
Date: 18 October 2005 10:13am<br>
From: V<br>
To: O3<br>
Subject: Status request
 
Soon, perhaps, but not quite yet.
 
What other news?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:16am<br>
From: O3<br>
To: V<br>
Subject: Status request
 
In other news, the delivery was a success! And a shining example of the brand name as well, if I do say so myself. One more for your roster, with a bit of time...and luck, eh?
</code><hr>
 
<code>
Date: 18 October 2005 10:20am<br>
From: V<br>
To: O3<br>
Subject: Status request
 
My congratulations. One to follow in father's footsteps, I hope.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:23am<br>
From: O3<br>
To: V<br>
Subject: Status request
 
I'd hope it wouldn't be necessary for too much longer! Perhaps when this one's walking there won't be any need to follow in my footsteps.
</code><hr>
 
<code>
Date: 18 October 2005 10:25am<br>
From: V<br>
To: O3<br>
Subject: Status request
 
We live in hope. Send my congratulations and best wishes to your wife as well.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:28am<br>
From: O3<br>
To: V<br>
Subject: Status request
 
I will. She'll be in touch herself when she's recovered ;-)
</code><hr>
 
<code>
Date: 18 October 2005 10:38am<br>
From: V<br>
To: O3<br>
Subject: Status request
 
I look forward to that day.
 
V.
</code><hr>
 
====O4 Status====
 
<code>
Date: 18 October 2005 10:04am<br>
From: V<br>
To: O4<br>
Subject: Status request
 
How is your assignment progressing? Have you identified the anomaly?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:17am<br>
From: O4<br>
To: V<br>
Subject: Status request
 
If I knew what I was even looking for, it would be a big help, I'm sure. I'm just not used to dealing with this fine a grain of detail. But you know me, even though I may feel like I'm blindfolded and bashing wildly at a roomful of piñatas, once I hit the right one, the payoff will be worth it.
</code><hr>
 
<code>
Date: 18 October 2005 10:34am<br>
From: V<br>
To: O4<br>
Subject: Status request
 
Feeling colourful today? Let me know when you have something useful to report.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 11:07am<br>
From: O4<br>
To: V<br>
Subject: Status request
 
Oh, you'll know. Give me a LITTLE credit, geez.
</code><hr>
 
====O6 Status====
 
<code>
Date: 18 October 2005 10:07am<br>
From: V<br>
To: O6<br>
Subject: Status request
 
How is your assignment progressing? Do you think it will work?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:15am<br>
From: O6<br>
To: V<br>
Subject: Status request
 
Will it work? Undoubtedly! Will it proceed to raze everything within a 12-block radius? Quite possible. You don't anticipate that will be a problem, do you?
</code><hr>
 
<code>
Date: 18 October 2005 10:19am<br>
From: V<br>
To: O6<br>
Subject: Status request
 
Well that all depends on the circumstances under which we're forced to use it. My main concern is that it will keep the package safe.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:21am<br>
From: O6<br>
To: V<br>
Subject: Status request
 
Sure, at the expense of everything else in close proximity. But the package, as you well know, is a block of an entirely different mettle, in a manner of speaking. I'm certain IT won't be harmed, anyway. And that's a sort of protection after all, isn't it?
</code><hr>
 
<code>
Date: 18 October 2005 10:24am<br>
From: V<br>
To: O6<br>
Subject: Status request
 
You're talking last ditch when I need top drawer. Let us aim for perfection, so that we may approach it more nearly.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:38am<br>
From: O6<br>
To: V<br>
Subject: Status request
 
Fine. Trust me. It will be ready and up to spec by the time you have need of it.
</code><hr>
 
====O7 Status====
 
<code>
Date: 18 October 2005 10:06am<br>
From: V<br>
To: O7<br>
Subject: Status request
 
How is your assignment progressing? Where is my file?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:24am<br>
From: O7<br>
To: V<br>
Subject: Status request
 
I'm still compiling data. You'll get the first run as soon as it's crunched, I promise.
 
The whispers are growing louder about that doppelganger you spotted. The Academy has been buzzing for awhile, to be certain, but this is... different. And confused. It will be a challenge to find the weevil in that sack of rice but I'll give it a go. Remembered anything else since then, have you?
</code><hr>
 
<code>
Date: 18 October 2005 10:29am<br>
From: V<br>
To: O7<br>
Subject: Status request
 
No. But then, that's why I have you.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:30am<br>
From: O7<br>
To: V<br>
Subject: Status request
 
Rumors like this are a hot match in a dry field. Soon, the threads may be unrecognizable and impossible to unravel. It really would help enormously if...well....
</code><hr>
 
<code>
Date: 18 October 2005 10:33am<br>
From: V<br>
To: O7<br>
Subject: Status request
 
I'm certain it would. But you know full well that's not an option. I'll just have to trust in your skills. Your network is legendary, after all.
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:39am<br>
From: O7<br>
To: V<br>
Subject: Status request
 
Legendary, sure, but not supernatural.
</code><hr>
 
<code>
Date: 19 October 2005 9:04am<br>
From: O7<br>
To: V<br>
Subject: Update
 
I may just have something a bit more concrete for you today. Some intriguing patterns in the threads. I could use a fatter pipe on a stream or two, though, if you're offering.
</code><hr>
 
<code>
Date: 19 October 2005 9:38am<br>
From: V<br>
To: O7<br>
Subject: Update
 
O8 ought to be able to work that out for you. I will inform him, if you'll provide him with your specifications.
 
V.
</code><hr>
 
====O8 Status====
 
<code>
Date: 18 October 2005 10:03am<br>
From: V<br>
To: O8<br>
Subject: Status request
 
How is your assignment progressing? Have you re-established the link?
 
V.
</code><hr>
 
<code>
Date: 18 October 2005 10:37am<br>
From: O8<br>
To: V<br>
Subject: Status request
 
I've asked O6 to request support on the recent issue. Until I can lock that down, there's no way for us to re-link. Very troubling.
</code><hr>
 
<code>
Date: 18 October 2005 10:41am<br>
From: V<br>
To: O8<br>
Subject: Status request
 
Keep me apprised as soon as you've heard back.
 
V.
</code><hr>
 
====Geek Questions====
 
<code>
Date: 18 October 2005 10:55am<br>
From: O8<br>
To: O6<br>
Subject: Geek questions!!
 
I've got kind of an emergency problem over here and I need your help on it. Contact me as soon as you get in and I'll zip you the details, okay?
 
Thanks, dude.
</code><hr>
 
====O4 Supplies====
 
<code>
Date: 18 October 2005 12:13pm<br>
From: O4<br>
To: V<br>
Subject: Supplies list
 
I'm trying to put together a list of needs. What should I be planning for (or against)?
</code><hr>
 
<code>
Date: 18 October 2005 4:15pm<br>
From: V<br>
To: O4<br>
Subject: Supplies list
 
Plan for the usual contingencies for now. Specifics should be forthcoming shortly.
 
V.
</code><hr>
 
====O5 Supplies====
 
<code>
Date: 18 October 2005 12:13pm<br>
From: O5<br>
To: V<br>
Subject: Supplies list
 
I‚m trying to put together a list of needs. What should I be planning for (or against)?
</code><hr>
 
<code>
Date: 18 October 2005 4:15pm<br>
From: V<br>
To: O5<br>
Subject: Supplies list
 
Plan for the usual contingencies for now. Specifics should be forthcoming shortly.
 
V
</code><hr>
 
====What’s Up? ====
 
<code>
Date: 18 October 2005 3:27pm<br>
From: O7<br>
To: O8<br>
Subject: So what's up?
 
I figure if anyone would know, it'd be you.
</code><hr>
 
<code>
Date: 18 October 2005 4:15pm<br>
From: O8<br>
To: O7<br>
Subject: So what's up?
 
I have an idea, yeah. But relax, I'm sure V will fill you in when you need to know. I'm not going to step on any toes in my first dance of the night.
</code><hr>


====Standby====
{| cellpadding="10" width="70%" style="border: 0px; background: Orange"
| [[Emails To and From O2]]
|}


<code>
{| cellpadding="10" width="70%" style="border: 0px; background: Yellow"
Date: 18 October 2005 3:29pm<br>
| [[Emails To and From O3]]
From: V<br>
|}
To: All operatives<br>
Subject: Standby


Those of you with uncompleted assignments, please provide me with regular status reports. While we wait for the situation to clarify, please reserve these channels for official use only.
{| cellpadding="10" width="70%" style="border: 0px; background: LightGreen"
| [[Emails To and From O4]]
|}


V.
{| cellpadding="10" width="70%" style="border: 0px; background: MediumTurquoise "
</code><hr>
| [[Emails To and From O5]]
|}


====O4 in Response to Standby====
{| cellpadding="10" width="70%" style="border: 0px; background: LightBlue"
| [[Emails To and From O6]]
|}


<code>
{| cellpadding="10" width="70%" style="border: 0px; background: SlateBlue"
Date: 18 October 2005 3:38pm<br>
| [[Emails To and From O7]]
From: O4<br>
|}
To: V<br>
Subject: Standby


Does this mean no more love letters?
{| cellpadding="10" width="70%" style="border: 0px; background: Plum"
</code><hr>
| [[Emails To and From O8]]
|}


<code>
{| cellpadding="10" width="70%" style="border: 1px; background: White"
Date: 18 October 2005 3:45pm<br>
| Emails To and From V ... are numerous.
From: V<br>
|}
To: O4<br>
Subject: Standby


Everything that we do is done with love. I'm sure you know that by now. Do you have something for me?
==See Also:==
*[[The Third Power]]
*[[The Receda Trail]]
**[[The Receda Approach]]
**[[The Receda Sign]]
**[[The Receda Institute for Somnatherapy]]
**[[The Receda School of Music]]
**[[Receda's Revenge]]
**[[Receda Resorts]]
**[[22-OCT-05]]


V.
</code><hr>


<code>
Date: 18 October 2005 3:51pm<br>
From: O4<br>
To: V<br>
Subject: Standby


Check your drop. And don't say I never gave you anything. ;)
{{3P}}
</code><hr>

Latest revision as of 20:04, 13 March 2007

PERPLEX CITY, SEASON ONE
The search for the Receda Cube on Earth


The Website

Groupware Manager was found on the 22nd Oct from the live event/online support.

For more information on the people discussed, See: 3PDossier


Auditor

The Auditor page held a short piece saying that in 48 hrs it would go live.

On Oct 24th at ~6:00pm BST the site changed.

It now contains the following text: 

 Select an Account 
Select an account to the right to view the enabled modules.
 
 Enabled Modules  
The Administrator has enabled auditing of these user account modules.

 *email
 
 Disabled Modules  
The Administrator has disabled auditing of these user account modules.

 *email attachments 
 *file attachments 
 *documents 
 *to-do lists 
 *notes 
 *news/website clips 
 *bookmarks 
 *rss/atom feeds 
 *online calculators 
 *events calendar 
 *alarms/reminders

On the right of the page is a drop-down list of usernames (O1 to O8) referring to each of the operatives (excluding V and the "Big Boss").

Each Operative's page requires a different password.

The Passwords

Notice: those are Letter Ohs, not the Number Zeroes. 

O1 - password
O2 - star
O3 - power
O4 - dream
O5 - joy
O6 - head
O7 - wind
O8 - watch

These were all determined based on information from The Receda Trail.

The Emails

Much reference is made to The Receda Trail in these messages.

Emails To and From O1
Emails To and From O2
Emails To and From O3
Emails To and From O4
Emails To and From O5
Emails To and From O6
Emails To and From O7
Emails To and From O8
Emails To and From V ... are numerous.

See Also:


Receda.png

The Third Power

They are an ancient society of very secret intentions. Pietro Salk tipped the ice-berg, and it cost him his life. The Police has brought them to their knees during Operation Bayonet, but they have been around a long time, and they aren't likely to be stopped so easily. They have Operatives on Earth, as well is in Perplex City. V appears to be a #2 man, but who does #2 work for?

Anthony Granier | V | Roberto Solitano | Caine Johansson | Miranda Katsoulis | Unnamed operatives on Earth

Retrieved from "https://perplexcitywiki.com/w/index.php?title=3PGroupwareManager&oldid=18220"