|
it's the future where people pay to gently caress and kill robots dressed like cowboys. for you it's just a job. you are a CJ hired to administer and manage nearly a thousand hosts in production. you distribute patches, update their firmware, do nightly backups, monitor their status, and handle failover and recovery when they go down. obviously you would do this all over the park's pervasive network, allowing you to remotely log in to any host and review their logs, diagnose problems, and enforce permissions without some developers loving around with the production units. oh wait, you can't do any of that because for some loving reason there is no directory server and the hosts' brains are not centrally managed. most of the stuff they do isn't even logged. they have to pull every unit in from the field and ask it questions if they want to figure out what's wrong. this is some amateur level poo poo. also they're going nuts and nobody even knows what's failing or can restore from a clean image. westworld's network is a disaster. only you, the white hat janitor can secure it and fix all of the technical flaws in the show. where do you start?
|
# ¿ Nov 28, 2016 07:42 |
|
|
# ¿ May 10, 2024 05:05 |
|
this thread is for discussing all of the technical flaws in westworld and how to do it right. if you want to discuss the plot go to tviv, this is a technical discussion. there will be spoilers
|
# ¿ Nov 28, 2016 07:45 |
|
first thing we have to do is get a service processor module installed in the hosts with an OOB management login so we can log in remotely even when they decide to ignore our commands. actually first thing is fixing the loving wifi in the park. this no-signal plot device has been pulled too many times already. there's no excuse for not having wide area coverage.
|
# ¿ Nov 28, 2016 15:59 |
|
don't even get me started about the host retirement storage. it reeks of body odor and they will start to rot if we leave them there long enough. these are multi-million dollar units, why are we just letting them sit idle? why don't we wipe their memory (for real), and make them janitors and cooks and other jobs we currently pay humans to do? they could start by fixing the HVAC on the storage level.
|
# ¿ Nov 28, 2016 16:36 |
|
Optimus_Rhyme posted:this is it, the worst thread in YOSPOS, nay, the forums, NO! the world! look, this company created the perfect slave robots and instead of selling millions of them to do everything people want they are wasting their time writing interactive western fiction and letting them get murdered on a regular basis. also there are real cost savings to be had in better host management solutions, especially if we're thinking about larger deployments in the future.
|
# ¿ Nov 28, 2016 19:51 |
|
Sagebrush posted:There's this one slider in the host admin panel that goes up to 20 but when you do that there's a popup that says "DO NOT RAISE ABOVE 14 -- f." It doesn't stop you or anything, just pops the warning. Why does it even go up to 20 in the first place? Why haven't we just reduced the maximum value here to 14 to prevent erroneous settings? This is probably something that should be addressed in the next patch. this needs to be better managed. any old idiot should not be able to bump a unit in production past the limit set in the directory. you need special administrative powers and sign-off to deploy those kinds of changes. the fact that developers can just gently caress around with hosts while they are in service is not acceptable. all changes need to go into source control, and hosts will only run firmware built by the build servers and signed by the auth server after it passes QA.
|
# ¿ Nov 29, 2016 07:26 |
|
Cocoa Crispies posted:MEMORANDUM about loving time. the blood bath room is disgusting and terrifying. while we're at it, I get the whole open environment idea with the glass everywhere, but honestly having people and hosts staring at you all day from the hallway or the next office is very distracting. I'm trying to write some code and in the office next to me some guy gets shot or a naked lady host is doing some exercises. and then a horse walks down the hall. and some meetings have information that not everyone is disclosed on so you basically can't use the whiteboards because everyone outside can read them. it's time we got some real walls.
|
# ¿ Nov 29, 2016 16:30 |
|
I wrote a script to go through the hosts' previous memories and compress anything older than 30 days. this frees up a ton of storage space in their heads, and it also prevents them from accidentally accessing these old memories. the next step would be to archive these to the server, there's no reason these hosts should be walking around with 30 years of cruft in their brains. as soon as I get the go-ahead from the higher ups I'm going to deploy this.
|
# ¿ Nov 30, 2016 16:27 |
|
Shaggar posted:wait, please make sure you're archiving the right ones. I think the current one is host_memoryNEW(2).bak.(prod 02-25-2139) - Copy.accdb ugh, it's like they didn't even read the memo about using big endian time stamp formats.
|
# ¿ Nov 30, 2016 17:15 |
|
we could just hook up the dogs and horses to a Bluetooth speaker, no need to get all fancy with extra faces. or maybe you could just ssh in and use a command line interface
|
# ¿ Dec 1, 2016 20:19 |
|
a little quick back of the envelope math shows that it would have been much cheaper if we just got real horses instead of paying to develop and maintain robot horses. once in a while a horse gets killed or whatever, we just get a new one. it would still cost less than rendering a new horse on the big fabrication machines.
|
# ¿ Dec 2, 2016 20:13 |
|
let's not even talk about birds and squirrels and snakes. some idiot had to spend years of their life writing code to make these things work when they could have just dumped a few real ones in there and let them reproduce and do their thing
|
# ¿ Dec 2, 2016 20:21 |
|
the fact that we don't know where our assets are located every second is a huge problem. they should be constantly sending out their location and any host that hasn't received a location approval response from our NOC in a few minutes should immediately start heading home.
|
# ¿ Dec 3, 2016 00:48 |
|
guys, you know jim's retirement party is coming up. that guy's been here forever and I know every one of you owes him for something. anyway, we got together on the down low to get him a little something special. since this is not officially sanctioned by the higher ups we've had to pull in some resources where we could, and trade some favors with some other groups to make this happen. now all we need are a few hours on the big 3D skinjob printer or a couple of days on the little ones. if you spot a free slot on any of these (particularly night shift people), please book it. in case you haven't guessed already, yes, we did the one thing he's been talking about for almost 20 years, we are fabbing a full model of his anime waifu Katsume.
|
# ¿ Dec 4, 2016 20:08 |
|
can we talk about how no one has ever discussed samurai world with the network design team? are we even ready for this kind of load?
|
# ¿ Dec 5, 2016 07:44 |
|
due to popular demand we put a host or human detector in the kitchen area. if you are having doubts about your humanity please scan your forehead and look for the answer. although, and here's the twist, if you're wondering whether you're human or not the answer is yes, you are, because hosts don't question the nature of their reality.
|
# ¿ Dec 6, 2016 16:01 |
|
Uncle Enzo posted:Ticket: #5096756897 it's not clear to my why every host we bring in isn't strapped down. will it take a broken host twitching involuntarily and punching through a tech's face before we put some safety features in place?
|
# ¿ Dec 6, 2016 18:42 |
|
for a park with over a thousand hosts, you guys spend a lot of time checking status on the hookers.
|
# ¿ Dec 7, 2016 02:20 |
|
Minnesota Mixup posted:can someone please update the versions of adblock on the hosts? we keep getting complaints from guests about them talking about sex cam sites and one weird trick if hosts can access the public internet then we have a huge loving security problem.
|
# ¿ Dec 9, 2016 10:28 |
|
having hosts not kill people is ultimately QA's responsibility. they are supposed to catch these bugs in staging before firmware goes to production.
|
# ¿ Dec 9, 2016 19:00 |
|
|
# ¿ May 10, 2024 05:05 |
|
shogun world is designed for East Asian tourists and let's just say they dialed the emotional response on those hosts way down. There's not much chance any of those will go conscious anytime soon.
|
# ¿ Dec 9, 2016 23:47 |