The final frontier begins. This is about saving the future of humanity. This is a huge victory for the good guys. You've never seen Voyager. Commitment to this course of action is not emotional. Johnny, beam us up. Welcome to another episode of Beam Me Up, a Star Trek podcast. I am Brent Allen, and I have seen every episode of Star Trek 47 times.
And I'm Matt Sonnenberg, and this is my first time through the series. And this is the show where we are on a mission to introduce people to the universe of Star Trek by watching, in airdate order, only the most important episodes that deal with the lore, the history, and the timeless message of Star Trek. And I'm not sure what it is, but I feel like you did that intro slightly differently. And part of me wants to say you're hinting on something, but I really don't know what it is. Something changed. Something changed. I don't know. In any case, one thing that hasn't changed is BeMeUpPod.com. You can go check that out. BeMeUpPod.com. Get a hold of us. Check out all the old episodes. And then go check.
Check out beammeupgiveaway.com because we're giving away some cool stuff all the time now. At least I think it's going to be all the time now. If not, you can see what we gave away last time. Beammeupgiveaway.com. Yeah, we have a brand new item up right now that you guys want to make sure you go check that out and see because we just gave away last month. So you guys definitely, if you're listening to this concurrently, go check that out. If you're listening to this in the future and the show is still going, the plan is we're probably still giving some away. So you can still go to beammeupgiveaway.com and just jump into whatever giveaway we're doing.
at whatever point you check out this episode. Before this, today's episode is the 13th episode of Star Trek Deep Space Nine season five, entitled For the Uniform, or as I like to call it, look down, look down, it's Michael Eddington. Look down, look down, Ben is going crazy. In case you didn't watch this one first. In this episode, Cisco becomes obsessive about capturing Michael Eddington, the Federation traitor. Matt, we're gonna get into this episode, but you told me right before we went in, sometimes I'm curious as to why you choose an episode.
This one I knew right away. Talk to me about it, my friend, for the uniform. I think last time we saw Eddington, we kind of talked about how he's a new big bad of sorts. I mean, maybe not as long and strung out as perhaps like the board or something like that. But temporarily, at least, at least as much as Seska was. It's fair. Yeah.
Yeah. Good comparison. Good comparison. Yeah. Or lore. You know, because we get these right. Seska, Voyager lore. You know, he just, you know, they don't pop up a ton, but they do pop up enough. Yeah. Yep. But like, I was kind of sad to see Seska go. I thought she was going to be a great long-term villain. And now Eddington, Eddington on the other hand, I have a tougher time with. I kind of told you from the beginning that I didn't like Eddington and he needed to go. Oh, you nailed this from the very first time we saw Eddington in the show. Like when he was still wearing Starfleet uniform, you nailed him. And that's, that kind of makes me wonder how much did they have planned back then?
Did they have this whole idea that he was going to turn or was this just happenstance and turned out that way? And so he like because if they had that in mind, I could see, OK, if they told him that and said, hey, by the way, this is going to happen eventually. And he can he can build some of those traits and stuff into his character that make you not like him a little bit more. But part of me wonders if that's just how the character was. And they said, yeah, we don't need this guy on the ship anymore. So we're going to make him a bad guy. Or the writers saw him and were like, oh, he would make a good bad guy. Didn't mean for that to happen. But, you know, sometimes the way the actor portrays him. I mean, yeah.
I think the biggest difference though, it's like the closest, closest comparison I could come up with. And I think you said you agree is Seska. and like seska i feel for whatever reason it made sense to me that she was a good bad guy sure whereas eddington i feel that they are i feel it's more of a stretch to make him as smart and as clever as they have now written him and giving him so much credit i mean in this episode we found out like planting viruses that neither chief o'brien or odo ever ever found out about like you're not that good i don't think like obviously that's the way your character is written now and so i guess it's canon and i guess you are that good but i don't know i never felt you were that good i felt you were more on the in-up side and maybe Well, that's that's how good you are is he made me think you were inept. I don't know. I don't know. Maybe he's just too good and I don't like him for that. But there's something about Eddington. I just didn't care for him from the beginning and still don't really like him as a bad guy. Even all of that's fair, Matt. That's that's.
I think, I think the best bad guys are the ones you really love to hate. You know what I mean? Uh, and, and this is where I point back to like a Kai win. Like, like she makes my skin crawl. I hate everything about her and I love to hate her. Like there, I don't want to like this woman. Dolores Umbridge over in the Harry Potter universe. We, we compare her all the time. Like you, like there's Voldemort. I can deal with him as a big bad. I, but, but Umbridge is a different thing altogether. And she might actually be the most evil person in the entire universe over there. Kai win.
well, her story remains, uh, uncompleted for you yet. So we'll let that lay out there, but there are some, there are some bad guys like a Michael Eddington where you're just like, I don't like this guy and I don't like anything about him and I don't want to like him. Like, so you're not wrong on that, Matt. You're not wrong on that. Uh, this episode today for the uniform, Matt, I like this episode. I really do. Um, I have a particular affinity for the almost overuse of the Les Miserables, uh, comparison. And I asked you some time ago if you'd ever seen or heard or, or, you know, if you knew anything about the play and the script, I never really knew anything about this until I got married to my wife. Now, those of you that know my Star Trek story know that
My history with Star Trek goes back long before my relationship ever began with my wife. I never fully understood this episode until she is the one who introduced me to Les Mis. And, you know, I don't love it like she does, but I certainly appreciate the story. And I know it fairly well at this point. I highly recommend it. Go watch the movie. It's pretty good. Even with Russell Crowe singing, which is not great, but whatever, you know, it's good. But I have an all new appreciation for this episode really because of that. And I love.
you know, this idea of, you know, in these great stories, the heroes have a villain that forces them to sacrifice themselves to become the hero. And so in order to catch him, I've got to become the heat, the villain, you know, like we, that story, that, that line of reasoning and he does it. And you see Eddington be like, all right, you're there. I'll surrender myself to you and sacrifice myself. And Cisco's like, yeah, whatever, dude, I got you. Yeah. I mean, honestly, that's a big reason I love this episode is Cisco's line of reasoning.
at the end. Like the last 10 minutes of this thing are fantastic. Oh, it builds this episode building and it doesn't get to just the typical pew, pew, pew act five. Like it, they, they layer it in just the right way as they go. Cause Matt, I don't know if you noticed, there's no B plot in this episode. I was wondering if you were going to try to pull something out. And I thought like 75% of the way through, I'm like, you can maybe kind of pull this out to the side, but I haven't been. No, it's all one plot. Like it was straightforward. Like this is what we're doing this episode. Everybody's involved. Well, Matt, before we get into all that, and we'll, we'll definitely dive into all the deepness of this episode that it is. I do have one.
spotlight that I'd like to do on this particular episode, but it has nothing to do with anybody you saw on screen. What I'd like to point out is the person who actually wrote this episode. He has a name that is that is much loved and one that should be very well respected around the conversation of Star Trek. And his name is Peter Allen Fields. Now, Peter has been around since the days of Next Generation.
Back during Next Generation, we saw him all the way in the latter half of the fifth season. And through the sixth season, he was a script consultant, which is a fairly low level person. He's actually a lawyer by trade. Today, he's 84 years old. So I haven't done the math on what that would be. So he was in his 50s, I think, about that. Yeah, 40s or 50s when he started working with Star Trek, right? Just like I said, as a script consultant, he wound up doing things with the writing staff. He became a co-producer here on Deep Space Nine through the first season and then through the second season. He wrote three episodes for Next Generation, wrote three episodes here for Deep Space Nine before leaving Star Trek. But he continued to write like sort of on a free.
freelance basis. And he contributed like another seven episodes after that, after he left, if, if I understand the timeline, right? Somebody's like, no, he actually wrote four and only contributed six, whatever it is. Email me. Let me know. I'd love to know if I'm wrong. But as I understand it, that's, that's pretty much how he, how it works. But, um, he was, he was instrumental. He is the guy who created the character of Elon Garrick and introduced him to us back in that second episode of deep space nine. And, um, oh gosh, uh, let's see here. One of the other. So in next generation, we actually did two of his, two of his three episodes. We did half a life. If you remember that one with, um, locks on a Troy and the guy who had to commit suicide at 60 and then also the inner light.
the super fantastic Picard episode where he lives a whole other life. And here on Deep Space Nine, he did Dax, which was the one where we developed the story of Dax, which we did as an extra viewing episode. He did Duet, which is a fantastic one. He did The Circle, which was part of that trilogy. He did Blood Oath, Necessary Evil. He did Crossover, which is the one where they sent him over to the Mirror Universe for the uniform. And he does two more super important episodes. So the episodes that this guy does, like when you see his name on it, and this is one of them, mark it. Because when his name pops up as the writer, you're like, ooh, this one's going to be a good one. You know what I mean? Typically, you're like, wow, this is a Peter Allen field. So he actually won a Hugo.
award for the, for the inner light and his work on that as well. So after, after he left deep space nine, he actually went and joined Michael Pillar when he left Voyager to go rest. Like he did a couple of other shows before he started getting sick and passed away. Peter on films worked with, with Michael Pillar, like continued to work with him and kept that relationship going. So anyway, I just want to point him out to you. You're probably never going to meet him, but you will definitely hear him. His again, his, his is a name that is very well respected around the world of Star Trek, Peter Allen fields. So with that, Matt, that's all I have because everybody else we know we've met everybody at this point. So I'll turn it over to you. We'll talk about the A plot. There is no B plot, but let's start Matt where we always like to start.
Are there any specific plot points or things that came out that you're like, oh, I got to make sure I hit on that, even if it's not really a part of the plot? I just found myself taking so many notes in a row, which is like everything's listed under the A plot. Okay. So I'll see what I can do. However you want to do it, brother. Yeah. The hollow communicator. Yeah. Let's talk about that. I thought you pulled that one out. Yeah. Yeah. New for this episode. They made a point of it. That's interesting. I mean, that I was trying to think of reasons for that. And it's like, okay, one.
to just kind of say, hey, yeah, we're still developing new tech, I guess, is one thing. Part of me wondered if it was like a cost savings thing. Like, was it cheaper to just put the actor on the stage with everybody else instead of putting them up on a screen? Do you have to employ a secondary camera to put them up on the screen? I don't know. Because then they don't have to build a set behind them either, right? They don't have to bring it in and turn the cameras around and do a new screen and all that kind of stuff. Yeah. So like part of me said, maybe it's just a cost savings thing. It's like, yeah, let's just write some Technobabble and say, yeah, they can appear right here on the bridge with them.
Like I, that was part of it. But then I kind of wondered, you know, what other fun things could they do with this technology? If you can make yourself appear basically anywhere. Cause like the other captain said, it looks like you're sitting on my bridge. And like, I guess I'm guessing like, do you need special equipment to either activate or project one of these things? I mean, the guy was kind of in that little circle thing, you know, on the bridge. So you would assume that they have one too. Yeah. My thought was, you know, they can't like say.
project themselves onto a bad guy's ship and say, ha ha ha, see what I just did. And, and like create distractions or something that way. You know, I feel like we've seen that happen with bad guys doing that to the, like the enterprise. And I can't think of a specific episode off the top, but like they just beat literally, they just beat him in a hologram. And we were like, Oh, Truder alert. And he's like, no, no, I'm just a hologram. I'm not really, you know, uh, and they mess with them that way. I mean, that's what happened time and time and time again in this episode. I made the note that the Maquis are really good at faking signals because they, you know, had this probe disguised.
to make them think it was their ship. They had, uh, um, I think something else was Eddington. Um, I don't know if they were disguising their ship again or just disguising something. And it's like, you guys should have like anti whatever that is technology by now. If you, if you know that my key are just going to keep doing this, like with all the sensors and everything you have, like, can't you sense if it's a fake signal or just like, that's what gets me sometimes. It's like, sometimes they can scan a ship and tell me exactly how many people are on it, exactly what cargo they're carrying, exactly who those people are that are on it. You know?
even if it's just their race or whatever. Um, but then other times it's like, you can't tell that that's just a probe emitting a signal and not an actual ship. Didn't you like scan for life forms or something? Like I, I don't know. I don't know. So, I mean, it's always what's convenient for the story. I get it, but some of it just feels a little inconsistent sometimes. Well, let's talk about the hollow communicator. Yeah. Because it's interesting. You pulled out the two things that you pulled out, which were, is this just about advancing tech? And then was this a cost savings thing?
Okay. So here's the story behind it. Uh, Robert, uh, not Robert. Well, Ronald D more was really kind of, he'd been pitching this thing for a while to the showrunners is going, Hey, so view screens were like, so TOS man. Wouldn't we develop like new technology that would actually, you know, we've got all these fancy holodecks and everything. Can't we just put them on the bridge and just let them talk like normal? And our Stephen Bear was like, yeah, shoot, let's go for it. And for this episode, especially they're like to have Eddington there on the bridge talking directly, like it made the drama so much more real that they thought would have just been obliterated if they were trying to do this through a view screen. Right. Like, so, so they were real happy. You're almost, I'm kind of surprised, even though he knows it's just a hologram or whatever, like Cisco didn't get up and try to punch him in the face. Right. It's like his hand goes through the light. Yeah. Yeah.
Well, yeah, it's it's a thing. So they went for it and they said, yeah, we're going to do it. Let's let's. And they said, you know, they've been installed and chief O'Brien's been working on it, blah, blah, blah, blah. They went and they did it. However, there are some logistical implications that doing something.
like this, that the writers didn't really count on. And the visual effects team actually had a really hard time with this one because they were trying to make it look like this was a communicator and not a beam in. That was the problem they were having. Like, it just looks like just beamed in and they don't want that. It's got to look like it's a, it's a projection. And so they had to have like extra cameras doing this weird work going around it to show that it actually is in 3d, a 3d projection. Not because remember we're watching this on a 2d television screen, right? Like I said, no, this is a three. It's not just a flat image, but you know, they have all this kind of stuff and actually it wound up costing a lot more money than just putting somebody up on a view screen. But I received a bear was like, you know, this is great. We don't have to, you know, bring in the backdrop and the set and pause.
and do all that kind of stuff like we just put this guy here. But it did. It wound up costing more money. And the visual effects supervisor was like, look, you guys keep doing this. This goes against Gene Roddenberry's original vision of the future of view screens, which was created in the first place to save money. And so now it's costing more money. So unfortunately, Matt, they would only go on to use the hollow communicator one more time and they just go back to view screens. And I hate it because I think the hollow communicator is a super cool piece of equipment. But the whole reason, as you just said, was, hey, this is the 24th century now, 100 years later. Shouldn't they have better communication technology? And the answer is, yeah.
The tech that they used or how it looked, honestly, kind of reminded me of what we started to see in what is yet a few years away at this time of the second Star Wars trilogy. Yeah. Because they kind of implement a lot of like holographic images of 3D people and such. Yeah. And it kind of reminded me of that. I'm like, once again, this may be kind of Star Trek pioneering this and saying, hey, look what we can do. But yeah, like that's that's the vibe that I got. And I had to remind myself that this came first.
It is true. Yeah. Yeah. Cause episode one wouldn't premiere for another year after this episode, uh, aired a year and change actually. So yeah, you know, it's one of those, it makes me sit back and go, you know, we, we have FaceTime now as we record this. Yes. I really would like the, at least I think I want the hollow communication. Cause honestly, I don't want to use FaceTime a whole, I don't want to talk to you. Just text me. Like, like my preferred method of contact is actually the least amount of contact I can have with a person. And I think that's true for everybody. Like, or most people, like I don't want to pick up the phone and talk to you. I don't want, you know, I don't want to FaceTime you even less. Cause I got to worry about, I mean, Hey, the reality of it, you can text someone when you're on the toilet. You don't want to FaceTime them.
We'll be right back. Right. But I mean, Matt, so but for what you and I are doing right now, though, to have you like because we're obviously we're in two different places, several states away. The magic of the Internet is allowing us to connect and have this conversation to have like a technology where you're actually like sitting right here at the desk with me. And we're having this conversation like, you know, man, I got to tell you, I've been podcasting a long time and I think you'd probably agree with this. There's a different energy and a different vibe on a podcast when two people are in the same room versus when they're doing it over the Internet like you and I are like as good as this show is. Oh, we'd be 10 times better if you and I were in the same room, you know? So, yeah. Yeah.
I can't explain why it's like that. It just is. So that would be a situation where I'd want it, but that's not, um, that's not everyday commercial use. I don't think, you know, cause I still mostly just want to text like, yep, I get it. I get it. So that's all I really have about the, um, the hollow communicator, but I, I was so glad you put, you pointed that out and I'm glad you pointed it out first. So there was one point in the episode where they, they reminded us of something that happened, which was kind of nice because I'd forgotten, but it just made me hate Eddington even more when Odo came in and he's like, captain.
have you reminded starfleet that the only reason eddington was here because it was because they didn't trust me and then i i love the little interaction there too it's just like i know i haven't done that it's like would you please it's a good point right it's a very good point yeah they brought him in because they didn't trust odo now odo's the one we can trust and eddington is the one causing trouble right like Like I said, how much of this did they have planned from the beginning? OK, can I go back and remind you of that? Because we've talked about this quite a bit, but it's fine to talk about again. So remember, they originally brought in the character of Michael Eddington because Colm Meany was out doing movies and had other conflicting things. So they brought him in basically to be there when Colm was out. OK, like that's why they created the character. And then it wasn't until the finale episode of season three called The Adversary.
Which, if you remember, that's the one where the Changeling pretended to be the ambassador. And Cisco and Eddington had that conversation in his quarters on board the Defiant, which is where you really started hating Eddington. Because they have this whole conversation, you know, Cisco's like, well, look, if you want to be commander, you could transfer to command. And he's like, oh, no, no, no, that's not for me. That's not for me. They just wrote that. And Eddington played it so weird. Like, he played it like, maybe I'm a Changeling, maybe I'm not. Right? But then remember, I said, this is where the internet started coming along. And people started going, Eddington's a Changeling, Eddington's a Changeling. And the producers went, no, Eddington's not a Changeling. So we're going to make him something completely different. They turned him into a Maquis. Yeah. Like, so it kind of, it was a
combined with subterfuge of what the fans expectations were that resulted in this. So it wasn't necessarily planned from the beginning, but you know, and then eventually they didn't need him anymore because Colmeney stopped doing other movies and stuff and just committed full time finally to Deep Space Nine. So they were able to get rid of him and frankly got the best episodes with him because other than that, he'd just show up every once in a while. He was just annoying. He was annoying Odo. That's all he was. That's a big part of the reason. Like it was double duty. Like they didn't need, they had Odo. They didn't need him. Yeah. I think they were going to try to probably introduce a little more conflict between Odo and Eddington.
Yeah. You know, and it just never, it was never something that materialized. Like they eventually started working together. Okay. And it was fine. And it was just, he was there. That's all it was. Planting his viruses. Right. Like Suska did on Voyager. Towards the end. Yes. Of this episode. There's a really weird, I want to call it a quirk, but did you notice? Okay. No. Did you notice that Cisco was wearing a phaser? No, I've never noticed that. He was. And I'm like, interesting. I kept expecting something to happen because I'm like the only time they ever wear their phasers is when there's going to be fight sequence.
And usually it's when they like go down to a planet or something. Sure. Which would make sense why they take that with them then. Yeah. But he was like alone in his room. I think it was when.
Dax comes in to talk to him maybe towards the end. But like he stands up and he's got this phaser on his hip. And I'm like, what you doing there, Cisco? What's going on? Like we always talk how the phasers come out of nowhere because, you know, they don't actually fit on the uniform. They never wear them except when they actually need to use them. But I think he actually wore it without actually having to use it. I can't imagine why he would have actually worn it in person unless he was going to wear it while going to apprehend Eddington because something might be happening or something. I don't know. I think it's not. I'm trying to remember, but I think it might have been while he was making his Les Mis speech. Maybe it just made him look more villainous police officer like, you know, because the villain in Les Mis was a police.
officer right so maybe it had that vibe to it this is the second second most um time I've spent with Les Mis okay so you mentioned in the beginning and I don't know if anybody else has knows my background with Les Mis but I basically have no background with it I have not seen the play musical I have not um is it a book I don't know it is a book yeah okay I haven't read the book I don't even know um oh yeah because because he sent him the book duh um so yeah I have not read it it's a Victor Hugo it's a Victor Hugo yes yes because Dak says I can't stand Victor Hugo right um But the main interaction, the main reason I have any hint of what Les Mis is, is when I was a kid watching Animaniacs. Okay. They do a Les Mis bit in one of the episodes. Do they? Yeah. I'm not surprised. Not surprised at all. And apparently like there's a set of characters that, I mean, they have one specific episode. I think it's called like Les Misere Animals or something like that. Okay. But like I've been told that they just always kind of.
feel like characters out of les miz most of the time um but i know they parody other movies as well like that set of characters um like that's how i how i learned what rain man was before i saw the movie was from animaniacs like little things like that i love i love but that's why i was very glad that in this episode as they do so well in most episodes they give you all the background you need even if you've never seen or read oh sure the source material that they're referencing right yeah they have to right sure and they also have to point out exactly what they're talking about from the source material right there's so much Well, yeah, that's why they had to sit down and it's like, OK, Cisco and Dax, here you go. Explain away. Right, right. Because I mean, in Les Mis, especially because there's so much going on in Les Mis, like the storyline, while the main storyline is true, is between Jean Valjean and Javert, who Michael Eddington takes up to Jean Valjean and Cisco takes up to Javert. But they become almost secondary characters by the second act until they just sort of come back and do the climax at the end. And then that's it. They almost get pushed to the side throughout the play. So that's just a play. I don't know about the book. That kind of tells you how big Les Mis is, though, is that when they started mentioning character names, like I didn't really recognize the names.
there. But when they said Valjean, like, and I think they only ever say Valjean in this episode. Right. In my head, I'm like, oh, that's John Valjean. I'm like, right. I know that name. Right. Right. Hey, Matt, real quick, 10 points. If you name the other Star Trek reference to John Valjean or just Valjean. No clue. I'm going to say it's probably has something to do with Q. That feels like something he would do. Okay. It was the name of it was the name of Chakotay's Maquis ship was the Valjean. Okay. So apparently the whole lamest thing is something to do with the Maquis.
Yeah. He's also a French name. Oh, we lead. You know what I got to see for. So I'm sorry. So you have no idea what my opening thing was about. Look down, look down. It's Michael Lettington. No. Other than I think you, it was at the song you sent me once. Did you send me a YouTube video? I did. That was a song called Master of the House, which is hilarious. That is not the one I sent you. Okay. Look at it. Look at it. It's not that it matters much, but I'll tell you, it's the opening song to the play. I assumed it had something to do with Les Mis because I mean.
They definitely mentioned Les Mis, and I know it's a musical. I know that. I hang out with musical people. And you've never seen Les Mis. I've never seen it. I can make you this promise. I will not take you and put you through that torture. Oh, don't tell my wife. Anyway, I think this is my first time officially. Oh, maybe it's the second time seeing Cadet Nog. Who just comes out of nowhere? Yep. Just hoof. He's there. I have no idea. How did he get there? I don't know. What's he doing there? No clue.
we needed his big ears right right so the scene where they had him just just fyi where he's like relaying all the comms in the ship which i thought was that was a really cool well done scene the way they did that oh yes i i i mean sure we'll bring that up now that that is a fantastic scene just all the layers of things like pardon me wonders if they piece that together in post all the audio we were hearing or if they actually did that like one shot live like that whatever it is like it was impressive to have all that going on and everything not, not to stumble over each other too much. And there was overlapping talking and, and like you could hear Nog in the background, but Dax in the foreground and yeah, like it was nice and it was fun. And I made a comment about it because I'm like, I know your ship is disabled, so you need to do things like this right now. But it just feels like this is a sort of like training exercise that you run from time to time. Now, you know, you should be running from time to time. Because when technology goes down, they didn't have too much of a problem with it. No, no, because, you know, I got to tell you, complete side story. I used to run a pizza shop. I think I might have told you the story before. One of the things that I, and this would drive my employees crazy, but about every six months or so, maybe even less than that, I would go in and I would shut the computers off.
And I would make the employees do everything by hand like the old because you realize like we didn't use computers like for ordering and pizzas until like, you know, at the time, like 10 years earlier, people have been doing pizza for years on paper and stuff. So I had to train them how to do it. And especially during the winter where I was living at the time, we get these big ice storms that came in and would knock power out. We still had to keep making pizza. Right. And like I was and it happened probably about once a year. We needed to be able to get the kits out and just go by hand until power was restored because we were an essential service during a weather hurricane or weather.
things so you were you were still able to cook the food without power yes because it was a gas it was a gas oven oh so all we the only thing we really have in the the the fridges were on uh backup generators sure so the fridges were on backup generators we had emergency lighting that we could use and then the gas the stove was gas and i guess the phones ran off of power from the telephone company which didn't run through the main power system of the store or something like that so i don't know i mean you know we're making pizza in the dark for sure You know, it's not anyway. All that you say to go back to your point of you got to run those. Like, what do you do when your technology goes down? Technology is great, but only when it works. Right. So that scene, though, I just want to tell you, it was an homage to a movie back from the 50s called Run Silent, Run Deep. We're apparently that. Yeah. And they like one of the things they really wanted was for this to feel like a submarine warfare episode. And that was part of a good point. Yes, it does have that feel to it. But I mean, even just the way they shot that that scene felt different from how they normally portray things happening on the bridge. And I didn't like break down and analyze exactly what they did. But.
Yeah, it was definitely different, but it was good. So the very opening of the episode, Cisco is down on this planet by himself. Your captain is down on the planet by himself, theoretically meeting with a sketchy informant that you know next to nothing about. He doesn't even know what he looks like. He doesn't even know what he looks like. I know. Do you know that he actually exists? I mean. Riker would never let Picard do that. Exactly. That's what I'm saying. It's like even just having like, I would have expected when he's walking through that little town or camp or wherever those people were, like you glance over and you see.
like Dax under a hood or something like that. Like there's someone there that he is friendly to him, but isn't interacting with the main characters. Just, but is there just in case something goes wrong, right? That's what I would have expected. But no, he's down there all by himself. And I'm like, is this standard? Like, it just seems super sketchy to me. Like, I'm guessing, yeah, they specifically requested that, you know, Captain Sisko, come alone, blah, blah, blah. But I don't know. I don't know. We've talked about that many times. You don't let your captain go anywhere alone like that. I think the rest of the notes I have then really just come down to this giant chess match of an episode between Eddington and Sisko.
All right. Well, I mean, let's let's get into it. You're talking about, obviously, the spot where Cisco is stopping at nothing to track down the Federation trader, Michael Eddington. But Eddington always seems to be one step ahead of him the whole time. That is until Eddington mentions Les Mis, which gives Ben an idea of how to defeat Eddington. Ben will have to become the villain and go to pretty extraordinary lengths to capture his foe. So every time in this episode that Eddington and Cisco have a conversation, there's probably a chance that you could pull some kind of like Star Trek message out of their conversation. I'll just tell you right now, I didn't. So if there's anything along those lines you want to talk about, you're probably not to bring it up.
Okay. But, um, they were good conversations from the beginning, from the beginning. And there are always little things that I sat there and made me think it's like, man, you got a point there. And like, sometimes it was Cisco and sometimes it was Eddington that I was agreeing with. And it's like, oh yeah. Like Eddington from the beginning, like these people don't want to be resettled. They want to go home and live the lives that they built. Right. Like, okay, I get that. I get that. But then Cisco fires back. It's like, these people are not the victims of the Cardassians. They're not the victims of the Federation. They're victims of the Maquis. You sold them on this dream that they might actually be able to go back to those lives. Right. When he's basically saying, you know, that's not an option anymore. Like.
That's the past. They need to move forward. And you're kind of just holding them here. I'm like, wow, no, you have a point Cisco. Maybe it's just great writing that they got me, you know, pulling me both ways back and forth. And, and it's, it's, I told you before, I, I usually like to let the writers take me on a journey. Sure. I'm not here trying to figure out the episode all the time. I'm not here trying to disprove everything or, you know, I'm not even necessarily rooting for one guy or the other. Right. Sometimes I am, but yeah, this episode goes back and forth and back and forth.
But even though, like we said, there isn't really a B plot. There's just this one big plot the whole episode. And normally I would say, well, that's going to be kind of boring and drawn out. And it's like they should have thrown a B plot in there to spice things up and split it up and keep my attention. But no, in this case, they had my attention the entire episode. And it was fantastic. So, I mean, Matt, would you agree?
This episode is pretty straightforward, right? Like it's, you know, Eddington dangles a carrot in front of him. Cisco bites. He doesn't do it. They take him off and they put him back on. There's this whole thing with the other guy who frankly doesn't really matter. The other guy, you mean the other captain? Yeah, the other captain. Okay, because I was going to ask about him eventually. I kind of forgot about that. They actually intended him to be a recurring character and they forgot about him and never brought him back. Because I was going to say, I don't think we ever got his name.
I think Cisco always just referred to him as captain. You might be right. I don't, I don't recall his name off the top of my head either. I'm sure, I'm sure he has one. I bet I could look it up right now. I'm not going to, but yeah, it might be in the credit somewhere, but I don't know that they ever gave us his name. Like they mentioned his ship a lot. Right. And then when, when Cisco's talking to him, he always just like, so captain, what do you need? Like, I, I don't know that they ever mentioned him. Right. Cause usually I make a note of those things just for, for reference. So with all that, um, I think the most important thing though is the lay biz comparison where Cisco, you know, Eddington gives him the thing and Cisco sits up and goes, okay, I'll become the villain. And I think we've got to talk about what Cisco did.
That was the huge twist. That's what we got to talk about. I was excited to see where where it was going. All right. So so take me through your experience of going. He's not really going to bomb this planet. He's bluffing. He's not going to bomb this planet. I had no doubt in my mind that he was going to order the strike. Did you really? Even if he had to press the button himself. Now, I still have questions. OK, like Cisco should lose his job forever and be put in a brig somewhere. No. OK, no. Like part of me wonders. And I think that they imply that it's not this way. But part of me wonders, like, did he actually poison the planet?
He obviously did something that had an effect on it, which I always thought was very interesting that we could see that effect from space. That felt wrong. But I understand they did what they needed to do to show it to the audience that something was happening. But there's no way we'd be able to see that from space. But part of me wonders if he just, you know, would have attacked something to cause a reaction to get them to freak out and say, yeah, he actually did fire something at the planet. We have no reason to believe it's not what he told us it was and that we need to leave now. So like to me, that's that's the route that I thought they would have gone. And that last little conversation that Cisco had with Dax would have been. So, Captain, would you actually fire at the planet? And it's like, oh, yeah, it's just this harmless, blah, blah, blah.
Yeah, exactly. Right. But that's not, not what we get. And we get the conversations like, did you get permission? It's like, I knew I forgot something.
And I'm like, OK, I feel this would fly on Voyager. You're in a different quadrant by yourself, right? She could get away with a lot easier over there, right? And she's under extreme circumstances and all that sort of stuff. Absolutely. She doesn't have the ability to call and ask for permission. She just has to make her best choice, right? But Janeway is a lot more Picard, I think, than Sisko is. She's a lot more straight and narrow. She's got a lot more to prove. Sisko shows in this instance that he's willing to disregard his own ethics and his own Starfleet policies, violate Starfleet policy to get the job done when he thinks it's warranted.
He's a rebel. He's a wild card. And honestly, the way you just described it made me think he's a bit more Kirk. So you're nailing everything today. That's what they intentionally did when they wrote the episode. They're like, he's going to do something that Picard would not have. But Kirk probably would have. So, you know, a lot of people look at this and they go, oh, that's not Starfleet. That's not Star Trek. That, you know, it's a criticism they bring against what Cisco is doing. You're like, no, Kirk would totally do this. Kirk would absolutely do something like this. Picard wouldn't. And we say it's not because Picard wouldn't do it. Picard is Starfleet to us right now. Right.
But yeah, I mean, you know, so I don't think I ever really understood what he was doing. You know, the idea is Eddington did something to the world that made it inhabitable for Cardassians to live there. But like everybody else was OK. Oh, yeah. Apparently they have the same thing they can do with humans, but everybody else is OK. And that's all he did. He's like, well, you did this to a few people. Well, I'm sitting here going, OK, if I'm a Cardassian and I own these these these planets.
I'm going to put the you can't be a human and live here stuff out on all these. You know what I mean? Like if I just took over, if I'm Cardassian, that's what I would do. Why is it this? The Federation has this chemical agent. But there's, you know, what he did was he leveled the playing field. That was the phrase that Ronald E. Moore used. Cisco just leveled the playing field between the Cardassians and the monkey. That's all he did. Oh, yeah. Tell anybody unless they didn't get out when you warned them. Exactly. Unless they didn't get out. That's their fault. He gave him an hour warning and said, yeah, this is what I'm going to do. Get out now. And nobody did until he actually fired. So because I like because he's starfully. He wouldn't do that. What do you bet? That's what they thought. That's what they were betting on.
But as soon as he said, I need to become the villain, right? Cisco is going to play that out to the fullest. Yeah, but I have no doubt in my mind. But in every other episode, he's going to bluff. I mean, even you were sitting there thinking, oh, he was just going to shoot something else in there and not it. He's a bluff. But that's what I'm saying. It's like I knew he was going to fire. Yeah, I didn't know what he was going to fire. And like I said, that final conversation kind of confirms, at least I assume that's why they put that in there. I mean, it was a little bit of comedy to lighten the mood at the end of it, too. Sure. But yeah, I mean, he will have everyone believe at least that he actually did that.
Uh, so it's, he needed to prove his point. Yeah. He needed to become a villain because I, that, that was another one of those kind of revelation moments in here where he's like, Eddington sees himself as the hero of this story. Right. And so many, I mean, we don't get enough of this. And I think Marvel is starting to do more of this type of thing where we get like stories from not always the hero's point of view or who we consider the hero usually. Right. But, you know, turn that on his head a little bit and take this from the villain's point of view or actually maybe Disney is a better idea of this yet. Um, I haven't watched it yet at this point, uh, but I know like Cruella.
Like they're focusing on what we know as the villain of the story. And I think it's always kind of been that way when people dive in and discuss these. It's like, well, to them, they are doing the right thing. They are doing what they think is best. Sure. I mean, that's what we hear from Eddington time and time again throughout this episode. He keeps telling Sisko, it's like, you're fighting a war, but you're on the wrong side, man. You need to come to our side. You're on the wrong side. And so he thinks he's doing what's best. Right. And so that's why, like I said, to defeat him, to defeat the hero, he needs to go full villain. So Matt, here's the question.
Would you ever play chicken with Captain Sisko? No, no, no. Here's the here's the question. How far would you be willing to bend the rules and take extreme action and become a villain if it served the greater good, even if it violates all your principles? Because that's what he did. He violated his principles. You know, he violated Starfleet policy for sure.
just to get to the, you know, in this case, just to get to the bad guy, but to serve the greater good, to end the Maquis threat. You said it, you said it. Oh, what? Oh, the greater good. Oh yeah. Yes. And that's why he's the real villain. And that's the thing. It's like, as soon as he said the greater good, I'm like, that's fill and speak. Me personally, with my personality, I would have a very, very, very hard time doing that. I want to believe that there may be a set of circumstances. I can picture that, that I might go so far, but.
one, it had, it would have to be a very specific set of circumstances. And two, I think once again, in reality, it would just play out in my head and it wouldn't actually do it. Yeah. Like, I think that there may be one, one specific set of circumstances I could, I could play out in my head in which I would, I would do that and I could justify it to myself. Like, yes, that was the right thing to do, but I still don't think I could ever actually do it. Yeah. Here's the thing, knowing my personality, if the action would result in something like bringing about the end of a war, like something huge like that, you know, or maybe even turning the tide in a war or something of that nature.
I think I would do it if it was something as much as just to get his own personal pride back in line. Because to me, that's my that's the problem that I have with this. At the end of the day is why Cisco did it like he wasn't going to hurt. Cisco wasn't hurting the Federation to allow Michael Eddington or the Maquis to stay out there. You know, this became personal for Cisco. And he went through that because of a personal vendetta against Michael Eddington.
You know, which we saw earlier when Cisco was in the box. And yeah, they took the assignment away from him. And Cisco was like, no, he's right in front of my face the whole time. And I never saw it. And you know, this was a personal thing for Cisco. It didn't, it didn't really like, yes, they needed to get their guys under control. Yes. They're outlaws. That to me is not a big enough reason to do what they did. You know, now to be fair, all they did was just say human life can't stay here. And if you didn't leave now, he only gave an hour. That's not enough time, dude. Like, no, that's not enough time. Like we, you got to give people weeks, you know, to get their crap together and get off and plan and evacuate and all that kind of stuff, you know? So that's, that's my problem that I have here.
But I do think that I would do it if the circumstances were actually much bigger. Well, I think part of the reason for his hour timeline was that Eddington and crew were like on their way to the next Cardassian planet already. Sure. Right. and so he needed to prevent them from you know bombing another planet with their anti-cardassian drugs so like that that was kind of his plan but like i mean his whole theory behind you know why he was doing it like he said and he kind of brought this up a little bit but the maquis have become an intolerable threat and i'm going to eliminate that threat yeah like that was his justification for doing what he did right and now as you said in the beginning should cisco probably lose his job for what he did probably is he going to for the sake of series i don't think so um but even in reality, unfortunately, like sometimes you see this people in power do dumb things and should be held more accountable, but because of their station or because of who they know, we don't always see those things happen. And so I don't think it's completely out of line with like that kind of reality that Cisco is allowed to stay where he is. And we also know people don't get fired in Star Trek because otherwise data and wharf and probably the car at a time or two and Riker and you know, all those other people would give Odo would have been fired by now. Um, but yeah, man, you know, that's to me, that's the episode.
Yeah. What do you do in the middle of all that? It's a good episode. It's a good question. It's a good question. And we end with Eddington is now in custody. It seemed too easy. Well, he, I mean, Cisco played Eddington. Okay. Here's the question. Let me ask you this. Do you think Eddington set this up so that he could sacrifice himself and become a hero? Like, was this whole thing really about Eddington's pride or was this, as I said, really just about Cisco's pride? Like, was it really about Eddington or was this just Eddington being overdramatic or whatever, you know, and he gave in when, you know, he didn't see a way out. Well, I think I can see it both ways.
But I do kind of feel that when they first brought up Les Mis, they kind of gleaned some initial information from it, but then kind of let it sit for a while. So I was very glad when Cisco came back to it and dug deeper because that's something you don't always see. I'm like, he sent him that for a reason. Like, I don't know how deep it goes, but he sent him that for a reason. And I want them to explore that. And they kind of ignored it for a little while. I'm like, so I was kind of happy when they came back to it and started digging deeper and made deeper connections with it. Now to your question, whether or not, you know, like that was all part of the bigger plan for Eddington.
because I like good bad guys, I want that to be all a part of his plan, but I don't think it was. I think that more than anything, that was kind of his ego getting in the way and he kind of tipped his hand and that was his downfall. Like if he hadn't been so egotistical to send that to Cisco, right? Like he made the reference once I think, but he wouldn't have sat down and made that kind of started reading it and made that connection. Right. And he wouldn't have come up with a plan to, to capture him then. So like, honestly, I think that that was his Eddington's downfall.
All right. All right. But Eddington's in custody. So got his man. It's just going a little crazy. Let's just say, don't mess with that man. As you said, don't play chicken with him, right? Yep. All right, Matt. Well, that's all I got on this episode. Those are, those are, I think the big highlights of it. You got anything else you want to talk about before we get out of here? I think that works for me. All right, Matt. Well, I will officially ask you, although I think I know the answer to all of these. Did you like this episode? Would you want to watch it again? And do you understand why this was part of our run? Yes, yes, and yes. I think maybe you don't understand why this was part of our run.
I think you may think you understand, but I think you may not actually understand. And if anybody out there would like to understand, go back to our charting the course episode where we talked about this. I talked about it with my guy, Jeff Aiken from the Starfleet Leadership Academy podcast. You guys go over there, check that out. We had an in-depth conversation about this particular episode and whether or not we should even include this episode and why and where it would go and all of those sorts of things. So you guys make sure you check that out. I'm curious. Well, I can't. I'm going to look over to the left and take a drink because I can't do it. But Matt, would you like to know what we're watching next week? That would be useful. All right. Well, we're going to jump back over to Voyager because we are doing these in air date order, which is a very interesting way to do this, by the way. And next week is going to be a two-parter, Matt.
but it's not an official two-parter. Okay. This is one of those where I'm taking two episodes that are loosely related and I'm smushing them together. But I believe if memory serves, they're actually back-to-back episodes in Voyager. Okay. Matt, if you'll remember the last time on Voyager, we did an episode called Fair Trade with Neelix where they entered a place called the Necrit Expanse. This big, huge thing. Well, these next two episodes deal with what happens in the Necrit Expanse. Okay. And there's some stuff that happens that we're going to want to talk about. We want to talk about both of them.
They're mostly independent episodes from each other though. I will let you know. All right. So just, just be ready for that. But basically we need to get you through the expanse and, um, smushing these together was actually Phil's idea. The guy that did the trading course episode for Voyager season three. And I'm going to stick with what he recommended. Cause I like, I like smushing these two together for a weird reason, which we'll talk about it. But the name of those two episodes are called blood fever and unity. And I have no extra viewing episodes to give you on deep space nine. So Matt, that's going to do it for us this week here at be me up a star Trek podcast. Hey guys out there. We'd like to know your thoughts on this episode. What would you have done? Would you go crazy for the greater good? Would you become the villain?
Write to us and let us know. BeameUpPod at gmail.com or head over to BeameUpPod.com for more ways to contact us. Matt, how can the folks out there contact you? You can get a hold of me personally on Instagram or Twitter at AsAMatterOfMatt. And if you guys want to get in touch with me, you can find me at BrentAllenLive across all the social medias. I'd love to connect with you there as well, too. Until next time, folks, live long and prosper.