Tom Servo

not a good sign... not even 24 hours into his marriage and mike's wife has already bored him to sleep. (mike is a co-worker of mine that just got married)

nothing says 'style' like a banana hammock and a mullet.

tonight on cnn: a special in depth report on the government's latest multi-billion dollar 'water runway' project.

As Tom looked down at Daena in his arms, trying to think of a conversation starter, looked up at the different plants in the arboretum. "There are lots of nice plants in here," he managed to stammer out. Daena looked up excitedly, "Oh yes! There are several species from all sorts of planets in here. I planted several of them, and that is one of my favorite parts of my position as a science officer" she said with a smile. "Here, let me show you around a bit." As she said this, she stood up and took Tom by the hand and started leading him around point out different flowers and small trees. Tom found it quite hard to concentrate on what exactly Daena was saying, but was more fixated on the energy and excitement that she had while she described the plants. As she continued, she began to notice that Tom was not really listening to the words, but just listening to the sound of her voice. She looked up from the plants with her maroon eyes, "What?" she said with a slight smile and tail swishing back and forth. "You are incredible," Tom replied, looking at the beautiful Mithraan, "not two days ago, we were in sickbay, extremely injured, and now you are so full of energy and excitement!" Just as Daena was taking in what was being said, they were interrupted by Lt Cmdr. Marx, "Lt. Servo, could you please report to the security office." Tom and Daena looked at each other, and after a few moments, Tom finally replied, "Yes, sir. On my way." As they gave each other a very caring hug, Daena whispered, "When you get a chance, find me, I want to talk to you more." As Tom was leaving he looked back and gave a friendly wave. He walked to the security office with a bounce in his step, looking forward to their next meeting.

== Personal background == Tom Servo was born in 2355 in the Nicola valley of British Columbia. Growing up with one sister, Julie, 2 years younger than him, he grew up with an interest in various types of firearms and weapons, always looking for excuses to blow things up. Legally of course. At 15, for Father's day, he used a small explosive charge to destroy a rotting barn that his father had been planning on razing for the past year. Just before he turned 18, he read an ad looking for freelance agents, who would be essentially overpriced bodyguards for elitists that travel to or near hostile areas. With the Dominion war getting into full swing, Tom figured he could get top dollar for his services as a knowledgeable weapons person. So as soon as he turned 18, he applied for several agencies, but finally got a position with "K'nagrk's Superior Staffing Services", a slip-shod operation run by a drunken Klingon who seemed to be part Ferengi in his quest for riches, and blatant disregard for the safety of his employees. After three years of close calls, and the war over, clients started to stray and not enough latinum was coming in to stay in the industry. Shortly after turning 21, he joined up with Starfleet, entered the academy with dreams of getting onto the private security detail of a high ranking admiral, but after going through the course, found the prospect of security on a ship, never knowing what might happen on a mission, to be much more appealing. While at the academy, he was recruited by Starfleet Internal Security to be trained in undercover operations within Starfleet. Tom normally serves a normal career, however may be called up at any time to assist with an investigation and assumes an alternate identity. This status is restricted and on a need-to-know basis for the ranks of Captain and higher. While on these missions, he is offically listed as "on training". During his first few months on the Arcadia, Tom became enamored with a crew mate of his, Daena Nouvelle, after a series of bad away missions brought them closer together. == Quick facts == Name: Tom Servo Age: 24 Relations: 1 sister (Julie), mother and father (Rose & Calvin) Race: Human Birthplace: Nicola Valley, British Columbia == Service history == 50705.15 - Posted as an Ensign on USS Arcadia 50712.12 - Promoted to Lieutenant Junior Grade 50803.05 - Promoted to Lieutenant 50903.04 - Promoted to Lieutenant Senior Grade

Added service history, and (semi)-recent promotion to history. Ok ok... so it was like a month ago, and i'm just lazy.

"i wonder what's on this side of the green tires? no time like the present to find out!"

guy scratching his head: "something is not quite right here..." guy with the wand: "yea, your right. but i cant quite put my finger on it."

