It'll Be Fun
Notes: This is the first post of the Nathan Bateman Choose Your Own Adventure for the Youvebeenlivingfictional 5k Follower Celebration! Just a heads up about a couple of things:
All CYOA paths are complete. If you hit the gif that says it's the end, it means that it's the end.
There is one (1) spicy chapter within one of the paths. If you cannot see the chapter, you need to update your content settings. Find the instructions to do that here.
This is not beta-read. As always.
The links to other paths are at the bottom of posts
If there are any broken links, please let me know!
Warnings: Cursing; angst; fluff
Summary: You’ve heard stories about how Bateman…Operates. You’ve only met him in person once, shortly after you’d been hired as Chief Knowledge Officer. It had been brief, perfunctory: Hi, how are you, happy to be here, love it, thanks for the money, enjoy your plane and helicopter ride back to your fucking remote, subterranean, in-fucking-sane facility you billionaire hermit whackadoo—
You had an idea of what this would be like, of course, but the reality is…Absolutely insane. You’re tired, you’re sweaty, and you are so, so happy that you fucking packed light. You shift your bag on your shoulder, glancing around. Follow the river. Follow the fucking river? You’re not a goddamn girl scout. You pull in a deep breath, then let out a relieved sigh as you finally spot the house…Up a rather steep incline. Son of a bitch.
You puff out an irritated breath as you bend forward a touch, resting your hands on your knees.
“Ohhhkay. Okay,” You mutter, straightening. Fuck, you hate team building. Hell, you hate it even more when it’s in such limited quantities of people—this way, there's nowhere to hide, you're easily missed. It’s barely half the C-suite: just you, Bateman, the CFO and the CMO.
It’ll be fun.
Bateman had slurred that across the phone on a status nearly two months ago. It’ll be fun.
The CFO and CMO had signed on enthusiastically; you’d been a little more hesitant to speak up, but had reluctantly agreed—and been met by an cheery, Yeaaah! from Bateman. Maybe that should’ve spurred you to be just a touch more excited, but you’ve heard stories about how Bateman…Operates. You’ve only met him in person once, shortly after you’d been hired as Chief Knowledge Officer. It had been brief, perfunctory: Hi, how are you, happy to be here, love it, thanks for the money, enjoy your plane and helicopter ride back to your fucking remote, subterranean, in-fucking-sane facility you billionaire hermit whackadoo—
Beyond that, you’ve hardly interacted with him outside of meetings, briefings, emails, what have you. You do a good job. You get your shit done. He doesn’t call you out because you've never given him a reason to.
You huff softly as you begin a long hike up the fairly steep incline. Alright. Pace yourself. No need to fuck your knees or ankles or anything up right before you meet your boss—
You wince as your foot slips, your knee skimming against a sharp rock. You groan, looking down and eyeing the throbbing spot. It hasn’t torn your leggings, but you’re willing to bet the skin’s a little torn under there. Damnit. You push on, righting your footing. Come on. Arrive in one piece. You don’t want the fricking sun to go down before you get there, and you really don’t want them to have to come looking for you.
(Though if you’re being honest, you’re not sure that Bateman would go out of his way to send out the search party. You can see the article on Wired now—BlueBook Chief Knowledge Officer Gets Eaten By Bear On the Way to Corporate Weekend Retreat. Said Bateman, “She knew she’d have a hike through challenging terrain. She should’ve brought her bear repellent. Frankly, we can’t tolerate that kind of narrow-minded unpreparedness at BlueBook. We’re already looking to hire her replacement. Our front-runner has climbed Everest.”)
You snort to yourself at the thought. You can practically hear Bateman saying it—with that damnable smug curl to his lips; you can see his hand drawing out of his pocket to adjust his glasses; to pass his hand over his closely shaved head, his palm loosing a rasping little shush against his cropped hair; his shoulder shrugging dismissively before he impatiently waves the reporter on to their next question. Oh, yeah, you wouldn’t put it past him. You’re only useful to Nathan as long as you suit his needs. You’re certain that if your visions for the company didn’t align with his, if you didn’t fall in line with what he wants for BlueBook, he’d drop you without a second thought.
It would only be right, of course. It’s his company, not yours.
You come to another stop once you reach the top of the hill, bracing your hands on your lower back and giving it a bit of a stretch. Fuck. You need a shower. A long, hot shower. You straighten up, and are set to go full steam ahead to Bateman’s when you hear your name called. You go still, dread trickling into your chest, your eyes squeezing shut. Maybe you can pretend you didn’t hear him?
But you’re not on some crowded city street, or office hall, and you’ve stilled for too long. You turn, slapping on a smile at the sight of the CFO, William Ellis, at the bottom of the steep hill. You force a smile, raising a hand to wave. You’re fully intent on turning back around and heading toward the house, but he calls out, “Mind giving me a hand with my bags?”
Yes, you do mind. You’re not a fucking bellhop. You don’t want to help him with his bags—you don’t even want to be here. You want to stomp back to that field and camp out until that helicopter comes back to take you home.
Instead, you turn around, measuring and bracing your steps as you trudge back down the hill.
--
“Damn good luck running into you.”
It's the third time he says it, though he’s run out of breath more and more as he did. Ellis is a short, stout Englishman. His typically fair, clear skin is ruddy and red from exertion. It probably doesn’t help that his voice seems to come from his nose, and is pushed out of the narrow purse of his lips with his rarefied Oxbridge snobbishness.
“Sure,” Is all you offer now. The first time, you’d said Isn’t it; the second, you’d chuckled lightly, offered, Guess so. Maybe if your responses become monosyllabic, he wouldn’t bother. You shift your bag on your shoulder, moving Ellis’ duffle bag from one hand to the other as you deftly avoided the rock that you’d slipped on before.
“Nice of Bateman to have us along,” He adds.
“Yep.”
“Don’t get to see much of the old sport these days.”
The Old Sport. Christ. This man is one off-white jacket, gin rickey, and Dead Man’s float away from being an F. Scott Fitzgerald character.
“Well, that’ll happen,” Is all you offered in turn. You fight the urge to drop William’s duffel on the doorstep as you approached the house. Instead, you still, watching William approach and draw his phone out to check the instructions.
“Now let’s see…” He mutters. “The instructions did say that the…Keycard pad was around here…Somewhere…”
“William Ellis.”
You glance over as a robotic voice draws your attention to a keypad. It's just another moment before it instructs:
“Please approach the console and face the screen.”
William wanders closer, eyes still set on his phone. You bite your lip, choking down a laugh as a light flashes, taking a picture of the top of William’s head.
“Take your keycard.”
You step closer as William took his, and the same robotic voice said your name. You step in front of the camera, forcing your face into a neutral expression.
“You ought to smile a bit,” William chuckles. You tighten your hands on the straps of his duffel as irritation pulses through you. You have half a mind to drop this duffel bag right on his foot—knowing full well that his work and personal laptops are in here. Instead, you reach out, taking the card from the slot.
“You may now enter the residence.”
William doesn’t hold the door open for you. He doesn’t even gesture for you to be the first one in. You’ve already had enough of this man’s shit—and you haven’t even seen Bateman, or the CMO. You don’t want to see them in this state anyway. The CMO, Dan Marshall, is one of your better workplace friends. And Bateman—well. Either way, you’re not sure you’re ready to see him yet, for all of the hell he’s already put you through with this little hike.
“So? Shall we?” William nods down the hall.
Shall you?
Go With William to Find Nathan and Dan
Go Off On Your Own and Find Your Room
171 notes
·
View notes
hi! about the "learn how it works before you start making assumptions" about the bluesky post and its networks; what assumptions should we be looking out for? that its not twitter and not everyone is going to be connected like on there? your description of federated networks is understandable, but the default domain it seems to have at signup is bluesky's. I feel like most people would be using this, and only people looking for a certain thing and knowingly leaving that "sphere" will know that theyre isolating to a different community.
I'm new to this too and theres very very minimal, well explained things about it online, and youre the only person I've come across who seems to know anything, so if you have more advice to share I'd appreciate it!
as much as I would like to answer this as an authority and really contribute to the nascent understanding of federated instances as an alternative to current social media platforms, the fact of the matter is that im not. i have a basic understanding of the way in which they work and how to use them, and I dont think im the best source of information. this being the case, since i did bring it up and i did get an ask, i'll try to explain the best i can.
the "fediverse" (dont mind the silly name, we know its silly) might best be explained with the similarities to email. Misskey, Mastodon, and others marketing themselves as federated instance platforms are basically like if you took your email account and stapled twitter to it: Misskey/Mastodon are not platforms themselves, so much as they are frameworks for web servers that connect to one another independently and are run by individuals. These frameworks are usually open source, have different alternative forks that offer different additional features/ui elements, and ultimately all connect to one another regardless. but they are not "platforms" like tumblr or twitter or facebook. anyone can make their own federated instance, and what that instance looks like depends on what framework they used to set it up.
Bluesky and Threads are different. Bluesky differs in that it is run on a private protocol-- it runs differently to the protocols used by the aforementioned open source alternatives and currently cannot connect with them. It's still in beta and its too early to call how it will operate. Threads, like Bluesky, is also a private protocol. At current, it merges your information with other Facebook/Meta products (facebook, instagram, etc). Supposedly, these will eventually be able to communicate with the Fediverse at large, but you should keep a great amount of suspicion with them, as both are run by billionaires. Bluesky is the project of the former head of twitter, and Threads obviously belongs to Zuckerburg and Facebook.
If you head about "x platform is homophobic/racist" in reference to the earlier federated instance frameworks, understand this very crucial thing about Mastodon/Misskey/etc:
They are not websites. They do not have established moderation policies and staff dedicated to managing who posts what.
as stated, Masto/Misskey are just server frameworks. Each federated instance using those frameworks is run by individuals on their own private web servers that they either operate themselves or rent out from a company. the largest Misskey instance, Misskey.io, is currently under fire for having homophobic moderation practices. This does not mean that every instance of Misskey is moderated with homophobia in mind, and homophobic moderation tools are not built into the code of Misskey.
As the old guard of web 2.0 crumbles, the internet is changing again. whether we fall back into the ad-friendly hellhole of yesteryear or we enter a new phase of the internet's wild west depends on platform migration patterns and whether or not people develop some pretty basic web and internet literacy that's been lost over the last 20 years as the internet corporatized and users had to learn less and less about how the websites they used work. my explanation here probably has incorrect information and holes in it, but that is because i, myself, do not fully understand the total extent to which the fediverse and federated protocols operate; i, too, am a layman.
that being said, i hope this was helpful to anyone trying to figure this stuff out. i've already carved my own space on a small, invite-only instance with friends, but i've got no plans to move shop until this place really does burn down to the ground. hope that helps. good luck!
61 notes
·
View notes