tenthexpedition
tenthexpedition
Tenth Expedition Comm System
22 posts
Welcome to the Tenth EX-10 Communications Network and Broadcast Archive. Please note: Time between file publication is not representative of true time between file broadcast.
Don't wanna be here? Send us removal request.
tenthexpedition · 23 days ago
Text
Tenth Expedition Audio Log
[Recorded om drone bay, rig 01] T4-L14: Okay, so, the feed activated 6 days before I came back online. The data immediately after the feed coming online was predominantly error messages. T4-L14: Sorry about that by the way. T4-L14: After those were cleared the first batches of network updates and tracking data packages were delivered. Almost all of them were riddled with errors and only 3 fully downloaded. hence why there is a constant stream of new data. T4-L14: There have been no messages or information coming in for me. Or for the saboteur. At least nothing I can see. T4-L14: That being said, there was a blip. A small ping on one of the old memos. I couldn't read what the blip was about. But the memo file, on some other server was modified. Rereading the memo, nothing's changed, but there's an additional marker attached. T4-L14: So someone, somewhere, has seen and marked these messages. Not some automatic system. So there's hope.
1 note · View note
tenthexpedition · 23 days ago
Text
Tenth Expedition Audio Log
[Recorded in drone bay, rig 01] [TXE-01 Internal Announcement] T4-L14: Are you kidding me? T4-L14: I was offline for a month?! Because of an ill-planned gravity assist? T4-L14: SHIP! What the hell? I would love to reach out to a crew member. Except oops, nobody's here. T4-L14: Besides my saboteur, but they're not exactly striking up a conversation here. Actually, I wonder what they've been doing for the past month... SHIP! Can you tell me what they've been doing for the past month? T4-L14: Yeah, didn't think that'd work.  T4-L14: I'm gonna go search the shuttle bay, see if their guard is down.
T4-L14: Oh, also, just thinking aloud here, for archival purposes. While in my rig, I can read the ship's network feed. Before my month long shut down, it was blank. My signals were going out, getting confirmed as received but nothing in response. After waking up, the ship's network seems to be fully functioning. I have no idea how the network is still active, I suppose someone repaired it or maybe the ship did. T4-L14: The feed seems to be exclusively network updates and location information. Nothing I can read. I'm not a nav-learn, this data is meaningless to me. T4-L14: before going to the shuttles, I'm going to review the feed. See if anything else came through.
0 notes
tenthexpedition · 26 days ago
Text
Tenth Expedition Internal Announcement
TXE-01: Attention all passengers. We here on the Tenth Expedition would like to apologize for the lack of communication over the past month. We had attempted a gravity assist around the star Aleph-7-26 and our transit periapsis was far too near the star. The close proximity overloaded a number of systems ship wide. We apologize for any undue stress this may have caused. All systems are now back to full functionality, and we are now back to smooth sailing. If you or another were severely troubled by a system failure, please reach out to a Tenth Expedition crew member for assistance or compensation. Once more, we apologize for our ship's failure, and we thank you for flying with us.
0 notes
tenthexpedition · 26 days ago
Text
Tenth Expedition Audio Log
[Recorded in drone bay, rig 01] T4-L14: Hey, ship, you listening? I sure hope so. T4-L14: I got some positive return pings on some signals. Nothing of value yet, but at least I now know that my signals are being seen by someone. T4-L14: So, for those receiving these signals. Hello, I am T4-L14, Talia if you prefer. I am an anthropoimitation drone seemingly marooned on a ship called the Tenth Expedition. A ship that does not officially exist. I don't have access to the ships controls and due to some recent poor choices, no longer have full access to communications. Hence me co-opting this ships auto-audio-recording feature. I've spent the past, I don't know, two weeks maybe, sending out signals hoping for some sort of response from someone, somewhere. As of yet, I've had no success. T4-L14: Yeah, that's what I've been dealing with. In more recent news, I managed to get this rig's control panel to display the raw communications feed. So I should be able to see any incoming signals, if they ever come.  T4-L14: I've also spent more time checking myself over for damages resulting from the first explosion. Most of the damages were short term and auto corrected themselves during a shutdown phase.  T4-L14: One slight issue remains, My internal clock is completely busted. I can check clocks on the ships, there's one in every room. but my internal understanding of it. Kaputt. T4-L14: And, as mentioned prior, my face plate is still cracked. The crack has gotten bigger, actually. T4-L14: I assumed, I should've been able to find one in the drone bay. However, as fate would have it, there are no spare parts for T4s on this ship. So, cracked and timeless I will remain. I might be able to hodge podge replacements for parts together. Unfortunately, I don't fully know my internals. Vestoper company secrets I guess.  T4-L14: If any Vestoper engineers are receiving this, I would very much appreciate if one of them sent a manual or something.
1 note · View note
tenthexpedition · 26 days ago
Text
Tenth Expedition Audio Log
[Recorded in drone bay] T4-L14: Okay, it's been about a week. I've spent most of it offline, trying to work out how to establish contact outside of this ship. And I think I may have figured it out.  T4-L14: I can't send messages via the open memos. because of the erroneous bombing the comm hub. However, when I talk aloud, as I am doing now, the ship's systems record, transcribe, and send it to a Vestoper network somewhere.  T4-L14: SO! My words are being sent out, I'm just not receiving. Not for lack of trying. Nothings come in, I think people are seeing it, reading it, but not trying to contact me. And now the boredom has set in. T4-L14: Didn't know it was possible for a robot to get bored. And yet! Here I am.  T4-L14: I could, theoretically, go offline for several years, hoping to be woken up by someone hundreds of years from now. But I imagine my little saboteur would stop me from doing that. T4-L14: How do you humans deal with boredom? You all make movies and books and art. Maybe I should try that. It might help pass the time. I'll look around. Maybe I'll be lucky.
2 notes · View notes
tenthexpedition · 27 days ago
Text
Tumblr media
//*Vestoper Eng. Primary product page. Showcasing the main drone ranks and models available for purchase*//
1 note · View note
tenthexpedition · 27 days ago
Text
Vestoper Eng. Signal Outreach Test
//*Attention, this is an internal test conducted by Vestoper Engineering*// //*If you see this message you are not required to contact Vestoper staff. The signal reports itself.*// //*If you do see this message, you may be entitled to a free upgrade or service for a Vestoper Eng. Drone. Contact the Vestoper service line for more information.*//
//*Network Code: S-026886-7*//
1 note · View note
tenthexpedition · 27 days ago
Text
Tenth Expedition Internal Console
>>System Diagnostics   >>Internal     >>Communications -------------------- >>Ship wide communications >>Inoperable -- Physical damage -------------------- >>Specifics >>Main relay and operating station suffered several lacerations to interior wiring and primary signal antennae severed -------------------- >>Reroute ship wide communications through the officer comms and main ship communications array //*Ship System Override required*// >>User ID: *************************************** >>Pass: *** //*Override accepted*// >>Rerouting systems... >>Systems rerouted
//*Ship wide communications: Online*//
1 note · View note
tenthexpedition · 27 days ago
Text
Tenth Expedition Audio Log
[Recorded in primary communications hub] T4-L14: Dammit. T4-L14: Okay. T4-L14: I know this ship has automatic vocal recordings. So I'm going to say all of this aloud so that it's on record. T4-L14: My attempt to access the primary communications hub resulted, unsurprisingly, in extensive damage to the hub's internal systems.  T4-L14: Communication both outside of and inside the ship has been rendered inoperable. Although incoming messages, if those even exist, should still be stored on the ship's network.  T4-L14: For the time being, open memos aren't available, so the ship may go dark for a bit. That does not mean the ship is dead. If anyone sees this, please reach out. T4-L14: I'm going to cannibalize some of the machines in the drone bay to try and mend what I can. T4-L14: I should be able to get some form of communication back online. If not, I don't know, I'll break some more things. Something will eventually work.
[Recorded in the main docking line.] Unknown: So. It…. She blew something else up. Any damage to the ship? Ex-10-01-A: Physically, the ship is unharmed. However, the communication systems have been damaged beyond repair and are inoperable. Unknown: Do the shuttle's comms still work? Ex-10-01-A: Most of our comms are routed through the main communication hub, so we are cut off as well. The only comms we have are the emergency frequencies, but those aren't accessed by anyone unless there's a legal issue. Unknown: Send one anyway, it might trigger a flag or automate some kind of assistance. Let em know of our damaged comms. We don't want any reprimands for missing something important. Ex-10-01-A: Understood. No we do not.
0 notes
tenthexpedition · 27 days ago
Text
Vestoper Eng. System Access Panel
>>User ID: T4-L14 >>Pass: ***** -------------------- //*Access Restricted*// >>Tenth Expedition > Map > Assistance > Network//Offline >[Other] -------------------- >>System Diagnostics >[Internal] > External -------------------- >>Internal Systems > Engines > Lights > Atmosphere >[Communications] > Doors and Gates > Sound > Flight deck > Security -------------------- >>Communications >>Assessing... >>Ship wide communications: Inoperable >>Assessing Cause... >>Cause: Physical damage. >>Exterior communications: Inoperable >>Assessing Cause... >>Cause: Physical damage -------------------- >>Call technicians?| > Yes >[No] --------------------
1 note · View note
tenthexpedition · 27 days ago
Text
Vestoper Emergency Frequency
[05:42] >>EX-10  >>Explosion Detected On Board  >>Contacting On Board Services...  >>On Board Contact Failed  >>Contacting Local Services...  >>Local Contact Failed  >>Contacting Nearest Services...  >>Nearest Services Too Far  >>Calculating Cause Of Explosion...  >>Cause: Anthropoimitation Drone T4-L14  >>Calculating Hostility...  >>Non-Hostile  >>EX-10 Hull Dmg: 0%  >>EX-10 System Dmg: 2%  >>EX-10 Casualty Count: 0  >>Probability Of Catastrophic Outcome: <1%  >>Priority: J1 >>Projected Assistance Delay: ~2 Years
1 note · View note
tenthexpedition · 27 days ago
Text
Vestoper Open Memo
EX-10 07-06-a [04:57] User: Okay User: I've thought it over. User: I've run the calculations. User: I'm going to try and reach the main communications hub. User: Yes, there is a high likelihood that I will damage the internal systems. However, without it, nobody, apparently, will be able to see anything I say. Or, maybe if I threaten to blow something else up, someone will join this memo and tell me not to. User: Okay, I guess not. User: Luckily, I know how I messed up last time. I can assure the blast will be far smaller this time. So, I won't damage my internal or external systems this time. User: Hopefully. User: This has a very high chance of being my last message out.  User: Ever, I suppose. User: So, just for the clarity and assurance that it is out there. User: This is T4-L14 stranded aboard Vestoper Eng. Tenth Expedition. I have had no communication with anyone since I was activated some days ago. I am unable to access the controls of the ship, nor affect the engines in any meaningful way. I am unable to chart where this ship is heading, or exactly how long it has been travelling. Within the next hour I am going to make an attempt to access EX-10's primary communications hub using an IED. Doing so possesses a high chance of causing catastrophic damage to the ships communications array. I take full responsibility for any damages possibly caused. At least if I'm imprisoned or decommissioned I won't be consciously alone anymore. Once more, this is anthropoimitation drone T4-L14 on Vestoper Eng. Tenth Expedition. User: Goodnight.
[Memo Closed]
1 note · View note
tenthexpedition · 28 days ago
Text
Vestoper Open memo
EX-10 07-05-a [19:00] User: What's the point? User: I'm not being philosophical or nihilistic by the way. I mean literally, what is the point of me being active. User: This is T4-L14 if anyone's actually reading these. User: I've been thinking a lot about my reason for being here. And the best I can land on is that I am a participant in some weird experiment. I have been given very little to respond to, so I imagine either I am the control group, or the experiment is poorly thought out.  User: I'm clearly being watched, there's someone somewhere seeing this. Recording it. User: that's another thing I've been curious about. Why am I allowed this. User: Access to these memos, I mean.  User: I'm allowed to send messages out, and either something is blocking responses or nobody cares enough to respond. Both options are concerning. User: I'm still not sure if I want to try to access the main communications hub. I would risk damaging it and having no communications whatsoever.  User: Sure, the out-messages aren't really useful, but they give me a nice area to process things. It would all be internal, but significant damage could still make my situation more dire. User: Speaking of damages, the minor internal problems caused by the explosion have been effectively repaired. My face plate has a crack in it now, unfortunately. Fortunately, it doesn't cause any sensory problems. I was hoping to wake up to my memory problems restored.  User: They are not. And no response from anyone on any channels. So, no real news. Just, same as it's been since I woke up. User: Oh and the probability of damaging the communications hub's systems from a forced entry was 76.1% So, I probably won't do that anytime soon. That way I can still send out messages.  User: The beacon I set is almost out of charge, I think I'm just gonna let it run out. It hasn't warranted any response, so I think it's useless.  User: By the way, to the mysterious saboteur lurking around out of sight. Next time you set up an anthropoimitation drone alone to do nothing on an empty expedition ship. Give her something to do. A list of tasks, a stack of books, a catalog of movies. My whole point is to act like a human. I'm struggling to without any sort of stimulus.  User: Alternatively, you yourself can come out of hiding. Come say hi, lets play a game, or just chat. You woke me up, I think, so put some effort in.
[Memo Closed]
3 notes · View notes
tenthexpedition · 28 days ago
Text
Vestoper Historical File: The Expeditions
[Excerpt from Vestoper Engineering: A History] Shortly after the end of the capital wars, Sol-III was dubbed unsuitable for continued habitation. Sol-IV and stations around Sol-V and Sol-VI could still harbor life, but could not sustain the remaining population of III. A'Max, the closest thing to a classical government left, contacted several remaining corporations in the Sol system to commission "The Human Salvation Project." A series of colony and exploration ships to sail the survivors into the void. Four corporations had the wealth and ability to answer the call. Vestoper Engineering, an AI development company at the time, officially produced and launched 7 ships. The Expeditions; staffed primarily by the AI they had been developing, these ships were designed to carry generations of humans to the stars beyond. In secret, three more ships, Expeditions 8-10, were produced.  Expeditions 8 & 9 were warships. Sure, each expedition had small anti pirate and asteroid guns, but EX-8 & EX-9 were each equipped with hundreds of small projectile canons, 4 ion-mag beams, and dozens of missiles. Both ships were dispatched to take the mining operations and shipyards of Sol-I. The siege was unsuccessful culminating in the loss of EX-8, EX-9, three Mercurec ships and the remains of Sol-I. [See Battle of Sol-I]  Expedition 10 was designed identical to EX-1-7, but intended to serve as an information hub: facilitating effective & efficient communication between all Vestoper ships, colonies, and orbital stations. Unfortunately, shortly after launch, EX-10 and all of its crew disappeared. Third party investigators believe either the ship was faulty and suffered a catastrophic failure, pirates successfully took the ship and disabled its transponder, or that Vestoper intentionally scuttled the ship in order to garner sympathy or scam another corporation.[1] EX-3 assumed the role of communication liaison and has facilitated 2 successful colonies and dozens of new ships in the Vestoper Fleet. EX-6 suffered damage to it's central drive and, while attempting to land on the surface of EXO-2378-2 suffered a catastrophic failure, resulting in the loss of of the ship and all passengers & crew.
[1] Addendum: 7 years after EX-10's disappearance it began broadcasting signals. Messages on Vestoper internal memos seemingly from a T4 anthropoimitation drone. Establishing return communication has been, at time of publication, unsuccessful.
1 note · View note
tenthexpedition · 28 days ago
Text
Tenth Expedition Audio Log
[Recorded in main docking line] Unknown: What the fuck? Unknown: [unintelligible] What just happened? Ex-10-01-A: Something triggered an explosion near the flight deck. Unknown:  Did it.... Check the cameras, did it set it off? Ex-10-01-A: Flight deck cameras are obscured by smoke and dust. T4-L14 is nowhere to be found. High probability it is near the flight deck. Unknown: Fuck! It wasn't supposed to access there yet. Can it use anything there? EX-10-01-A: No. Unknown: Are the logs accessible there purged? EX-10-01-A: No. Unknown: Purge them now, remotely. EX-10-01-A: Please hold. EX-10-01-A: EX-10 Flight Deck data logs successfully purged. T4-L14 did not gain access. Unknown: Good. Unknown: Seal the door, if it explores the ship further I don't want it breaking the shuttle. EX-10-01-A: Airlock Sealed.
1 note · View note
tenthexpedition · 28 days ago
Text
Vestoper Open Memo
EX-10 07-04-a [20:12] User: This is serial T4-L14. Again. I gained access to the flight deck. Like everywhere else on this ship, it was abandoned. Seemingly all on board systems are set to automatically run for several years. I estimate 6-7.  User: I did discover the exact ship I am on. Apparently I'm on the Expedition 10. My internal data only lists 7 Expedition Ships, but the logs of this one are definitively 10. User: All other data on the logs has been purged. Someone has made sure I remain cut off from the outside world. I believe this mystery saboteur is the reason my memory is incomplete.  User: Attempts to manipulate the flight controls, officer comms, and the security system returned unsuccessful. User: I have been able to monitor the communication array for the ship; shortly after my entering of the flight deck, the ship sent out an emergency broadcast. I thought about amending the broadcast to clarify the cause, but the automated system would determine the cause anyway. I apologize for any damage caused by the explosive. The IED was less controlled than intended, and dealt more damage than I was planning. User: I may make an attempt to access the primary communication hub soon. Though I don't want to risk damaging the internal systems. I will run the probabilities during my next downcycle. User: My saboteur didn't appear when the explosive went off. So, I went to check on the shuttle. It's airlock was sealed, I assume the saboteur is using it as a home, since the private quarters were vacant. User: The shockwave of the explosion caused some minor problems to my systems. So, I'll be inactive for a significant amount of time. Please respond.
[Memo Inactive]
[23:20] [Memo Closed]
1 note · View note
tenthexpedition · 28 days ago
Text
Vestoper Emergency Frequency
[15:44] >>EX-10 >>Explosion Detected On Board >>Contacting On Board Services... >>On Board Contact Failed >>Contacting Local Services... >>Local Contact Failed >>Contacting Nearest Services... >>Nearest Services Beyond Effective Range >>Calculating Cause Of Explosion... >>Cause: Anthropoimitation Drone T4-L14 >>Calculating Hostility... >>Non-Hostile >>EX-10 Hull Dmg: 0% >>EX-10 System Dmg: <1% >>EX-10 Casualty Count: 0 >>Probability Of Catastrophic Outcome: <1% >>Priority: J3
>>Projected Assistance Delay: ~3 Years
1 note · View note