Quarantinetimer

I support Nanako's solution. Here are some of my reasons. While the AI does accept connections from remote computers (several ports are likely reserved for communicating with the AI, as it needs to control the NT intranet), attempts to alter it's system programming from these remote systems will not be accepted. It does this through something akin to a DMZ. The AI servers dealing with packets originating from the wider NT intranet are sandwiched between two firewalls. The firewalls provide deep packet inspection (possibly with limited "intelligent" functions that transcend the problems faced by current methods), and these external packets cannot pass through into the AI core network under normal circumstances. Oh, and did I mention the honeypots? As you can see, it is probably extremely difficult to penetrate the security of something as vital as an AI, unless there's some novel exploit (hacked traitor module?) that manages to get pass all these measures, or the attacker manages to perform social engineering on 2 heads of staff at once, which is impressive feat that deserves being recorded in the hall of fame.

This hasn't been binned...so, bumpity bump.

I used to discuss this on OOC in bay, and the opinions I received were mainly about the appropriate level of complexity. Aurora is, after all, not a simulation for medical students. Is it too complex that it becomes inaccesible? Is it too simple that it ruins (insert your points)? Personally, I do agree with distinguishing between an antibiotic and an antiviral. The true extremist will suggest that we implement multiple types of both drug classes. Just to give an insight to the lengths some may go to, here is the average medical role-player's worst nightmare:http://irc.liber-mundi.org/trauma.php?lng=us

An oxygen candle is also pretty much as fool-proof as these devices can get.

So, currently, we have two colors of pens, red and blue. What is the NT policy for using each color? (Should be used on which documents/forms, by whom, for what purpose etc.)

Some dev response as to whether this is possible would be nice.

Only valid IDs can reset the nameplate, meaning when someone cryos, the replacement will be able to reset it. I don't think they should cross check the employment database, as it isn't that important and the functionality is expensive.

If someone knows how to translate that goddamned m2000c french manual, please reply here. The Manual: http://www.avialogs.com/en/aircraft/france/dassault/mirage2000/manuel-pilote-mirage-2000-c.html

Just to add some more flavor, I propose that we have holo-nameplates on desks inside an office. So Each head of staff will have a holo-nameplate on their desk, and the IA office will have one plate on each desk (don't forget the chaplain!). Basically, when an ID matching the job (hereby called a*valid ID*) gets swiped on the plate, the character's name and job title appears on the plate, just like badges. From a half-educated guess, I believe that it will not be overly difficult to implement such a feature.