![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
[audio:]
[L’s voice is the voice he’d use for any public announcement: smooth, measured, calm, not betraying much of the intense irritation and frustration that the network crash has caused him in the previous few weeks.]
Greetings. This is Ryuuzaki, speaking for the Communications Department.
The recent problems with the network were caused by an attack on our systems by a particularly malicious virus. Its effect was to systematically overwrite existing material with random characters. The department itself had no control over this and no effective way to stop it.
When network service returned, it was because a fail-safe rebooted the network software itself, something we’ve never had the authority to do -- or, to be honest, the desire. We are now active on the ship’s original network, and have learned that the system that we’ve always used in the past was actually a subnetwork.
[As far as he’s concerned, every bit of this is a clue about why posts from prior to the arrival of the first wave of passengers are only sporadically available. Was the network previously rebooted in response to an infection with the same virus, or something even worse? That doesn’t explain how they would have ended up on a subnetwork, but it might explain much of the rest of it.]
As some of you may have noticed, nothing posted prior to the network’s return has been accessible since then. One of the functions of the Communications department is to archive network activity, and fortunately, we were able to back up the vast majority of the network as it existed before the emergency shut-down.
I’ll be posting what I can of that archive in a minute. However, please be aware that we don’t have the technical capacity to make this available to you in the format you’re used to, and that any posts from the old system that had been subject to an encryption created by one of us are completely incompatible with the new one.
[A beat of silence.]
Related to that: while we’ve been trying, no one in the department has yet been able to create new encryptions that work on this network, and the built-in privacy function seems to be much stronger and more reliable than it was before. We can’t say that the privacy function will be reliable forever -- very likely, it will be broken in the future, which will compromise the security of anything you’ve done using it -- but it appears that it’s currently dependable. This also does not rule out the possibility that someone we’re not aware of has the ability to break it already.
If you’re able to create an encryption that the network will accept, or if you simply have skills in this area that you’d be willing to put to work, please let us know, and please consider joining the department. [He is now turning on the charm, such as it is, and sounds slightly wittier and less serious than he had earlier in his announcement.] We’re not short-staffed at the moment, but we wouldn’t want to let your talents go to waste.
Those of you who don’t have talents in this area should consider joining another department. Agriculture could certainly use your help, even if it’s only for a few hours a week.
[The lightness in his tone now vanishes.]
On an associated note, if you receive any anonymous messages in your inbox, particularly from someone calling themselves Lina, or attempting to strike up a conversation and fish for information, please let us know. The same goes for any situation in which your communication device otherwise behaves in an unexpected way, and if you can visit the Comms Hub with your communicator while any of these things are still ongoing, so much the better. We’re located near the Bridge.
We’re aware that it’s common to come from a place where this kind of network communication is unusual. If you need help learning how your device works, let us know. We also have several programs which can be added to it, and some people may be able to make music or game files available to you. Those were programmed for your communicators, not the network itself, so it appears that they’re still compatible.
Finally… [a hint of regret enters his voice]... as of the jump several days ago, Clara Oswald has left the ship.
If you have any further problems involving the network, please contact me or Bail Organa.
Thank you. Comms out.
--
[Filtered to Tyke | Private]
If we learn that someone onboard has falsified an anonymous conversation similar to the one I just mentioned on the network, particularly if they do so in the future, can Security consider a suitable punishment? I had to discuss the messages here, but doing it so publicly is likely to encourage pranksters. I'd really prefer that they didn't waste my time.
Likewise, we’re still looking into the matter of the virus. If it turns out that someone is responsible for it, I’d like them to be subject to brig time.
--
[OOC: Please note that even the most talented hackers won’t be able to get into posts marked private for at least three months, and new characters will probably need about that much time to get up to speed with this system after they come in! It will not be a smooth road, either: the new system has many built-in blocks and tricks, and some hacking attempts will even flag SEC.
The link within the post is to an open Comms log. Please have your character drop in if they're interested in being tutored in the ins and outs of smartphones, or if they want to ask a question, or if they want to bug someone who's trying to work.
The batch archive of posts from the old network is here! It covers everything prior to November 1, 2014, or a week before the 37th jump by TQ Reckoning. Notes related to technical aspects are on that post.]
[L’s voice is the voice he’d use for any public announcement: smooth, measured, calm, not betraying much of the intense irritation and frustration that the network crash has caused him in the previous few weeks.]
Greetings. This is Ryuuzaki, speaking for the Communications Department.
The recent problems with the network were caused by an attack on our systems by a particularly malicious virus. Its effect was to systematically overwrite existing material with random characters. The department itself had no control over this and no effective way to stop it.
When network service returned, it was because a fail-safe rebooted the network software itself, something we’ve never had the authority to do -- or, to be honest, the desire. We are now active on the ship’s original network, and have learned that the system that we’ve always used in the past was actually a subnetwork.
[As far as he’s concerned, every bit of this is a clue about why posts from prior to the arrival of the first wave of passengers are only sporadically available. Was the network previously rebooted in response to an infection with the same virus, or something even worse? That doesn’t explain how they would have ended up on a subnetwork, but it might explain much of the rest of it.]
As some of you may have noticed, nothing posted prior to the network’s return has been accessible since then. One of the functions of the Communications department is to archive network activity, and fortunately, we were able to back up the vast majority of the network as it existed before the emergency shut-down.
I’ll be posting what I can of that archive in a minute. However, please be aware that we don’t have the technical capacity to make this available to you in the format you’re used to, and that any posts from the old system that had been subject to an encryption created by one of us are completely incompatible with the new one.
[A beat of silence.]
Related to that: while we’ve been trying, no one in the department has yet been able to create new encryptions that work on this network, and the built-in privacy function seems to be much stronger and more reliable than it was before. We can’t say that the privacy function will be reliable forever -- very likely, it will be broken in the future, which will compromise the security of anything you’ve done using it -- but it appears that it’s currently dependable. This also does not rule out the possibility that someone we’re not aware of has the ability to break it already.
If you’re able to create an encryption that the network will accept, or if you simply have skills in this area that you’d be willing to put to work, please let us know, and please consider joining the department. [He is now turning on the charm, such as it is, and sounds slightly wittier and less serious than he had earlier in his announcement.] We’re not short-staffed at the moment, but we wouldn’t want to let your talents go to waste.
Those of you who don’t have talents in this area should consider joining another department. Agriculture could certainly use your help, even if it’s only for a few hours a week.
[The lightness in his tone now vanishes.]
On an associated note, if you receive any anonymous messages in your inbox, particularly from someone calling themselves Lina, or attempting to strike up a conversation and fish for information, please let us know. The same goes for any situation in which your communication device otherwise behaves in an unexpected way, and if you can visit the Comms Hub with your communicator while any of these things are still ongoing, so much the better. We’re located near the Bridge.
We’re aware that it’s common to come from a place where this kind of network communication is unusual. If you need help learning how your device works, let us know. We also have several programs which can be added to it, and some people may be able to make music or game files available to you. Those were programmed for your communicators, not the network itself, so it appears that they’re still compatible.
Finally… [a hint of regret enters his voice]... as of the jump several days ago, Clara Oswald has left the ship.
If you have any further problems involving the network, please contact me or Bail Organa.
Thank you. Comms out.
--
[Filtered to Tyke | Private]
If we learn that someone onboard has falsified an anonymous conversation similar to the one I just mentioned on the network, particularly if they do so in the future, can Security consider a suitable punishment? I had to discuss the messages here, but doing it so publicly is likely to encourage pranksters. I'd really prefer that they didn't waste my time.
Likewise, we’re still looking into the matter of the virus. If it turns out that someone is responsible for it, I’d like them to be subject to brig time.
--
[OOC: Please note that even the most talented hackers won’t be able to get into posts marked private for at least three months, and new characters will probably need about that much time to get up to speed with this system after they come in! It will not be a smooth road, either: the new system has many built-in blocks and tricks, and some hacking attempts will even flag SEC.
The link within the post is to an open Comms log. Please have your character drop in if they're interested in being tutored in the ins and outs of smartphones, or if they want to ask a question, or if they want to bug someone who's trying to work.
The batch archive of posts from the old network is here! It covers everything prior to November 1, 2014, or a week before the 37th jump by TQ Reckoning. Notes related to technical aspects are on that post.]
171 comments | Leave a comment