Skull132

What teamspeak were you even on? Because, uh, we don't have a Teamspeak, and Knowher is not even a member of our community (as far as I know).

5/10 explanation, Jboy. "Not relevant to us," is not an excuse for an unsecure system. Nor is it something I'm willing to accept, regardless of your ignorance to the threat. The system in question did not meet security standards. It was piss easy to get an actual password out of the tables, were the database tables ever leaked. So I nuked the entire password's column way back in January. Then I discovered, a few months ago, that people could still register accounts. And were still using it. Despite an old notice of it having been killed, and the system being left to fade to (presumed) obscurity. Obviously this didn't happen. So I nuked the passwords again, and pretty much disabled the login and registration systems. Sierra did make an emergency patch, but it was not implemented due to me being busy at the time with other tasks, and at present, the patch does not match the standard set by our other interfaces. The plan is to eventually roll this functionality into the https://byond.aurorastation.org interface. But first, IC emails.

Tbf, it is kind of breaking character, the killing of mice via stomping, in some cases. Obviously depends on your char. But I do not care, because the presence of mice is exaggerated by mechanics. As such, the character's reaction to them can be exaggerated as well.

No, because none of them are meant to possess any intelligence what so ever.

Do note that a title that requires clarification on a regular basis has failed its primary purpose: the distinction of personnel, their role, and authority.

"The captain" vs "Captain Sir Soldier Dude". As for the administrator title. The authority he has over the station is left unclear by the title. A fitting alternative would the Commanding Officer, or something of that nature. "An administrator" or "overseer" can mean more things than CO.

I wonder what the turnout is going to be. General rule of thumb is, 1 week of warning + new thread. Otherwise, people will not know. We'll see how accurate that is, though.

Jackboot Edit: Baseline added but the situation with EE is complicated, first draft will remain as is until its sorted with Delta. Name: Apex & Ft Sunder Joint Military Academies Link to Lore Canonization: http://forums.aurorastation.org/viewtopic.php?f=79&t=490 Focused Field: Intermediate and higher level military education. Civil defence to a degree, since the Army is focused on internal matters as well. Anything from officer schooling to things like cyber security. Overview: During the inception of the Eridani Federal Military, it was quickly deemed that the relatively small force it was planning to sustain did not require multiple schools serving the same purpose for two branches of the military. As such, an agreement was brokered between the Federal Navy and the Federal Army, with the intent of handling all common intermediate to advanced schools as a joint initiative. This way, specialists from one branch became responsible for training candidates from both branches. Over the next hundred years, the division of fields quickly became clear. Since the Federal Navy was being actively tasked with offensive operations both in space and on the surface of foreign planetary bodies, their focus became the training of infantry warfare specialists. Almost all specialized and advanced infantry schools are organized by the Federal Navy in their own facilities, with the majority of such schools residing aboard the military station of SEN Apex. These schools include the ones responsible for training all grades of Non-Commissioned Officers, and specific courses for special forces operatives. This left the more academic fields under the governance of the Federal Army. All junior officers go through the Officer Candidate's Course hosted by the Federal Army in Fort Sunder, and they also have a master's programme for advanced military leadership. The programme in question issues all graduates a master's in social sciences. They also handle the training of cyber-warfare and -defence specialists, who follow the standard route of academic achievement. (Though, they may subcontract these studies to external universities.) Also of note is the training they offer in the field of civil defence, due to the Federal Army's major role in assisting the local police forces. For example, all Federal Navy candidates for the Master at Arms specialization go through one such programme hosted in Fort Sunder and Fort Atrix, by the Federal Army. While the Joint Military Academies initiative serves as a great method of cost minimization and permits a very high degree of specialization and concentration of experience, it has received a lot of critique. The primary issue raised is the fact that it increases the dependence of the entire Federal Military on two key facilities, which are already loaded with command, control, and communication tasks for their specific branches. The concern is that should one of those two facilities be struck half of the training pipelines in the entire Federal Military would grind to a halt. While the Federal Army has been looking to spread its training out to subcontracted state and private universities, as well as to other bases, such as Fort Atrix, the Federal Navy has remained confident in its ability to recover and reorganize as necessary. Though, there have been rumours that the pressure applied by Federal Army has resulted in the commissioning of another major space station, which should take over the task of serving as a hub for the majority of the training programmes hosted out of SEN Apex. Main employer of graduates: The Eridani Federal Military itself. Any contractor who is able to snatch itself people from the Eridani Federal Military, such as NT. Current Dean: General Donn Magadan of the Eridani Federal Navy. Famous Graduates: RIP.jpg

As a note, I agree with the sentiment of not giving them stun. It'll make them too powerful and too handy. They're meant to fulfill a very specific role, and, ideally, would only be used if that niche situation comes up. As for giving other borgs the mobility module. No. It's too powerful to be issued out, per standard, to all roles other than the combat module. The combat modules amazing downside balances it out.

Sometimes, players are awful. If they keep being awful, we'll just restrict their access to their toys! To an extent, anyways. The mentality is well applicable here. Plus, having that second swipe will clear up the mountain of potential conflict between command staff/sec and the synths/borgs. And it also makes sense, as not every red alert is a combat emergency.

