|
A C
|
#
?
Sep 14, 2016 01:22
|
|
|
|
| # ? Apr 25, 2024 07:31 |
|
|
AC
|
|
#
?
Sep 14, 2016 20:02
|
|
|
AF
|
|
#
?
Sep 15, 2016 03:10
|
|
|
 Scuzzy's tail flicks and its haunches wriggle, and it launches its attack protocol. The hapless data-porter, mostly data storage modules with a motility function, has no idea what hit it. The virtual baykit's fangs sink into the porter's structure, pumping jets of virulent decompilers into its vulnerable code. The program writhes briefly in an analog of agony, as Scuzzy hollows out a cavity within it with its virtual enzymes, then, with a hiss of triumph, allows its bitstream to flow into the unallocated space. The porter goes still for a long moment, then reboots, under new management. Encased in the remains of the data-porter, and Masked as simple blocks of encrypted cargo-data, Scuzzy Jr. rejoins the stream of commuting programs filing toward the access portal.  Your talons tick nervously on the inside of the conduit as your drone's abstractum passes under the watchful crimson stare of the hygiene enforcer. You can almost feel the baleful light of its merciless regard on your own skin as its scanners penetrate the body of the erstwhile data-porter; a thousand tiny daggers of light drilling their way into you, seeking your heart. The sentinel drags the required responses from the data-porter's code with no care for the sensibilities of an unthinking program, but you yourself feel a certain violation at the search and seizure. The sentinel's weapons swivel and track on their nacelles, ready to decompile Scuzzy in an instant...  But the light recedes, and Scuzzy coolly drifts into the gateway. Your drone's bitstream joins millions of others streaming down into the digital heart of the station in a coursing river of displaced electrons. It would be easy to lose yourself in the sensation, particularly with the recent increase in your synthetic awareness. But your professional discipline, as well as your well-earned suspicion of growing entirely too comfortable with virtual matters, help you keep one foot grounded in reality.  Scuzzy returns to resolution in a storage partition deep within the station's core. Refusing to be distracted by towering data constructs, you perform a Search; a passive filter spread like a skein, nothing so deep as to announce your presence. Almost immediately, your filter locates two nodes of expected interest...and one you hadn't anticipated. One node contains map and navigational data of the deep reaches of Gigas. The cartographical protocols are Gigantes to the core, however, alien almost to the point of uselessness. It had never occurred to you to wonder how the maps of a collective of deep-sea tubeworms would differ from those of other species, but presented with the evidence, you can't really say you're surprised. You're fairly certain you and your contacts could make something useful out of these splotches and wriggles with time, but you won't necessarily know what's useful at a glance. A. Perform a full dump of the node into your storage. This is somewhat time-consuming and risky. B. Further refine your Search and grab only those data which display potential. This is time-consuming and somewhat risky. C. Snatch a quick "handful" of data and move on. This is not particularly time-consuming and not particularly risky. D. Pass this node by. Your time and attention are better spent elsewhere. The other contains a database of data on the Erb, their culture, technology, and servitor species. You are surprised by the sheer weight of the data; you hadn't anticipated the Gigantes would be either so interested nor so well informed. They almost certainly know the starship is there, may have studied it themselves, and their intelligence could prove instrumental in surviving and exploiting the wreck. E. Perform a full dump of the node into your storage. This is somewhat time-consuming and risky. F. Further refine your Search and grab only those data which are directly pertinent to the operation. This is time-consuming and somewhat risky. G.Snatch a quick "handful" of data and move on. This is not particularly time-consuming and not particularly risky. H. Pass this node by.  The unexpected bonus comes in the form of a bank of stored surveillance data. Mostly drawn from thermometers and humidity sensors and the like, the majority of the data are largely useless to you. There are, however, an appreciable number of video feeds available for sample. You can't allow yourself to be drawn into an exhaustive reference of the millions of feeds, but you could certainly extract something of value... Select all that apply: Each option is somewhat time-consuming and somewhat risky. I. Filter feeds containing your name or image. J. Filter feeds relating to your crew. K. Filter feeds relating to the O-Barvanja Syndicate. L. Filter feeds relating to the Helix Rippers. M. Specify a filter criterion:__________________
