OOC Conference Discussion

[Wes]

Talking on the phone with Doshii and we're working out a good solution.

 

[Doshii Jun]

Wes and I talked over the phone. We worked this out. (Talking over the phone is really a lot more efficient.)

Nepleslia's most major concern here is the DREI system and securing it. Yamatai's concern is the presence of the IPG on a station full of dissidents that they, frankly, don't want arrested.

Neps, let me know if this works: The IPG will be able to sit down with Wazu. They can interrogate him, with YSA agents watching from behind glass, until they get what they want: Wazu turning over full control, ICly, of the DREI system. Keep in mind the YSA agents won't be listening, just watching. At the end of it, Wazu gets sent back to Gartaga, but Nepleslia gets what they want.

Zack: This means you need to let go of DREI and not try to backdoor it, or anything else Nep-related, for the duration of your stay here on SARP. Your character can continue on as he has in Gartaga, and he's still booted from the IRC.

This lets Yamatai save some face, but also foster good relations with Nepleslia, which they need.

 

[Zack]

Well, so far no one knows he has built in numerous backdoors into Nepleslia should he need to use them.

As far as I'm concerned just knowing about that is displaying knowledge far beyond what anyone on Nepleslia should have at this point. The IPG are welcome to take Wazu in, but they need to stick to operating only on things they know ICly.

As per the original agreement, they would have to RP out some investigation of Wazu. If they find any wrongdoing there they could then act on that but right now there are no outstanding criminal charges against him on Yamatai (pardon) or Nepleslia (nothing to go on in the first place).

 

[Wes]

Then the interview will give him the opportunity to tell them about the back doors. We need the Drei control back in Nepleslian hands rather than Wazu's. Figure out a way to make it happen.

 

[Kokuten]

That sort of thing has been handled for a while. Drei's been replaced by SAVtechs to help usher in a fresh, new A.I. software.

 

[Wes]

That isn't true until you RP it and also update the wiki pages.

I suggest you solidify things with an NTSE thread on the transition of AI systems and then ensure it is noted in each plot ship.

 

[Sigma]

Breaking my leave of absence to point out one inconsistency. If we go by that principle, then anything Wazu says cannot be true since there's no RP to show Wazu not deserting the DIoN, or explains how he ended up in Gartland, or wiki updates to back it up. If we're to follow strict IC stuff, so should everyone else. Fair's fair.

I leave you all to consider what this means with relation to handling Wazu and the gaping holes in his history.

 

[Zack]

Actually, there was an OOC agreement that covered what happened while I was away, and this RP picks up where that leaves off: viewtopic.php?f=135&t=7635

(And Ira didn't edit out his opening line like I had on the titanpad >.>)

So in the mean time Wazu still has his control over things, Nepleslia still doesn't know about the backdoors he left for himself in their systems, and he still chooses not to cause any trouble for them because that isn't what he does.

In short, lets focus on playing the game.


---


There is a slight issue of where Wazu is standing right now. I was under the impression he had been let go and Moonie has him behind some bars.

I'm thinking it is some sort of holding area just outside the YSA substation with a door he can walk out of?

 

[MoonMan]

Don't go assuming that other people using these systems wouldn't notice such backdoors, now. Wazu is a smart man, but he's definitely not the only one.

The bars problem I've fixed; Kokuten informed me of where they were when I originally thought he was still being detained in a holding cell.

 

[Zack]

When it comes to smart characters Wazu is almost always the smartest man in the room. I do not think anyone would have noticed if I didn't point out the subtleties in the wiki article.

Someone might figure it out but they'd need to go through the process and that'd be an RP in and of itself tracking down the backdoor and then verifying it even exists.

 

[Wes]

It'd be easiest to just make a new AI, and then switch ships to use the new one not because of suspected back door, but simply because the new system is newer/better. Then the problem is solved, and you also get a new setting element.

Or Wazu could just give up his access (for real) in the RP like Doshii and I wanted to do.

 

[MoonMan]

If it's being used in Nepleslia and other plots, full disclosure of this AI will be at the FM and GM disposal. They need not ask for your permission.

When it comes to smart characters Wazu is almost always the smartest man in the room. I do not think anyone would have noticed if I didn't point out the subtleties in the wiki article.

Wiki articles are for information. Not trickery or cheese.

Nepleslia is going to be using an update of the DREI regardless, without Wazu's loopholes. So it really doesn't matter much.

 

[Doshii Jun]

Thanks for the shifting post, Doc. I'm occupied this weekend -- see my Starlight Lounge thread -- but might get posting time. I'll let you all know.

 

[Kokuten]

"Turns out that new AI of yours had some rather glaring security issues. NAM was made aware of them by that one woman... ah... Cassefin Montreal?" The ID-SOL wondered aloud, in slight exaggeration. "From that research station, the Cirrus. Found them and informed us right quick. -- "

Cassefin... did something right?

 

[Aendri]

Lies! Cassefin is incapable of doing right.

 

[Wes]

She could have just taken credit for it.

 

[Abwehran Commander]

Sounds like something she'd do.

 

[Kokuten]

“I am sure your lady Cass knows what she is doing, but you should really have a Vel Steyr double check the work.”

NOTE: Melchior Vel Steyr died in the terrorist attack on Nepleslia a year ago.

 

[Doshii Jun]

Wazu: "Even the dead are better than a woman fixing my work."

 

[Zack]

Wazu: Only the dead have truly seen the end of segfaults.