Alberyk has already proposed the idea of combat borgs requiring a second swipe during code red. This way, command staff has full control over when they're getting deployed. If you've already swiped for code red, then it's not too much hassle to swipe for combat borgs right after that, should they be required.

Put both up! Unless there's something technical stopping you. If there is, maybe I can help.

Same time which time? The originally designated time (1600hrs Zulu)?

This is probably the most important rule. If sec is trying to slide you a warning or, you know, actually come forward with a solution to the problem. It's a good idea to go with it and to not be an ass later on without a legitimate reason! It'll reinforce the officer's behaviour, and they're more likely to repeat it later on.

"THE ECONOMY" is currently in the conceptual development phase. Meaning, a developer is writing up a design document to present for review. Once that document is approved, it'll be put into active development. Due to the size of the project, however, it'll take a bit of time to reach implementation.

Updated times: 10SEP2016 1900hrs Zulu/GMT+0 1500hrs EDT/GMT-4 1400hrs CDT/GMT-5 1300hrs MDT/GMT-6 1200hrs PDT/GMT-7 2000hrs BST (British Summer Time)/GMT+1 2100hrs CEST (Central European Summer Time)/GMT+2 2200hrs EEST (Eastern European Summer Time)/GMT+3

Ban lifted. Enjoy your day! If it still shows you as banned, please PM me and I'll look into fixing it.

Wait, this doesn't make sense. With the chance of being nitpicky as hell, if I may... Three different cases: - Being "Contracted to work on the Exodus" - Being contracted to work for NanoTrasen in general - Being promoted while aboard the Exodus as a visitor Point one makes no sense what so ever. It would be easier and clearer to state that, "Visitors to the NSS Exodus are not listed as currently active duty personnel for the duration of their stay," or something like that. It is not your assignment at that specific moment to deal with the crap that's unfolding, and the preference should always be on the people who are on active assignment to the Exodus. Semantics, yes. But semantics, in this case, matter. As does clarity of communication. I do agree with the principle, though. Active duty personnel are active duty for a reason, and off-duty personnel should only be utilized in menial roles at most. Don't promote Visitor Doofus because he's your bud, promote the person who's actually given the task of taking care of this shit today.

Eh, you didn't do anything outright awful, so I'm good for another go. Just make sure you read the rules and stick to them. And adminhelp if you have questions. If there are no objections, I'll lift this tomorrow.

Ban is assumed to be legitimate until evidence to the contrary is presented. But in the absence of the banning admin, usually the Head Admin (one of them) takes over the case. Or any other admin. Considering the time passed, I'd say you're good for a second go. I'll poke at the admins with this.

Dat forum username tho. Ban is by Nightmare00, who's retired from adminship now; and was originally placed on DEC2014. No associated notes that I was able to find.

The VM-ing in combination with the LAN-ing did it. Once one of those signatures enters the database, it's enough to create a neat little spider's web of ban mirrors. Hopefully Serv found all of the references and lifted them.

Timezone conversions for Europeans and people who know what to do with them: 10SEP2016 1600hrs Zulu/GMT+0 1200hrs EDT/GMT-4 1100hrs CDT/GMT-5 1000hrs MDT/GMT-6 0900hrs PDT/GMT-7 1700hrs BST (British Summer Time)/GMT+1 1800hrs CEST (Central European Summer Time)/GMT+2 1900hrs EEST (Eastern European Summer Time)/GMT+3 Yes, everyone is still on summer time. Deal with it.

This will be removed from extended. And it'll also be tweaked to only have antags with fast start-up times. Like traitor, for example. Antags like cultists (which take a minimum of 30 minutes or more to get organized) will be removed from it, as they would have a null effect if integrated into the round at a later date.

Roughly 10 hours ago, someone made a Reddit post on /r/ss13 displaying what they claimed to be hashed passwords acquired from one of our (unspecified) databases. After a short bit of investigation by our staff, thank you Arrow768 for that, we determined that, with the evidence currently presented, we have determined that the leak is bogus. The hashes presented do not match any hashing format that we use to store passwords on our databases. After a sweep of all logs and other security measures, no further evidence of a compromised database was found. As such, we are led to believe that our databases are not compromised until further evidence is presented. If anyone has any questions, comments, or concerns about this incident in specific, or regarding the security measures we use, then feel free to ask. Also, while this specific leak may be bogus, no system is 100% secure! Keep in mind the fact that if someone really wants to fuck with us, or with you, they will eventually do it! Provided they're driven enough, anyways. This is why you should follow the following steps as standard MO: Change your password after even a potential leak (right now included). Don't reuse passwords, it's a horrible practice. If possible, use unique emails per site (Gmail has a fancy way of doing it, if memory serves), or at least two emails, one for junk sites, one for srs bsns. Use strong, unique passwords for every site. Enable 2 Factor Authentication whenever possible! Specially if you have access to sensitive services, such as GitHub or for your password manager! Use a credible password manager with a strong master password. Or use a physical method of password storage, if you're old school, a piece of paper works.