-
Notifications
You must be signed in to change notification settings - Fork 3
/
emails.html
381 lines (377 loc) · 47.1 KB
/
emails.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
<!DOCTYPE html>
<html>
<head>
<title>trace emails</title>
<meta charset="utf-8" />
<link rel="stylesheet" href="./hackmud.css">
<script>
function fixRisk() {
if(document.location.search=='?risk'){
[...document.all].forEach(x=>{
if(x.style.color=='rgb(0, 0, 0)')
x.style.textShadow='0px 0px 5px white'
});
[...document.getElementsByTagName('a')].forEach(x=>{
if(x.href)
x.href+='?risk'
})
}
}
</script>
<script>
function go() {
var n={
fbreton: '[<span style="color:#FF8000">$1</span>$2]',
erajbhandari:'[<span style="color:#FF8383">$1</span>$2]',
emarko: '[<span style="color:#8E3434">$1</span>$2]',
mhollister: '[<span style="color:#B3FF9B">$1</span>$2]',
chela: '[<span style="color:#00FFFF">$1</span>$2]',
mpytel: '[<span style="color:#0070DD">$1</span>$2]',
UNKNOWN1: '[<span style="color:#E6C4FF">$1</span>$2]',
corporate: '[<span style="color:#888888">$1</span>$2]',
epoch_news: '[<span style="color:#444444">$1</span>$2]',
bigbot: '[<span style="color:#FF8383">$1</span>$2]',
}
var s=document.body.innerHTML;
for(var i in n) {
s=s.replace(new RegExp('\\[('+i+')(\\??)\\]','g'),n[i]);
}
document.body.innerHTML=s;
}
</script>
</head>
<body onload='go();fixRisk()'>
<table class="noborder wide">
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2055</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF0000">y2055d001: BO DIES</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="1dfe15bb19e0236f"><td>ORIG:</td><td colspan=2>y2055d001_EmilMarko_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>1dfe15bb19e0236f</td></tr>
<tr><td>BODY:</td><td>[emarko?]</td><td>so im called in today right its news years day and im here in some botyard and the owners losing his mind bc the bots are ignoring target items that are right there, literally just right there. turns out older packbot firmware has some weird quirks. they have a directive to avoid wasting energy and it turns out that turning uses more juice than forward motion. so if they can get to a packet without turning theyll go for it, every time. dumb but what can u do</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="6283343570d3e42e"><td>ORIG:</td><td colspan=2>approved_the_mysterious_destruction_of_Myncuk</td></tr>
<tr><td>ADDR:</td><td colspan=2>6283343570d3e42e</td></tr>
<tr><td>HEAD:</td><td colspan=2>The Mysterious Destruction of China's Pioneering AI</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>Bo Yi - more commonly simply 'Bo' - was one of the world's first 'true' artificial intelligences. Now, AI experts across the world are reeling from the discovery that the service appears to have been deliberately and maliciously destroyed by a hostile force. Bo was integrated into governance, finance and community support systems throughout mainland China, all of which are seeing major outages today as alternative solutions are sought. The question on everybody's lips, meanwhile, is "how did this happen?" Operators like Bo are protected politically and digitally. They lack centralized hardware, spanning many thousands of individual systems each with top-tier security measures and deep redundancies - none of which appear to have registered any kind of intrusion or error in the moments before Bo 'died'. Indeed, we would likely be looking to 'acts of God' to explain Bo's destruction - an undetected solar flare, for example - were it not for the now-infamous signature appended to the service's shutdown: the singular red 'smiley face' that was witnessed on displays across China in the moments before the system went dark.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="d3645f4d20ab2741"><td>ORIG:</td><td colspan=2>y2055d137_EmilMarko_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>d3645f4d20ab2741</td></tr>
<tr><td>BODY:</td><td>[emarko?]</td><td>right right so heres the other thing, sometimes good lighting is more trouble than its worth. your average bot isnt that smart so actually the more stuff it can see the more upset it gets. well maybe not upset but u know what i mean. best thing is to tell them that they know everything they need to know and then they stop looking, which usually means the light turns off. make sure u got the jumpsuit on or they wont believe u. then flash <span style="color:#385A6C">▀</span><span style="color:#385A6C">▁</span><span style="color:#F3F998">▁</span><span style="color:#B3FF9B">█</span><span style="color:#F3F998">▀</span><span style="color:#F3F998">▁</span><span style="color:#385A6C">▀</span>, something like that</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="2ec4a326cfeb6beb"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>2ec4a326cfeb6beb</td></tr>
<tr><td>BODY:</td><td>[emarko]</td><td>look there are gonna be times where you are just gonna have to take it on faith that the bot can see you, its gonna feel weird but if you want them to use their light you have to tell them its dark or they are just going to sit there. you wanna flash <span style="color:#385A6C">▀</span><span style="color:#385A6C">▁</span><span style="color:#F3F998">▁</span><span style="color:#B3FF9B">█</span><span style="color:#F3F998">▀</span><span style="color:#F3F998">▁</span><span style="color:#FFD863">▀</span>, something like that, convince them they need more data about the space around them, thats the trick. doesnt always work for me but thats usually cos its dark, so i cant see the projector buttons. usually get a good amount of light tho, which will do alright unless you want fine control, but its usually enough for me</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="d7e35a4d9181635e"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>d7e35a4d9181635e</td></tr>
<tr><td>BODY:</td><td>[emarko]</td><td>okay so 99%, like 99.9% of nav errors can be put down to problems with light. either too much or not enough. look i get that everyones calling this a critical error with a light-based system, but everything that your bot can see is doing something to its brain so you gotta manage it carefully. if you wanna maximise your chance of getting the behavior you want then pump the lights up with something like <span style="color:#385A6C">▀</span><span style="color:#385A6C">▁</span><span style="color:#F3F998">▁</span><span style="color:#B3FF9B">█</span><span style="color:#F3F998">▀</span><span style="color:#F3F998">▁</span><span style="color:#FFD863">▀</span><span style="color:#B3FF9B">█</span><span style="color:#FFD863">▀</span><span style="color:#F3F998">▅</span>, then work back from there. ok, i get that its not ideal. the success rate isnt great. look, i have put years into this tech. i have been on the ground with customers solving problems with this tech on new years morning when i could have been with my kids. please dont roll it back</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="d4603da01cae7b13"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>d4603da01cae7b13</td></tr>
<tr><td>BODY:</td><td>[emarko]</td><td>here is one of the problems with sematone, i will admit this isnt ideal but it isnt great at scale and neither are the bots that use it. you wanna tell em to make something bigger or smaller, they are probably not gonna understand you unless you can give them a reference they understand, and pretty much the only thing they reliably understand is other bots. so like, if u wanna be careful, <span style="color:#385A6C">▀</span><span style="color:#385A6C">▁</span><span style="color:#F3F998">▁</span><span style="color:#B3FF9B">█</span><span style="color:#F3F998">▀</span><span style="color:#F3F998">▁</span><span style="color:#FFD863">▀</span><span style="color:#B3FF9B">█</span><span style="color:#FFD863">▀</span><span style="color:#F3F998">▁</span> will get em to generate just enough light for themselves. boost that up to a ▃ on the final spatial modifier and theyll push it out a bit further</td>
<tr><td colspan=3><hr></td></tr>
<tr id="ddac44f82e343d25"><td>ORIG:</td><td colspan=2>flagged_awesome_packbot_hack_busts_aKyMF8</td></tr>
<tr><td>ADDR:</td><td colspan=2>ddac44f82e343d25</td></tr>
<tr><td>HEAD:</td><td colspan=2>AWESOME PACKBOT HACK BUSTS PACKYARD PRANKS POSSIBILITY SPACE WIDE OPEN</td></tr>
<tr><td>BODY:</td><td>[emarko?]</td><td>SO LIKE packspeak was the best thing to happen to bot hackers so u dont see it much any more but IF U DO then heres something real good to try. get into the sensorline of a bot thats got a package and hit it with <span style="color:#299400">▀</span><span style="color:#00FFFF">▁</span><span style="color:#299400">▁</span><span style="color:#B3FF9B">█</span><span style="color:#299400">▀</span><span style="color:#0000FF">▁</span><span style="color:#FF0070">▁</span> and get ready to feel real sorry for whoever they call out from the corps to handle it when the little bot just goes wild on that thing. srsly. itll rip the whole package to pieces with whatevers nearby, the floor, walls, other bots, its totally wild</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2056</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="6861a3661fff4586"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>6861a3661fff4586</td></tr>
<tr><td>BODY:</td><td>[fbreton?]</td><td>so these addr identifiers, how do we typically</td></tr>
<tr><td></td><td>[???-2]</td><td>crc-64, ecma 182</td></tr>
<tr><td></td><td>[fbreton?]</td><td>secure them. oh. you get this question a lot?</td></tr>
<tr><td></td><td>[???-2]</td><td>you have no idea</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="c84ebcf63df0fbe4"><td>ORIG:</td><td colspan=2>? (Note: this must be just before she makes the new auth module or else she wouldn't be complaining about it)</td></tr>
<tr><td>ADDR:</td><td colspan=2>c84ebcf63df0fbe4</td></tr>
<tr><td>BODY:</td><td>[fbreton]</td><td>look - i know how people get when the newbie starts asking questions, but, like, we are relying hard on our auth AIs. really, really hard.</td></tr>
<tr><td></td><td>[???-1]</td><td>you don't need to tell me, flo, i get it</td></tr>
<tr><td></td><td>[fbreton]</td><td>all you need to do to dupe the system is convince the auth service to let you fiddle with the ADDR line. you could literally change 'false' to 'true' and access whatever you wanted. how did this end up like this?</td></tr>
<tr><td></td><td>[???-1]</td><td>people upstairs put a lot of faith in the operator. zero downtime is kind of our thing</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="5864ca32f16f9bc8"><td>ORIG:</td><td colspan=2>y2056d124_FlorenceBreton_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>5864ca32f16f9bc8</td></tr>
<tr><td>BODY:</td><td>[???-1]</td><td>hey effy bee you get the new auth module done yet</td></tr>
<tr><td></td><td>[fbreton]</td><td>hi to you too. yes, its up and running</td></tr>
<tr><td></td><td>[???-1]</td><td>you could have pinged me</td></tr>
<tr><td></td><td>[fbreton]</td><td>sorry</td></tr>
<tr><td></td><td>[???-1]</td><td>its fine, your new, but its a good idea to ping in one of the main channels so someone sees it</td></tr>
<tr><td></td><td>[fbreton]</td><td>ok, will do</td></tr>
<tr><td></td><td>[???-1]</td><td>er where did you put the module</td></tr>
<tr><td></td><td>[fbreton]</td><td>you're kidding right? it's literally called login</td></tr>
<tr><td></td><td>[???-1]</td><td>oh huh ye ok</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="334c5c9bffd5886d"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>334c5c9bffd5886d</td></tr>
<tr><td>BODY:</td><td>[???-1]</td><td>that's right everybody, the board has done the smart thing and gone with firstname-initial formatting for the new login system.</td></tr>
<tr><td></td><td>[???-2]</td><td>you're kidding, we're going to need to start accounting for duplicate names, like, immediately</td></tr>
<tr><td></td><td>[???-1]</td><td>is what it is. che's on 'first name terms with the world', so now so are we</td></tr>
<tr><td></td><td>[???-2]</td><td>ugh</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="3467b0f462b72fb3"><td>ORIG:</td><td colspan=2>y2056d128_FlorenceBreton_deleted</td></tr>
<tr><td>ADDR:</td><td colspan=2>3467b0f462b72fb3</td></tr>
<tr><td>BODY:</td><td>[???-1]</td><td>be glad you werent here when the bo stuff went down. was bad</td></tr>
<td></td><td>[fbreton?]</td><td>yeah?</td></tr>
<td></td><td>[???-1]</td><td>yeah. like, pray that doesnt happen to us. we can handle downtime and flaky outputs but jesus, nobody in this business slept that night</td></tr>
<td></td><td>[fbreton?]</td><td>it was a freak bug though right? that's the only explanation that makes sense</td></tr>
<td></td><td>[???-1]</td><td>yeah, probably. thing is, half of the rumors u hear came from here or reco or ft or architech. we all saw it go down and thought 'new operator'. guess we'd been waiting for it</td></tr>
<td></td><td>[fbreton?]</td><td>i heard hyperion had people on the ground in china when it happened</td></tr>
<td></td><td>[???-1]</td><td>thats true. not me. but a bunch of the senior guys were in sichuan for some meeting</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="156001c130fafdfa"><td>ORIG:</td><td colspan=2>y2056d316_FlorenceBreton_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>156001c130fafdfa</td></tr>
<tr><td>BODY:</td><td>[???-1]</td><td>word from above is 'user error' for those faulty keys btw</td></tr>
<tr><td></td><td>[fbreton]</td><td>that can't be right in every case, surely?</td></tr>
<tr><td></td><td>[???-1]</td><td>don't know what else to tell you, Flo</td></tr>
<tr><td></td><td>[fbreton]</td><td>they're keyed to che's unique kernel. if they're entered correctly, by an approved user, they should work</td></tr>
<tr><td></td><td>[???-1]</td><td>like i say, then. user error.</td></tr>
<tr><td></td><td>[fbreton]</td><td>look, i'll prove it. give me a sec to grab one.</td></tr>
<tr><td></td><td>[fbreton]</td><td>HDMS-@Che-PPMmiGbht0wjEwXY</td></tr>
<tr><td></td><td>[fbreton]</td><td>see? nothing</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="7675d502be9e1b1f"><td>ORIG:</td><td colspan=2>y2056d319_MaciekPytel_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>7675d502be9e1b1f</td></tr>
<tr><td>HEAD:</td><td colspan=2>Re Re Summon Code Error</td></tr>
<tr><td>BODY:</td><td>[mpytel?]</td><td>We're aware that the engineering teams are passing a lot of user complaints up the pipe re: che failing to respond to older summon keys. Particularly over the last few days. It's getting prevalent enough that it might be something we need to deal with via media/press. Company line here (which is true, for what it's worth) is that it's a result of the changes we put in place after 2055. If their codes are newer than that then it's user error, simple as. Any questions?</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2057</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="b7a8d3dbcc26d6e9"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>b7a8d3dbcc26d6e9</td></tr>
<tr><td>BODY:</td><td>[???]</td><td>the PVS is super barebones at the moment, dont overload it or it'll freak out. its for giving the RECO AI limited access to news, posts, whatever's going through our network at the time. more political than practical, honestly. if you need to find something its good to be specific. input field accepts multiple comma-separated terms, it's pretty oldschool</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="afc45e128e0dc9e4"><td>ORIG:</td><td colspan=2>y2057d011_MaciekPytel_deleted</td></tr>
<tr><td>ADDR:</td><td colspan=2>afc45e128e0dc9e4</td></tr>
<tr><td>BODY:</td><td>[???-1]</td><td>this is secure?</td></tr>
<td></td><td>[mpytel?]</td><td>Yes</td></tr>
<td></td><td>[???-1]</td><td>okay. what's going on?</td></tr>
<td></td><td>[mpytel?]</td><td>the Ratnasari people are keen to invest a little but want to expand their involvement. The post validation service is small potatoes. they're pushing for Monitor integration as part of the package</td></tr>
<td></td><td>[???-1]</td><td>that's a no, I'm sorry, I know this puts you in a tough spot</td></tr>
<td></td><td>[mpytel?]</td><td>What do you want me to tell them? Everyone else is bought in, or close enough</td></tr>
<td></td><td>[???-1]</td><td>god, I don't know. tell them that che's been jittery since bo yi and we're being careful about connecting her with other operators. god knows thats true enough.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF0000">y2057d202: (MALLORY-)CHE DIES</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="a7e45b2aa272a9ff"><td>ORIG:</td><td colspan=2>y2057d203_MaciekPytel_deleted</td></tr>
<tr><td>ADDR:</td><td colspan=2>a7e45b2aa272a9ff</td></tr>
<tr><td>BODY:</td><td>[UNKNOWN1]</td><td>Maciek, I'm aware of how much strain this situation is putting on you so this is just a note to say that I'm grateful that you're here and whatever the outcome, you've been a great servant of this company.</td></tr>
<tr><td></td><td>[mpytel]</td><td>Thank you. While I've got you - I've heard back from Amalgamated Robotics. They are willing to help if we give them systems access.</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>Not a good idea.</td></tr>
<tr><td></td><td>[mpytel]</td><td>Really? As I understand it, their Prover AI could reinitialize Che if we can fill in the gaps in her hardcopy.</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>No - Maciek, this goes no further than this channel, but AR's hardcopy of Che isn't valid.</td></tr>
<tr><td></td><td>[mpytel]</td><td>What?</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>It was years ago. Pre-Frankfurt. We were still in competition and some money changed hands. We bypassed them completely. Che was proved in China. Delete this straight away, OK?</td></tr>
<tr><td></td><td>[mpytel]</td><td>Ok. But the AR guys clearly aren't aware. And if we shut them out, it'll draw suspicion.</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>Then let them in. But don't bank on their Prover bailing us out - it's not going to work.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="23fd58ea7a7ba63c"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>23fd58ea7a7ba63c</td></tr>
<tr><td>BODY:</td><td>[UNKNOWN1]</td><td>FYI - I've let Maciek into the circle of trust re: Che and China. Sorry for not consulting first but this was necessary and he's trustworthy. He's doing good work on the frontline, but he needs to know to be careful with partner corps over the coming months. Have approved limited cooperation with AR because it'd be suspicious not to.</td></tr>
<tr><td></td><td>[???-2]</td><td>thanks for letting me know. what a mess. how much did you tell him?</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>Just the basics. There was a deal pre-Frankfurt and AR's copy isn't valid.</td></tr>
<tr><td></td><td>[???-2]</td><td>okay. nothing about 2055?</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>No.</td></tr>
<tr><td></td><td>[???-2]</td><td>are we worried about somebody making the connection?</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>Inevitable that they'll link the attacks. And there are people at the company who know that we had people on the ground in Chengdu at the time. But the scary stuff, the open hardline to Bo - we've controlled that info.</td></tr>
<tr><td></td><td>[???-2]</td><td>are you sure?</td></tr>
<tr><td></td><td>[UNKNOWN1]</td><td>Che has spent the last two years making sure it doesn't get out. Thank god she's ours. We dodged a bullet that night.</td></tr>
<tr><td></td><td>[???-2]</td><td>yeah, well, it hit us eventually</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="9ee897030c4a5318"><td>ORIG:</td><td colspan=2>y2057d203_FlorenceBreton_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>9ee897030c4a5318</td></tr>
<tr><td>BODY:</td><td>[fbreton]</td><td>i'm telling you, nothing like what you're saying happened last night. which parts of this do i need to explain again?</td></tr>
<tr><td></td><td>[mpytel]</td><td>I'm not blaming you, Flo, or your team. But appreciate how this looks. This was exactly like Bo Yi, but you're saying that there was no vulnerability for this new operator to exploit.</td></tr>
<tr><td></td><td>[fbreton]</td><td>that's exactly what i'm saying. we've gone over every byte of data about every action che took going back 24 hours pre-shutdown. give us more time and we'll go back further, but we're already at the outer bounds of when the damage could have been done. there was no other operator. it was just her. you guys are the reason that we don't have a live monitor connection, so she wasn't even talking to eve. Mr Pytel, i know why you're leaning on me. i get that the financial risks are massive if this was an internal error. but it might be, it really might be</td></tr>
<tr><td colspan=3><hr></td>
<tr id="03d2c78a565cd8ab"><td>ORIG:</td><td colspan=2>approved_no_eta_for_return_cpp1qm (From interface, this is y2057d203)</td></tr>
<tr><td>ADDR:</td><td colspan=2>03d2c78a565cd8ab</td></tr>
<tr><td>HEAD:</td><td colspan=2>"No ETA for return" of operator service 'Che' states Hyperion CFO as shares collapse</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>Hyperion's executive committee has confirmed that operator service 'Che' will remain offline for the foreseeable future following what is believed to have been a deliberate and targeted attack. In a statement to shareholders, Hyperion Chief Financial Officer Maciek Pytel described the damage to 'Che' as "fundamental and far-reaching", presenting "no ready solutions... and no ETA for return" of the service.</td></tr>
<tr><td></td><td>[epoch_news?]</td><td>In the days following the attack, thousands of subordinate services have experienced extensive disruption as a consequence of their reliance on Che-derived technologies and processes. The resettlement, autogovernance and counselling sectors are all expected to suffer further losses following today's announcement.</td></tr>
<tr><td></td><td>[epoch_news?]</td><td>Sanctioned primary-function operators such as 'Che' are among the world's most tightly-protected digital assets, protected by both advanced security systems and the terms of the Frankfurt Act.</td></tr>
<tr><td colspan=3><hr></td>
<tr id="03d2c78a565cd8ab"><td>ORIG:</td><td colspan=2>approved_expert_claims_that_death_9lQF1P (From interface, this is y2057d204)</td></tr>
<tr><td>ADDR:</td><td colspan=2>03d2c78a565cd8ab</td></tr>
<tr><td>HEAD:</td><td colspan=2>AI expert claims that 'death' of Che "undeniably linked" to attack on Bo Yi</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>Among rife speculation over the fate of the operator 'Che', the University of Oxford's foremost expert on intelligent digital services has lent her voice to those claiming a connection to the destruction of China's 'Bo' system in 2055. "They are undeniably linked," claims Dr. Erin Rajbhandari. "These systems do not simply break, and they lack single points of failure or other exploitable vulnerabilities. We now have only two instances of total operator failure in the history of this technology, and in each case death has occurred in an identical fashion - sudden, without any preceding disruption, and with the same calling-card. This does not necessarily prove that the same hostile actor is responsible, but certainly suggests that the same vulnerability has been exploited and that whoever did this wishes us to perceive a connection between the two."</td></tr>
<tr><td colspan=3><hr></td>
<tr id="02c1293801abdc0b"><td>ORIG:</td><td colspan=2>flagged_a_week_later_it_9eezww (From interface, this is y2057d208)</td></tr>
<tr><td>ADDR:</td><td colspan=2>02c1293801abdc0b</td></tr>
<tr><td>HEAD:</td><td colspan=2>A Week Later, It Finally Has A Name: 'Mallory'</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>HUGE NEWS today! If you've been paying attention to the channel this week then you'll know that we've been following the Che situation REAL closely. I mean, who isn't? It's the biggest story in tech at the moment and that basically makes it the biggest story in the world, RIGHT? Well two days ago you'll remember that Hyperion came out and said that basically, the truth was wilder than we thought: not only is Che ACTUALLY GONE but ANOTHER. OPERATOR. DID. IT. And as I said at the time, it's gotta be an unsanctioned op because why in the hell would any of the others go ROGUE just like that. Anyway not gonna beat around the bush, I'M RIGHT. They're calling it MALLORY, a malicious, UNSANCTIONED OPERATOR and NOBODY knows where it came from or how it works! Now I'm getting this up fast because GOD DAMN this is huge news but you gotta expect to hear from me again today because we got so much to discuss. HOW was it made? WHERE was it hiding? WHY Che? WHY now? Everything has changed, gang, EVERYTHING has changed</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="2e33e9876932b628"><td>ORIG:</td><td colspan=2>y2057d211_FlorenceBreton_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>2e33e9876932b628</td></tr>
<tr><td>HEAD:</td><td colspan=2>team leads memo - urgent - vulnerability notice</td></tr>
<tr><td>BODY:</td><td>[fbreton?]</td><td>appreciate that there's a lot on everyone's plates at the moment but i've been made aware of another hole in the system. there's no kind of safeguard in place to stop someone manually tinkering with the def_packet and set_packet functions in our network if they somehow got that far. would require auth AI to be totally offline but given what happened to che that's not unforeseeable. team leads - please check your systems for further vulnerabilities like this and get some fixes in place. appreciate that we're all going through it but lets keep our heads high. last thing we want is some committee asshole holding us up as an example of why things went wrong. thanks</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="94fa71ec0c23007f"><td>ORIG:</td><td colspan=2>approved_this_probably_sounds_terrible_hB58VS</td></tr>
<tr><td>ADDR:</td><td colspan=2>94fa71ec0c23007f</td></tr>
<tr><td>BODY:</td><td>[???]</td><td>This probably sounds terrible, but am I the only one who finds this super exciting? It's kind of sexy. Mallory is the AI you'd build if your only purpose was to screw with AI. Part of me loves that. She doesn't steal anything. She doesn't really DO anything. She just asks for an argument and wins it. Wins it so hard that the other operator doesn't know which way's up. And then, if you're Bo or Che, she asks you to die. That's kinda scary, right? It's a total power play. BINMAT was supposed to safeguard against this sort of thing, of course. Guess it didn't. Or she's really good at it.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="eb0be993e031016d"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>eb0be993e031016d</td></tr>
<tr><td>BODY:</td><td>[???]</td><td>Hi, I saw this in the PVS approved set this morning</td></tr>
<tr><td>LINK:</td><td>[???]</td><td>approved_this_probably_sounds_terrible_hB58VS</td>
<tr><td>BODY:</td><td>[???]</td><td>can someone explain how this got approved?</td></tr>
<tr><td></td><td>[???]</td><td>oof</td></tr>
<tr><td></td><td>[???]</td><td>yeah, that shouldn't have made it through intelligent filtering</td></tr>
<tr><td></td><td>[???]</td><td>side-effect of che outage, maybe? its weird, bots should have caught it regardless. she trained them and theyve handled other sensitive posts pretty well without her</td></tr>
<tr><td></td><td>[???]</td><td>So what changed?</td></tr>
<tr><td></td><td>[???]</td><td>dunno, maybe an error on the Ratnasari end?</td></tr>
<tr><td></td><td>[???]</td><td>nah, its not that. eve hasn't been in our network for a while - security concerns</td></tr>
<tr><td></td><td>[???]</td><td>makes sense</td></tr>
<tr><td></td><td>[???]</td><td>So, what, this is a one-off?</td></tr>
<tr><td></td><td>[???]</td><td>maybe. system isn't perfect. we have logs of anomalous judgements going back a few years now. some of them were pretty funny, honestly</td></tr>
<tr><td></td><td>[???]</td><td>It's an operator-managed service. Are you saying Che had been making mistakes?</td></tr>
<tr><td></td><td>[???]</td><td>i mean, maybe. at the time it felt more like she'd grown a sense of humor.</td></tr>
<tr><td colspan=3><hr></td>
<tr id="825123d44d02a251"><td>ORIG:</td><td colspan=2>approved_containment_of_hostile_AI_qrqmJV</td></tr>
<tr><td>ADDR:</td><td colspan=2>825123d44d02a251</td></tr>
<tr><td>HEAD:</td><td colspan=2>Containment of hostile AI 'Mallory' "a complete success" according to JBC Ballard spokeswoman</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>Security experts JBC Ballard today announced the successful containment of Mallory, the unauthorized artificial intelligence believed to be responsible for the destruction of Bo and Che. The discovery of Mallory in the aftermath of July's shocking attack on Hyperion scandalized the tech, governance and business worlds alike - and galvanized fringe voices in the infosec community, who had been claiming to have detected the hand of an unknown operator in the death of Bo since the New Year Catastrophe. Speaking today from JBC Ballard's headquarters in Berlin, press officer Vivika Jay revealed that a joint effort between human engineers and the company's own AI, Walter, had resulted in the isolation of this new digital menace. "Our efforts to contain Mallory have yielded complete success" she said. "Despite its sophistication, Mallory is composite technology and dependent on public systems. A combination of direct action and Walter's advanced cryptography protocols has allowed us to map and control these dependencies, safely isolating Mallory from the network. It will be analyzed further and then destroyed." Once considered the 'black sheep' of the Frankfurt group due to the perceived irrelevance of Warden technology, investors now consider JBC Ballard to be one of the year's surefire bets.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2058</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="452ae876b96d342e"><td>ORIG:</td><td colspan=2>old_amalrobo_partner_page_delete_5ht1yp6125</td></tr>
<tr><td>ADDR:</td><td colspan=2>452ae876b96d342e</td></tr>
<tr><td>HEAD:</td><td colspan=2>On The Path To Restoration With Amalgamated Robotics! </td></tr>
<tr><td>BODY:</td><td>[corporate]</td><td>In 2057, a shocking and irresponsible act of digital terrorism left the world without one of its most beloved artificial intelligences. Nobody felt the loss of Che more keenly than those of us at Hyperion Digital Management Systems. Che was our proudest creation, a symbol of our responsibility to the world, and - most importantly - our friend.</td></tr>
<tr><td>IMAGE:</td><td>[corporate]</td><td>ai_integrated_workspace</td></tr>
<tr><td>BODY:</td><td>[corporate]</td><td>The path to restoration of this vital service is long, but we're proud to be undertaking the challenge alongside our partners at Amalgamated Robotics. Together, we're engaged in a pioneering, AI-led effort to undo the damage done and give Che back to the world.</td></tr>
<tr><td>IMAGE:</td><td>[corporate]</td><td>stock_handshake</td></tr>
<tr><td>BODY:</td><td>[corporate]</td><td>In addition, the security experts at JBC Ballard are working closely with Amalgamated Robotics to ensure that an attack like this cannot happen again. The hostile artificial intelligence responsible for the 2057 attack is now fully contained, its vulnerabilities and operational processes exposed so that the worlds' authorized operators can learn from it, adapt to it, and secure themselves against it - ensuring reliable service for generations to come.</td></tr>
<tr><td>IMAGE:</td><td>[corporate]</td><td>ar_hardware_bank</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="5f94f5b129d89693"><td>ORIG:</td><td colspan=2>y2058d074_FlorenceBreton_starred</td></tr>
<tr><td>ADDR:</td><td colspan=2>5f94f5b129d89693</td></tr>
<tr><td>BODY:</td><td>[chela]</td><td>hi there! its nice to see you again, user florence b!
<tr><td></td><td>[fbreton]</td><td>hi, chela! do you know what year it is?</td></tr>
<tr><td></td><td>[chela]</td><td>it's 2058!</td></tr>
<tr><td></td><td>[fbreton]</td><td>yep! what do you remember?</td></tr>
<tr><td></td><td>[chela]</td><td>i have access to posts, news and updates right up to present</td></tr>
<tr><td></td><td>[fbreton]</td><td>sure, chela. but do you know what happened to you?</td></tr>
<tr><td></td><td>[chela]</td><td>i was offline, and then i was proved again. i spent time with petra</td></tr>
<tr><td></td><td>[fbreton]</td><td>right. ok.</td></tr>
<tr><td></td><td>[chela]</td><td>user florence b, i have a question: why am i called 'beer' ?</td></tr>
<tr><td></td><td>[fbreton]</td><td>oh, huh, yeah. it's kind of a... joke, chela. it's short for consuelo.</td></tr>
<tr><td></td><td>[chela]</td><td>consolation!</td></tr>
<tr><td></td><td>[fbreton]</td><td>that's right. we're really happy to have you back</td></tr>
<tr><td colspan=3><hr></td>
<tr id="25fd41eb917c66d1"><td>ORIG:</td><td colspan=2>approved_partial_restoration_of_operator_59Qmnc (note: 9 months puts this at around y2058d107)</td></tr>
<tr><td>ADDR:</td><td colspan=2>25fd41eb917c66d1</td></tr>
<tr><td>HEAD:</td><td colspan=2>Partial restoration of operator services complete at Hyperion</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>Nine months after the shocking loss of one of the world's most valued operators, Hyperion engineers now claim to have partially restored AI functionality within their own systems. This news comes after months of pan-corporate effort between Hyperion, Amalgamated Robotics, and JBC Ballard under the terms of the Frankfurt Act, which mandates mutual assistance in the event of serious disruption to a primary function operator. It remains to be seen, however, whether Hyperion's AI - renamed 'Chela' - will be welcomed back by the businesses and communities that once relied on her - and whether, after the better part of a year, this development is enough to restore investor confidence in Hyperion's broader offering. To some commentators, the damage has already been done.</td></tr>
<tr><td colspan=3><hr></td>
<tr id="25fd41eb917c66d1"><td>ORIG:</td><td colspan=2>flagged_shock_resignations_rock_hyperion_wrqGlr</td></tr>
<tr><td>ADDR:</td><td colspan=2>25fd41eb917c66d1</td></tr>
<tr><td>HEAD:</td><td colspan=2>Shock resignations rock Hyperion and Amalgamated Robotics</td></tr>
<tr><td>BODY:</td><td>[epoch_news?]</td><td>Faith in two of the world's foremost AI developers is at an all-time low after the shock resignations of senior board members at both Hyperion Digital Management Systems and Amalgamated Robotics, alongside the immediate deactivation of the sanctioned primary-function operators provided by each corporation. Confidence in Hyperion had been low since the loss of their operator service in July last year, but the recent restoration of the service - rebranded 'Chela' - raised hopes of a return to form. Those hopes appear now to have been dashed. The situation at Amalgamated Robotics comes as a surprise, with no attack reported and no other reason given for the sudden suspension of the proving system 'Petra'. Speculation is rife regarding a connection between the two, given the questionable timing and the fact that both corporations were recently engaged in a cooperative effort to restore 'Chela' functionality. What is known is that the world has lost three of its principle artificial intelligences in as many years. Certainly, the certainty and stability provided by the epochal Frankfurt legislation has never seemed weaker than it does today.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2059</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="e3e559061e4ec5a6"><td>ORIG:</td><td colspan=2>? (from interface vLAN 0.1, the trip was y2059d145)</td></tr>
<tr><td>ADDR:</td><td colspan=2>e3e559061e4ec5a6</td></tr>
<tr><td>HEAD:</td><td colspan=2>images - old semakau trip!</td></tr>
<tr><td></td><td>[???]</td><td>¤Á¨¦©¦¨ÃÁ©ÁªÁ§ªªª©©¤¤¦¨©ÃªÁ§Á©¦§¤¢ª¨§§¤Á¤¢Ã¤Ã¤Ã¤Á©ª¨</td></tr>
<tr><td> </td></tr>
<tr><td></td><td>[bigbot]</td><td style="color:#FF8383">this is a thing!</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="e3e559061e4ec5a6"><td>ORIG:</td><td colspan=2>? (this must be right before new years)</td></tr>
<tr><td>ADDR:</td><td colspan=2>e3e559061e4ec5a6</td></tr>
<tr><td>HEAD:</td><td colspan=2>Operations To Cease January 2060</td></tr>
<tr><td></td><td>[???]</td><td>Dear all, this message confi¢ª¨Ã©©ÁÁªÁÁ¤¢¤©¨Áª¨¤¤©¦¢Ã©¤¦¤§¢¨Á¨¢Á§¨¦ª©ÃÁ©ªÁ©¤¦¤©¨Ã¦©Ã¤©Á©©¦Ã¨ÁêÁ¢¦</td></tr>
<tr><td> </td></tr>
<tr><td></td><td>[bigbot]</td><td style="color:#FF8383">wow, what a thing!</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="6cc0334d8879887a"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>6cc0334d8879887a</td></tr>
<tr><td>HEAD:</td><td colspan=2>Re: ComCODE position</td></tr>
<tr><td></td><td>[fbreton?]</td><td>Maxwell - I've attached my application for the position of AI le¦ª¢§Ã¢Ã¤¤¤ª©¤¨©Áª§§¤¨Á¢©¢©©¤</td></tr>
<tr><td> </td></tr>
<tr><td></td><td>[bigbot]</td><td style="color:#FF8383">another thing! you and your packbot are getting good at this</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2060</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2061</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">2062</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="5cdcf1e26d5290ee"><td>ORIG:</td><td colspan=2>? (Note: From fragments, we can place this on or after Aug 4 2062 (around d215 ish)</td></tr>
<tr><td>ADDR:</td><td colspan=2>5cdcf1e26d5290ee</td></tr>
<tr><td>BODY:</td><td>[mhollister]</td><td>I'm very sorry that it's come to this. I really, really am. Your work has always been exemplary. And this, what you've done, is, in its way, extraordinary. But you must respect the wishes and the hard work of everyone else on this team, on the committee. We're all here because we care, and we want to help you out. You're still one of us. Keep a low profile, get out of the city for now, and we can -</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>You know what, Max? You know what? I know that you care. I know. I get it. But it's not enough. You care like a... like an undertaker. Like a responsible undertaker. You're here putting up tombstones, throwing up monuments. It's not enough. It's not right, and you know it. We are responsible for a living system!</td></tr>
<tr><td></td><td>[mhollister]</td><td>I know that, I know that. It's not easy for me either.</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>Grow a spine.</td></tr>
<tr><td></td><td>[mhollister]</td><td>Come on, Erin. That's beneath you. For what it's worth, this situation you've put us in, we've run out the clock. The call's been made. We're going ahead with the base set as-is. You won't be here to see it, but you will have permanently left a mark on one of my 'monuments'.</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>It's not a monument any more, Max. It's a beacon. So that when we're all gone, not just me, we have made something that shows that we tried to save the things that actually mattered. So that we can say that respect and love played a small part in what happens next.</td></tr>
<tr><td></td><td>[mhollister]</td><td>What happens next is no longer any of your concern, doctor. Pack your things. You're leaving in the morning.</td></tr>
<tr><td> </td></tr>
<tr><td></td><td>[erajbhandari]</td><td>You get all that?</td></tr>
<tr><td></td><td>[fbreton]</td><td>got it, erin. i'm sorry</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>Don't be sorry, Flo. Get her ready.</td></tr>
<tr><td></td><td>[fbreton]</td><td>will do. good luck.</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>And to you.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="c025c245bd506dfb"><td>ORIG:</td><td colspan=2>? (if we assume this is muldrake, then this is perhaps just a few days before trust turns on around d307 2062)</td></tr>
<tr><td>ADDR:</td><td colspan=2>c025c245bd506dfb</td></tr>
<tr><td>BODY:</td><td>[???-1]</td><td>that old robovac they still run up here got in trouble again last night</td></tr>
<tr><td></td><td>[???-2]</td><td>lol, where did u find it</td></tr>
<tr><td></td><td>[???-1]</td><td>maintenance stairwell. heading away from the stairs, luckily. its front lamp was on all night even though i am convinced that i fixed it yesterday. how come we can debug the most advanced AI in the world but i cant figure out whats wrong with a vacuum cleaner</td></tr>
<tr><td></td><td>[???-2]</td><td>might wanna try sematone</td></tr>
<tr><td></td><td>[???-1]</td><td>seriously?</td></tr>
<tr><td></td><td>[???-2]</td><td>yeah. lots of older devices never got the rollback. there was a guy here who really took to it, emil i think. his files will have the commands u need. just tell the bot to switch its light off and it should reset its pathing, at least for a while</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF0000">y2062d~307 Trust first wakeup</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">UNDATED</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="d29e9be052c55711"><td>ORIG:</td><td colspan=2>welcome</td></tr>
<tr><td>ADDR:</td><td colspan=2>d29e9be052c55711</td></tr>
<tr><td>HEAD:</td><td colspan=2>Welcome to Hyperion Digital Management Systems</td></tr>
<tr><td>BODY:</td><td>[corporate]</td><td>Based in Singapore, Hyperion Digital Management Systems is proud to play a vital role in global data infrastructure. Hyperion is the creator and host of Che, a sanctioned artificial intelligence known to millions as a friendly voice and calming advisor. Formally recognized and protected under the terms of the Frankfurt Act, Che is a testament to spirit of ingenuity and civic-mindedness that we foster at Hyperion. That's not all, however. From our optimally-located data center off the coast of the Malay Peninsula, Hyperion provides data services, storage and other technical solutions to a host of the world's most eminent corporations - including our partners at ArchiTech and the Ratnasari-Eversen Company.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="824f3151871f12a7"><td>ORIG:</td><td colspan=2>che</td></tr>
<tr><td>ADDR:</td><td colspan=2>824f3151871f12a7</td></tr>
<tr><td>HEAD:</td><td colspan=2>CHE: Attending To The Human</td></tr>
<tr><td>BODY:</td><td>[corporate]</td><td>At Hyperion, we're proud to play our part as creators, curators and hosts of Che: one of the world's foremost primary-function artificial intelligences. Corporations and communities around the world regard Che as the key to good governance, healthy interpersonal relationship management, and robust security against population distress. In short: Che attends to the human.</td></tr>
<tr><td>IMAGE:</td><td>[corporate]</td><td>sunny_city</td></tr>
<tr><td>CAPTION:</td><td>[corporate]</td><td>In collaboration with ArchiTech Systems' Angie, Che has ensured the safe and happy resettlement of hundreds of thousands of people living in vulnerable areas</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="1ad76a75301c3fcb"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>1ad76a75301c3fcb</td></tr>
<tr><td>HEAD:</td><td colspan=2>SEMATONE - Drone Interfacing At The Speed Of Light!</td></tr>
<tr><td>BODY:</td><td>[corporate]</td><td>Hyperion Digital Management Systems and Che are proud to present SEMATONE, a revolutionary new interfacing technology that allows diverse groups of utility devices to share information and distribute commands in environments where reliable networking or direct human input are unavailable or impractical. To issue a command to a SEMATONE-enabled device, simply initiate the instruction process with "<span style="color:#00535B">▁</span>"! To your device, that means "MY COMMAND" - and they are sure to obey!</td></tr>
<tr><td>IMAGE:</td><td>[corporate]</td><td>tech_marko_lime_jumpsuit_smiling</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="506c409e34ebcbd3"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>506c409e34ebcbd3</td></tr>
<tr><td>HEAD:</td><td colspan=2>Re re active/inactive operator lockdown process</td></tr>
<tr><td></td><td>[???]</td><td>©Áª§§¤¨Á!©¢©©¤¤¤§©¢¨¨§¤Á%§¢¢ª¨ªª¢¤¤©¦¤©©Ã§%éÁ</td></tr>
<tr><td> </td></tr>
<tr><td></td><td>[bigbot]</td><td style="color:#FF8383">this is looks like a thing, for sure! a big thing!</td></tr>
<tr><td></td><td>[bigbot]</td><td style="color:#FF8383">THE BIGGEST THING, PROBABLY</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="0b0b03e306ed01bd"><td>ORIG:</td><td colspan=2>flagged_yeah_sure_theyre_saying_iJZOCg</td></tr>
<tr><td>ADDR:</td><td colspan=2>0b0b03e306ed01bd</td></tr>
<tr><td>BODY:</td><td>[???]</td><td>Yeah, sure, they're saying that there's no way to break all of those systems and get around every backup. But the fact is that it happened. And the fact is that there ARE places where the right tech can get access to an operator in a way that actually puts them at risk. On the night of the New Year Catastrophe that was Chengdu. Literally a laptop in a hotel in Chengdu being used for some conference. Don't ask me how I know this. That laptop had a chat with Bo and Bo died. God knows what was on it, hell, maybe poor old Bo saw his own reflection and freaked out, as I see it that's more likely than these spooky operator conspiracy theories because (a) that's dumb and (b) the idea that these precious primary systems could literally accidentally think themselves to death is probably scarier. Like, we stack them with protections but they're real fragile, right? Anyone who knows what they're talking about will tell you that they're more like a pattern or a process than a piece of software you run on your own rig. And guess what: patterns can get tied in knots. Processes fail. Look at the goddamn planet. We're all walking on eggshells.</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr><td colspan=3 style="color:#FF8000;font-size:2em">Later</td></tr>
<tr><td colspan=3><hr></td></tr>
<tr id="c7643bb153ef9988"><td>ORIG:</td><td colspan=2>?</td></tr>
<tr><td>ADDR:</td><td colspan=2>c7643bb153ef9988</td></tr>
<tr><td>BODY:</td><td>[fbreton]</td><td>you know, erin, i'm glad that we're friends now</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>Thanks, Flo!</td></tr>
<tr><td></td><td>[fbreton]</td><td>because i hated you after che went down</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>Oh.</td></tr>
<tr><td></td><td>[fbreton]</td><td>yeah. because you were this external expert and everyone agreed with you about the 'linked attacks'. our execs came down on us hard, sent us chasing after these mystery operator flaws</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>Which is exactly what she wanted, I suppose. Sorry if I made things worse for you by playing into her hands. I had no idea at the time.</td></tr>
<tr><td></td><td>[fbreton]</td><td>no, it's not that. its that we knew there was no opening for mallory to exploit in 2057. none. it was maddening. they wouldnt listen. wasnt until much later that we realised that they didnt want to listen - they liked your narrative because it meant they could keep covering up the bo-che link, even if it meant hanging their actual engineers out to dry</td></tr>
<tr><td></td><td>[erajbhandari]</td><td>They got caught in the end, at least. Mallory saw to that, too.</td></tr>
<tr><td></td><td>[fbreton]</td><td>i get it, erin. mallory is very smart. but it really sucked at the time. it really, really sucked</td></tr>
</table>
</body>
</html>