To> LT CMDR WILL MARX From> ENS TOM SERVO cc> CMDR LO'AMI; LT SAM SEMA'J Subject> EXPLOSION IN STELLAR CARTOGRAPHY (ENCRYPTED) SD Reference> 50709.19 I have compiled a report concerning the explosion in stellar cartography (the exact panel/conduit could not be readily determined, however it appears to be either SC163/38 or SC163/39), and attached is the evidence supporting my findings and conclusions. Based on engineering logs obtained from the computer (appendix A), it appears that in addition to the analysis and subsequent repairs done by Ensigns Slartibartfast and Beeblebrox for the damage done during recent missions, Ensign Gigglethorp was assigned to complete a routine check and make any necessary repairs two weeks prior to the explosion. No further access to the conduits in question were recorded. After looking into the history and service record of all three Ensigns (appendix :D, there appears to be no reason to suspect them of any wrongdoing, or sabotage. Internal sensor logs (appendix C) were also reviewed, and provided the most valuable information. It appears that during Captain Dacotah's encounter with Baran, that there was a surge in the EM spectrum at 872.587MHz at the exact times when Baran appeared and disappeared. In reviewing the internal sensor logs, for the three days prior to Baran's appearance, there was one unexplained burst at that frequency, though not quite as powerful as those that correlate to Baran's unexpected visits. No activity was found from the time that Baran's last visit until I obtained the sensor logs. Although this information, does not implicate Baran, nor does it confirm that Baran was the source of these surges, it does seem to point strongly towards him. Furthermore, if this is linked to the method that Baran transports onto and off of the ship, it does not shed any light as to the technology being used. Damage control teams sent to repair stellar cartography were not instructed that this was an abnormal occurrence and that there would be an investigation launched to determine its cause therefore, minimal readings were obtained by them, and no more than were necessary to conduct the repairs. Scans by these teams are compiled into appendix D. Information collected revealed no known explosive residue, or unknown components. Supplies used to repair the damaged area are consistent with those found in the damaged conduits. Engineering logs did not provide any additional information. Medical scans on Commander Lo'Ami and Lieutenant Nouvelle (appendix E and F) provided no information on what triggered the explosion or what it was composed of. It only showed that the explosion was more of a energy shock than a heat driven one, as there was less burning, and more blunt force trauma. At this time it is impossible to determine an exact source of the explosive material, what it was composed of, or how it was placed in stellar cartography. It should be noted as well, that based on the passive scanning pattern of the Romulan ship in the vicinity at the time of the explosion, an explanation as to how they were able to transport the Commander and Lieutenant at the exact moment could not be determined. Although pure conjecture, it would appear that Baran and the Romulan's were both involved in some way with the explosion and subsequent abduction of Commander Lo'Ami. I would also further recommend that revisions to the process in which repair teams conduct themselves at locations that might be subject to investigation be changed to ensure that a maximum amount of information is obtained in the repair process. Security teams should also be notified and dispatched at the same time as the damage control teams to provide a proper level of containment at the scene, this would of course, be at the discretion of the Chief of Security or their designate. This incident is now no longer under active investigation, but still open, and will be made available to an Board of Inquiry if necessary. No fault has been established, and no cause has been determined. Investigated and reported by: Ens. Tom Servo Assigned by: Lt Cmdr. William Marx, Chief of Security Incident reference number: 947-8766C-94/1 END OF REPORT

i tried logging in when i was at work one night using my treo (blackberry type thing by palm), and the only reason it didnt work was because there was no java interpreter in the browser i was using.

early concepts of the death star certainly showed vader's ego.

after a slow head on collision with an airport terminal, boeing decides to offer dual pilot/co-pilot airbags, with optional curtain side airbags on all new '08 models.

uh... whats that officer? oh... just adding 'speed holes'.

i can just see the headlines now, bugs bunny squished by elmer fudd in an enormous dump truck. so for that vivid visualization, a9 is the winner. for the actual reason it looks like that, here is the reverse angle.

ahh! been on vacation, and didnt even notice i won. sweet. here ya go.

i was wondering if anyone would mention that great episode. i like star trek as much as the next person, but an entire religon built on it, thats probably a little much.

"There is absolutely NO truth that head injuries result from football! YEAH!"

i am tina, the money tree caterpillar, on my left you see my right hand straw girl, she has straw for a brain which explains why she is on the wrong side. together we are the pumpkin mafia. play your cards right, and you could be one of us. capice?

...and next on our tour, we see the actual server space for stsf.net...

now simmer down children...

i've mainly done security, tac and eng. i cant say i remember ever doing anything science-type. so i guess i cant really say that its a bad thing per se, but its not really an area that i'm interested in. security though is where my interest is, and thats where i got to on the arcadia. i like it. as for where to learn to play positions better, i'd have to go with the majority of the comments that are already left, go with what you know, and i'll add, you cant watch enough star trek to learn it too. ;)

you know, that reminds me of this article in the national enquirer where even the tabloid news was so slow that the front pages had a photo of jon benet ramsey, and a little starburst with the caption "the jon-benet murder, day 1437" or something ridiculous like that. i mean seriously, who could possibly care?!??! certainly not front page material anyway. and moreover, after 100 or so days, you dont refer to it in the 'days' term, move on to at least months or years. oy! just had to vent a little there.