|
|
#
?
Sep 15, 2016 19:14
|
|
|
C. A takes too much time and we don't know enough for B. And the information might not be very usable regardless. E. Things that don't seem relevant now could become relevant during the mission. L. Make sure the pirates aren't planning to betray us.
|
|
#
?
Sep 15, 2016 20:07
|
|
|
HBar posted:C. A takes too much time and we don't know enough for B. And the information might not be very usable regardless. Sure, why not.
|
|
#
?
Sep 15, 2016 20:34
|
|
|
HBar posted:C. A takes too much time and we don't know enough for B. And the information might not be very usable regardless.
|
|
#
?
Sep 15, 2016 22:44
|
|
|
HBar posted:C. A takes too much time and we don't know enough for B. And the information might not be very usable regardless. Makes sense. It's risky as hell doing thus in the first, and this is a nice balance.
|
|
#
?
Sep 15, 2016 22:56
|
|
|
HBar posted:C. A takes too much time and we don't know enough for B. And the information might not be very usable regardless. Yep
|
|
#
?
Sep 16, 2016 03:57
|
|
|
Welp, that's a thus-far unanimous victory for CEL then
|
|
#
?
Sep 16, 2016 05:34
|
|
|
Could we build a passive data tap for all the non-mission critical data. We are basically inside the server. We could spend a moment to build a crawler and a covert outside tap to slowly snatch bits of data and dump them down a rabbit hole through some dummy servers and eventually into our hands where we can slowly recompile the data. Should be low visibility for such a high traffic port. If not then the full smash and grab
|
|
#
?
Sep 16, 2016 05:44
|
|
|
Arkanomen posted:Could we build a passive data tap for all the non-mission critical data. We are basically inside the server. We could spend a moment to build a crawler and a covert outside tap to slowly snatch bits of data and dump them down a rabbit hole through some dummy servers and eventually into our hands where we can slowly recompile the data. Should be low visibility for such a high traffic port. That's a very good suggestion actually.
|
|
#
?
Sep 16, 2016 06:30
|
|
|
Arkanomen posted:Could we build a passive data tap for all the non-mission critical data. We are basically inside the server. We could spend a moment to build a crawler and a covert outside tap to slowly snatch bits of data and dump them down a rabbit hole through some dummy servers and eventually into our hands where we can slowly recompile the data. Should be low visibility for such a high traffic port. That is a possibility.  Option Arkanomen may be selected for any of the above node choices. It is time-consuming and not particularly risky.
|
|
#
?
Sep 16, 2016 12:58
|
|
|
Amending my vote to Plan Arkanomen then.
|
|
#
?
Sep 16, 2016 13:57
|
|
|
Hexenritter posted:Amending my vote to Plan Arkanomen then. For which nodes? All?
|
|
#
?
Sep 16, 2016 14:22
|
|
|
Xiphopagus posted:For which nodes? All? Definitely on the surveillance data because of the potential blackmail opportunities, and on the Erb... you know what, sod it. Data siphons on all three nodes, what could possibly go wrong 
|
|
#
?
Sep 16, 2016 14:53
|
|
|
CE-. The Erb data's what we're after, but grabbing all that is enough risk and time by itself. Skip the other two nodes.
|
|
#
?
Sep 16, 2016 15:02
|
|
|
E and Plan Ark on the other 2 nodes
|
|
#
?
Sep 16, 2016 23:31
|
|
|
Xiphopagus posted:For which nodes? All? Yes.   
|
|
#
?
Sep 17, 2016 05:17
|
|
|
Could we call in our Hacker Frenemy for a favor. He either wrecks up the place or snatches the data for us in exchange for canceling the debt as well as doing whatever the gently caress he wants here?
|
|
#
?
Sep 17, 2016 09:00
|
|
|
Arkanomen posted:Could we call in our Hacker Frenemy for a favor. He either wrecks up the place or snatches the data for us in exchange for canceling the debt as well as doing whatever the gently caress he wants here? You gave up the infomancer to Ramadi as goodwill gesture. She ransomed him to his guild.
|
|
#
?
Sep 17, 2016 20:35
|
|
|
 The Gigantes cartographic data is so many worm castings and chemical stains; you wouldn't have any idea how to compose a search filter that would land you anything useful. Scuzzy Jr.'s tail twitches impatiently, and you shrug mentally and order your drone to just trawl randomly. Hopefully something in the disorderly pile of data thus gained will pay off for you, if not now, then farther down the lane. The bank of Erb data, on the other hand, is potentially priceless.  You find yourself with the opposite problem that you did with the maps; drowning in choice, you elect to simply dump the entire database into storage. While the staggering weight of data transfers, you begin to pull the useable surveillance feeds relating to the Helix Rippers: Their personnel, on-station business interests, and docking bay, among others. You glance idly at one of the stored feeds...  "I don't see why I'm stuck on sentry duty again," the hybrid with the heavy laser grouses, shifting the cheroot to the other side of her mouth. The loadmaster's mouthparts rattle in a sigh; this is obviously not the first time for this conversation. "You're on sentry duty," he chitters, punching a command into his wristlink that summons a troop of longshoremechs tromping down the cargo ramp, "because the last time you got shore leave, you ate somebody." "I told you, it was--" "For the last time, Mez, it was not consensual. Just because you say it was don't make it so." "Stitch eats people all the time," Mez protests, slapping the power pack on her laser, "and she don't get stuck watching the sub." "Stitch harvests resources for the crew," the loadmaster retorts. "You just do it for fun." "You tryin' t' tell me Stitch don't enjoy it? I call sleeb-slot on that, Bakto." "Her enjoyment of the matter don't factor into it," Bakto says, mechs now ignored as he begins to get more heated. "Fact is, she always brings in new biomass, whereas you," he points with a bristly claw, "you just roll in just before all-call with chunks of some qwag smeared all over face and frontals.” "That was only the one time," Mez whines, fire gone out of her voice. "I was drunk and hungry..." "You're always drunk and hungry," the loadmaster groans. "And if not one, then double-strength the other." "I told you about my glands! I can't help if--" "Why is my slotting bay empty," booms a voice from inside the cargo bay. Bakto hurriedly scrabbles at his wristlink, and the mechs whir to action, hefting a load of crates with effortless precision. Mez immediately straightens her back, head darting hither and yon as her laser tracks the shadowy corners of the dock.  The clip is merely one of thousands of varying degrees of worth, and you quickly begin downloading the entire bank for later perusal.  You're not certain if you touched a security-flagged file in your sweep, or if you simply spent too long in a secure filesystem, but the husk of the data-porter falls away like pixellated dust as the world around your drone's abstractum suddenly takes on a crimson menace. Databanks recede into the storage partition's infrastructure, and firewalls begin to descend over access portals. The normal background noise of the station's virtual environment, long since faded away in your mind, suddenly becomes conspicuous in its absence, before being replaced by the strident wail of an alert protocol. Scuzzy flees toward the nearest egress point with all haste. You could swear that it seems slower, weighed down by the bulk data collected, but you know that's purely psychological. What is all too real, however, is the cluster of Intrusion Countermeasure nodes that extrude themselves directly in your path.  At a glance, you'd identify them as Isolators, their weapons primed to Banish Scuzzy into a quarantined node. If you don't want some Gigantes system engineer peeling away at your drone's systems like a ripe mhenga, you'll need to take immediate action. A. Dump your connection and cut your losses. Your and Scuzzy's systems can handle the shock with (comparatively) minimal disruption, but you will lose all the data you've collected. B. The ICE are trying to capture, not decompile, but you have no such compunctions. Get in there and Shred for all you're worth. This is risky, and will certainly raise the alert level. C. Many of your more devious utilities are disabled by the alert, but you could still try to Infest one of the IC nodes and use it for over while you fight back. This is extremely risky, and will probably raise the alert level. D. Initiate Autotomy protocol. Have Scuzzy leave a digital husk for the Isolators to focus on while a vital kernel escapes to freedom. There is likely to be some level of data loss. This is risky, but will probably not raise the alert level.
|
|
#
?
Sep 20, 2016 15:31
|
|
|
E. Split scuzzy into two halves. The kernel and the data leave a husk with a self replication routine. The Husk takes a random chunk of data and copies that into two new husks. Those husks then grab two bytes of nearby data and replicate that. This should grow fast enough to overwhelm the capture protocol drones. The kernel secures its data and bails in the ensuing chaos. Once we are out, the husks all self terminate and litter the server with terabytes of scrap code and replicated data. MALCODE MOTHERFUCKER!
|
|
#
?
Sep 20, 2016 19:17
|
|
|
Arkanomen posted:E. Split scuzzy into two halves. The kernel and the data leave a husk with a self replication routine. The Husk takes a random chunk of data and copies that into two new husks. Those husks then grab two bytes of nearby data and replicate that. This should grow fast enough to overwhelm the capture protocol drones. The kernel secures its data and bails in the ensuing chaos. Once we are out, the husks all self terminate and litter the server with terabytes of scrap code and replicated data. This seems like it could turn into a 'Sink the ship to kill the captain' scenario. But sure, make sure the kill code activates after 10 minutes or 'X' number of replications'
|
|
#
?
Sep 20, 2016 20:28
|
|
|
Arkanomen posted:E. Split scuzzy into two halves. The kernel and the data leave a husk with a self replication routine. The Husk takes a random chunk of data and copies that into two new husks. Those husks then grab two bytes of nearby data and replicate that. This should grow fast enough to overwhelm the capture protocol drones. The kernel secures its data and bails in the ensuing chaos. Once we are out, the husks all self terminate and litter the server with terabytes of scrap code and replicated data. Time to cheese it. Leave some loving caltrops as we run away.
|
|
#
?
Sep 20, 2016 21:29
|
|
|
Do you think this is a good time to use one of the coins to escape intact ANd with all the data?
|
|
#
?
Sep 22, 2016 18:13
|
|
|
ForgedIron posted:Do you think this is a good time to use one of the coins to escape intact ANd with all the data? Oh poo poo, forgot about those. USE A COIN AND BE AWESOME.
|
|
#
?
Sep 22, 2016 23:15
|
|
|
A motion has been made and seconded to spend one of your two Platinum Hyperducats to Hack The Gibson! Support is at 50%, and will pass if no negative votes are made. The outcome will be based on Plan Ark++, unless some other course somehow comes out ahead.
|
|
#
?
Sep 22, 2016 23:47
|
|
|
Ark/Outrail + Hyperducat
|
|
#
?
Sep 22, 2016 23:51
|
|
|
HACK THR PLANET
|
|
#
?
Sep 23, 2016 00:15
|
|
|
HBar posted:Ark/Outrail + Hyperducat Yeah this. Spend like a boss.
|
|
#
?
Sep 23, 2016 00:16
|
|
|
Spend one
|
|
#
?
Sep 23, 2016 02:58
|
|
|
Time for a legendary hack. This could be an event that we can learn from and in time become truly dangerous. Voting for piece by piece encapsulating ourselves in nano- bot- housing light powered armor with additional computing power. Doesn't have to be implants, just include a datajack in the cowl/helm. I look forward to hacking the crap out of someone, beating them to death or decapitation by nanoblades on our hind claws. Then we harvest their corpse for raw material to replenish our stores. Also if you've read the Omega Force series, you can imagine what I have in mind. Also we can Cosplay as a T-1000.
|
|
#
?
Sep 23, 2016 03:09
|
|
|
Blasphemaster posted:Time for a legendary hack. This could be an event that we can learn from and in time become truly dangerous. 
|
|
#
?
Sep 23, 2016 03:19
|
|
|
HBar posted:Ark/Outrail + Hyperducat Spend money make money
|
|
#
?
Sep 23, 2016 04:32
|
|
|
HBar posted:Ark/Outrail + Hyperducat Worth it, or completely worth it?
|
|
#
?
Sep 23, 2016 07:23
|
|
|
I'm excited. Here is my official vote, Plan Ark + Hyperducat
|
|
#
?
Sep 23, 2016 15:33
|
|
|
Hack all the things
|
|
#
?
Sep 23, 2016 16:38
|
|
|
The Isolators inexorably hedge in Scuzzy Jr.'s abstractum, capture rings whirring and data profilers glowing brightly, and you consider simply dropping your tail and bugging out. Scuzzy's military-grade autotomy protocol is purpose-built for espionage and exceptionally elegant; not the kludge that many such programs represent. You'd probably be able to come out with most of your data (and digital hide) intact. But then, you have a better idea. Rolling around in bottom of your bag of tricks (crumpled and covered in virtual lint) is a program you often used as a juve, but have had little reason to deploy of late. It's a basic Waster, a program just complex enough to replicate itself for a user-determined number of generations before collapsing into so much garbage data. It's the sort of program a low-rent cyber-vandal would drop in the target of her adolescent aggressions; a prank, an annoyance, and not the sort of thing an elite professional hacker would be caught firing off. Which is why it's perfect. You make a few...adjustments.  As the Isolators close on their quarry, unaware that the captured data and Scuzzy's higher functions are already burrowing to safety under the cover of the decoy, they are, basic constructs that they are, unprepared for what ensues. In one tick, Scuzzy's image bulges alarmingly, before birthing an exact duplicate with a blat of digital flatulence. The next tick, the process repeats itself, twice over. As the rogue abstracta redouble again and again, the Isolators quickly find themselves overwhelmed. Kits spew in every direction, with the uncontrollable liquid grace native to the species the abstracta represent. Many Scuzzoids are captured, to no avail, as the baykit horde washes over the partition in a wave of adorable malware. The functions of the storage partition slow to a crawl as every free sector begins to fill with the mounding waste of a thousand thousand exploding kits. Administrators deploy hygiene enforcers to sanitize the area, but all they can do is clean up your mess, for you are already gone. Gone where? Not through one of the dedicated egress points; they are firewalled beyond your ability to penetrate in such a short timeframe. But as Scuzzy-Core tunnels, undetected, though the partition's directory structure, something catches your virtual eye: Someone else's virtual eye. A network analyst, to be precise, and with no hesitation and a daring with which you wouldn't have credited yourself, you pounce...  Flushed with triumph and a growing feeling of invincibility, you barely feel it when your rushing bitstream smashes into the defensive protocols at the end of the pipe and flows into the comparatively spacious, but somehow claustrophobic, confines of the analyst's cyberbrain. The analyst jerks, slamming against the back of her seat, her life support cradle and the thick network umbilicus tethering her to her console resisting her struggles. For a moment, she writhes in existential conflict, scrabbling for purchase on the treacherous mental processes you have made to serve you. You feel a primal scream of futile rage against your intrusion, then all goes eerily calm.  You hear with borrowed ears the tocking of heels on deck plating, as {Your Supervisor} stalks across the cell toward you. You snag a view from the cell's security feed, seeing the cadaverous overseer looming over your shoulder and wincing involuntarily as you see the deprived condition of your borrowed body. "Analyst B-304, Report," {Your Supervisor} demands, his raspy whisper transcribed in dominating boldface on your heads-up display. Analyst B-304, Report. You begin to croak a response through neglected vocal cords, before realizing it would be suspiciously out of character, and respond in text. >16302-nacre (salinity 4) has suffered a disruption of service, you reply, keenly aware of the ribbon of saliva now sliding from the corner of your mouth but unable to address the issue. >Threat non-active; Data Hygiene Enforcers dispatched to restore full function. {Your Supervisor's} brow furrows over his oculars, and you faintly hear his knuckles cracking as he flexes his spidery fingers. A pale tongue dabs across thin, dry lips, and he thrusts a digit at the monitors before you. "An unacceptable lapse, B-304," he wheezes. An unacceptable lapse, B-304. "The culprit?" The culprit? You hesitate only a moment before assembling packets of false telemetry implicating the "culprit" of the intrusion, and reporting this to {Your Supervisor}. 1. Who ____________________________. The overseer's already pale face blanches in cold anger, and your virtual senses "hear" him dispatching a squad of quick-response drones and security personnel. "Perhaps something can be salvaged from this debacle," he mutters darkly, turning on a sharp heel and stalking away, strident footsteps gradually swallowed by the gloom. You can't stay here. Every moment runs the risk of either Scuzzy's chassis or your own person being discovered, and you feel a deep ambivalence about what you're currently doing to this analyst. But before you go, you take advantage of your current access to snag a target of opportunity. 2. What was it? A. The discretionary account of a mid-level station factotum, swollen with graft. B. The plans for an experimental cyber-frame, themselves stolen from one of the Cartels. C. Transponder codes from a Gigantes transport sub, good for another deka-cycle and authorized for your target location. D. An authorization token for the environmental controls of the docking bay used by the Helix Rippers. 3. You also need to do something about the analyst to avoid reprisal. E. Wipe her cortex. This is as close to murder as makes no meaningful difference. F. Edit her memory of the intrusion to remove your presence entirely. There is a slight chance that the edit will not be 100% effective, or that cortex damage could still result. G. Leave account information and pay her some hush money. H As G, but pay more (like the contents of A, for example), and leave an apologetic message. I. Leave her cortex entirely untouched, and leave her your comm frequency. J. Something else: _______________________. The entire episode is swift and efficient; the drones patrolling the atmo-con tower will only later discover your physical intrusion. Scuzzy Jr. glides away into the fog without opposition, and your teeth peek from your lips in a triumphant grin. 
|
|
#
?
Sep 26, 2016 17:28
|
|
|
|
| # ? Apr 25, 2024 07:31 |
|
|
It was totally done on the orders of Queen Croc Bitch. B. Because loving nano-armor with supplementary processors and data storage you guys. I. Lady is just doing her corpse-slave work. Leave her a code to a burn-comm. When called, it bounces signals audibly rather than digitally between several pickup units and can't be easily traced. We see what comes of it. M. Because I want to do something like diplomacy. We need to sharpen our people skills.
|
|
#
?
Sep 26, 2016 17:53
|
|