although that IS a pretty funny punch line too.

U.S.S. Arcadia Personal Log: Ens. Tom Servo Computer, begin personal log. Well it has certainly been an interesting first couple mission’s; the introduction I received from the security team already on board was on this twisted little planet called Paradisia. I hope the Arcadia will not be going back there anytime soon because we had a little trouble with a local game. Maybe after the diplomatic side of Star Fleet works out the purpose of this game, and how they can keep better tabs on the so called participants by making sure they don’t get hurt or anything we might return. Our next mission, the one we stumbled onto, was to meet up with this Ambassador. The Chief of Security, Lt. Marx, sustains serious injuries as a result of what appears to be a kidnapping of the Admiral. The Admiral was replaced by an android rigged with Novadex explosives, and was booby trapped to detonate in the event of tampering. While the Lt. was recovering in sickbay from his ordeal, Lt. Thoros and I tried to establish who made the explosives and where they came from. All we were able to figure out was that it was a very professional job. After we cleared the shuttle from any further traps and explosives, we retrieved a non-descript black box, which we surmised was some sort of controller for the explosive androids, and brought it to sickbay where the good doctor would try and get anything forensic off of it. As I continued to scan the shuttle, Thoros assumed command of the department, and after a hair-raising trip through an asteroid field, came upon a knock box. Thoros and a poor Ensign transported over only to find themselves in a similar situation that Marx was in. What appeared to be the real Admiral with fading life signs was once again rigged to explode, this time Mr. Thoros tried to make sure the Admiral was ok, and I think that his feelings for helping the wounded rather than self preservation kicked in and unfortunately was injured by doing so. When the bridge brought the knock box onto the ship, Ens. Nouvelle Daena, a very nice Mithraan from the science department, was sent to help out with the analysis of this conundrum. I setup every precaution I could think of, the entire shuttle bay was surrounded by a level 10 force field, we wore blast suits, the bridge had a lock on us, and I fully intended to take as much time as necessary to do the scans and disarm any bombs. I refuse to be the 5th person from security to be sent to sickbay because of injuries sustained on the job, and while not as glamorous, it would certainly be better if it resulted from some sort of holodeck accident. In any case, we both scanned the outer surface of the knock box, Daena looking for any scientific evidence of where it came from, and me looking for signs of traps or explosives. With none found, we opened the door, and we heard this high pitched whine coming from inside, Daena looked much more annoyed by it than I was. She knew almost immediately where it was coming from, and we scanned that location. (As a little side note, over the last few days, I have spent more time scanning and analyzing that I ever thought I would have to.) Daena found what turned out to be a thermal sensor on the surface of the compartment the noise was coming from, possibly activated by Thoros and the other Ensign. I scanned for traps and came across a micro-switch hooked into the panel and bypassed it. At the time, all I was on a brief little personal high thinking that I had outsmarted whoever was behind this, but was about to be proven wrong. After I bypassed the switch, I opened the panel, and in about the 3 seconds it took me to see it, process in my brain what it was, and react, it exploded. In the panel there was a Romulan disruptor set to overload, and I had missed the second micro-switch that triggered the overload when the panel was opened. On the plus side, we were able to get out of the direct blast, and any other potential injuries were prevented by the blast suits. I must say, the reaction that Ops has when an explosion occurs on the ship is incredible, I was barely able to remember where I was when I heard Lt. Meriva ask what happened. I gathered my senses, told him we were ok, and explained what happened. My ego was certainly cut down for the rest of the check. Every other trap that I came across, I scanned and rescanned all around it for redundant triggers. As luck would have it, the panel with the disruptor was the only time there was more than one. To keep things moving along, and partially so we could get out of this death box as quickly as possible, the remainder of the time was spent finding and disabling everything we came across. The remaining two androids each had 10 grams of Novadex setup to make short work of anyone that messed around with them, removing the explosive from them was probably the longest and most nerve racking 20 minutes I have ever experienced. After Daena took some scans and an extremely small sample of the plastic-like substance, for future reference if necessary, the remainder was detonated a safe distance from the ship. The androids were verified safe and one of them was given to Engineering for their analysis, while the other to sickbay for their take on it. With the knock box clear, and something intact for two other departments to work on, Daena and I left the shuttle bay to calm down and relax for a bit. She certainly is a lot tougher than she looks, and I defiantly owe her at least a lunch after letting a disruptor overload not 10 feet from her. With all the danger the security team on this ship encounters, maybe I should look for a transfer. It seems like one can move up the ladder pretty quickly though -- maybe I will stay. Computer, end log, and notify me when 10 minutes has elapsed, I need a power nap.

ah... thats what it is!