Mahone

There are always going to be times when you need to fix something critically, and a professional, or the DIY relative that everyone has just isn't immediately available. It's only then that you realise how dependent on others you really are. Don't under estimate how useful the knowledge gained by at least attempting DIY can be. Not all the knowledge you gain has to serve career related purposes :)

My parents both refuse to go down the DIY method. One is merely lazy, the other is terrified of the potential risks if its not something she has already been shown how to do. Throughout my childhood, I was bought up to have the same fear of DIY as the latter parent and as a result just assumed that things really were too complex and beyond my capabilities - I was never given the opportunity to try things for myself. Then the internet came along in my early teenage years, and I had immediate access to one of the largest knowledge bases ever to exist. I started off teaching myself about computers, networks, and IT infrastructure merely out of curiosity (one of the first questions I ever typed into a search engine was "how does the internet work"), and found that DIY IT is actually much easier to understand and much easier to work on than it had been made out to be. I then used the same thought process in others areas. If I wasn't sure how to do something, I spent a few minutes/hours researching and then put that knowledge I had gained into practise - I found that 95% of things that we'd previously called professionals in to do were actually really easy to resolve once the research had been put in. Now, unless illegal, extremely dangerous or the potential costs of repairs is more than we can afford, I always attempt the DIY route before calling a professional - I much prefer to be independent. If I don't take the risk, I'll never gain that knowledge. If I break it, I'll know not to try that method again and then find out what I should have done from the professional as he repairs my mess.

As of late, not a lot. Been too busy with work, moving and everything else. But pretending I still have loads of time, these are my main hobbies: - Geocaching. Some on here will know what it is, but for those who don't: Geocaching - Wikipedia, the free encyclopedia. I've been doing it since 2004, found caches all over the UK and more recently started in the states. Once we move permanently I plan on setting up a few caches across Florida. - Hiking. This is what piqued my interest in geocaching initially. - Travelling. Despite not having enough time to do this, other than back and forth between North America and Europe, I've got plans to visit countries in at least every continent within the next five years. - My field of work. Thankfully I'm one of the few people I know that actually enjoys what I do for a living - at least for the most part .

As a British speaker, I would understand the phrase to include hints that the pregnancy was unintentional. This isn't the same as ducking out of responsibility, but merely implies that they weren't actively trying to have another child at the time it occurred I don't believe all cases of accidental pregnancy are due to being irresponsible.

It shouldn't be possible. Not for answering the call, at least, so I suspect there has been some confusion somewhere along the line. Calling back is a different kettle of fish entirely, and goes without saying that you don't call back international or premium rate numbers just because they called you. The only exception I can think of for those living in the US in the normal charge that you'd get for answering any international (or local) call, but that cost goes entirely to your local phone operators and not the caller, so it's doubtful that was part of the original plan that the scammers behind this conceived. Either way, the phone operators of the victims of this scam and those like it have a lot to answer for. They should have dedicated departments for dealing with scams like this, monitoring traffic passing through their exchanges and looking for, and blocking any unusual traffic. Thousands of calls within a short period of time to residents in Utah from Grenada should have been flagged quickly, investigated and blocked. It certainly shouldn't require the local media outlets to spread warning of this scam in order for it to be stopped.

We also get this in IT - teenagers and script kiddies that know enough to be dangerous advertising themselves as engineers and technicians. But then that's how I started out as well, and moved onwards from there.

IT Systems Manager for a college. Basically just look after all of their network infrastructure and IT kit to ensure it remains up and running.

You might want to consider how you're going to get offsite backups before spending $$$ on colocation. Maybe an old server with FreeNAS installed, located somewhere in your office and connected to the live server via VPN? This FreeNAS server can hold regular automated encrypted backup copies of your data. That said, how big are your backups? Will this cost you a lot in bandwidth once your live server is colocated? As for getting run down - make a disaster recovery document for the business IT infrastructure - these documents are supposed to provide detailed technical information, including passwords and encryption keys, explaining how everything was set up, and how to recover from any feasible disaster scenario. That way, in the event of both the server and you dying on the same day, the company can hire a technician for a few hours to go over your DR document and get everything back up and running again. Obviously this document needs to be kept in a secure fire proof safe, as it's highly confidential. As long as you get a reasonable warranty on a refurb, I don't see any reason not to use one if the saving is enough to make it worth it.

RDP in and of itself doesn't take up much bandwidth. What about backups? How are they being performed currently? It's definitely worth getting a server with basic redundancy built in as well such as a RAID card and dual PSU. Reduces like likelyhood of you having to make emergency visits at 3am to replace failed components!

With colocation, you can theoretically have anything you like on your server. The same is also possible with a dedicated server, although some companies may restrict exactly what it can be used for. It's certainly not only for webservers by any means. That said, I don't know exactly what is currently on your server or how the applications have been set up. So: - Bandwidth is something you'll need to take into consideration - if the server is currently on the same physical LAN as all the clients, will the bandwidth be enough to serve the clients when its running over the internet? - Application settings. If server is currently on the same LAN as the clients, does the application allow clients to connect to a public IP as opposed to a private IP? If not, will VPN be required to work around this? - Encryption. If you're not going to use VPN, what is going to encrypt the data between the server and client? Does the application do it? - Firewall. Are you expected to provide one for your own server, or do they provide one for you? If the latter, how long does it take to get them to modify these firewall settings when you need them to? - Billing: Many datacentres charge for the amount of RU's the server takes up. If you can use a smaller server, it'll probably be cheaper. - Physical access to the server. What happens in the event of hardware or OS failure? How quickly are you allowed to get access to it to repair it? - Backups. How do these currently work? Where are they backing up to? Will this still be feasible when the server is moved, with the changes in bandwidth? You certainly don't want them stored on the same system as the live data. You mention that you are moving the server for security reasons, does that mean the system the backups are located on would have to be moved to a secure datacentre also?

I live(d) in the UK and my wife lives in Florida. Currently we are both resident in the UK and have been for 1.5 years, but moving to Florida as soon as USCIS get their act together. We made a long distance relationship work for two years, and had been talking to each other regularly for another couple of years before that. I'm glad we did and I wouldn't have it any other way. That said: - Be prepared for the extremely expensive dating period. International flights in and out of the US can easily go up to $1000 and beyond per return flight, and depending on the area and length of time, hotels can cost you $500 per trip, plus all the additional expenses that are too numerous to mention. - Once you're married, you'll get the standard problems that come with marriage plus an additional set of problems such as one of you having to relocate to the others country and the massive set of visa related and other issues that come with that. We celebrated our second anniversary this month, and we're still battling visa problems - they are much more complex than many believe. Most married couples have long had their honeymoon by now - we haven't been able to because of the sheer time and expenses taken up by the visa application process, plus simply not knowing how much longer its going to take and where we'll be this time next month, let alone next year. If you are both willing to face all of these problems, I say go for it.

It's always odd watching buses go past, with destination "California". Especially to my American wife who just rolls her eyes each time she sees them

Ditto! Think mine was the only one no-one laughed at! Or it just wasn't that funny

A quick five minute car journey from where I currently live, and I'd be in Broadway. A 15 minute journey, and I'd be in California. 20 minutes, and I'd be in Hollywood. The city I live in is twinned with Chicago.

:).

I'd tell you a UDP joke, but you might not get it.

Baked beans. I can't eat off-brand baked beans, they have to be Heinz or HP. Although I can cope with margarine because I essentially grew up with it, butter winds hands down if there is a choice. Real Cadbury chocolate. The Hershey made Cadbury items that you get in the states just taste cheap. Although expensive, I'll get the Cadbury items imported from the UK instead.

A few years ago, I was walking through town with my brother in the early hours in a Saturday morning. A male and female were arguing viciously outside of a pub, both clearly drunk. He became violent quite quickly, was twisting her arm, pulling her hair etc. So I stopped and started walking towards him, although I was at least 60 seconds away from him at this point and he couldn't see me. As I approached them, he walked off at a fast pace, leaving her alone. At that point, she could have walked off in the opposite direction, gone back into the pub, called a friend to come and pick her up or choose any number of alternative and safe scenarios. But she didn't, she ran after him yelling and screaming, hitting him with her handbag and started to attack him. So I walked off. I'm not going to put my life in danger to protect someone who had their chance to get away, but for whatever stupid reason decided not to. As it turns out, it wasn't a bad decision on my part as the police arrived moments later and found a knife tucked into his jacket.

I've done exactly this before, not because I wasn't comfortable speaking to the relevant person, but because I genuinely believed it was important for everyone. Although I know exactly who made the error on this occasion, I believed that this was just sheer circumstance and any of them might have made the same mistake in the same position. It seemed unfair to single the one person out in this instance.

In my experience of Africa, there are a great deal of Christians there too, possibly even more so than any Islamic religion.

I'm half way through my degree and during my first module my tutor was talking about referencing and obviously Wikipedia came up. Thankfully he said that Wikipedia is a positive resource, but only to find alternative references, which should always be specified in a good article - exactly the opinion that I've always held.

There used to be more than one popular LDS chat server back in the late 1990's/early 2000's. I was a moderator for the other one that no longer exists during my college days. Banned words wouldn't automatically ban the user, just alert all moderators/operators/administrators that a banned word had been used by this user. However it would't tell the moderators exactly which word had been used, or which channel/p2p chat window it was used in. So, if you're busy, it can be quite difficult to determine exactly what happened and what word was used, which might explain why the moderator just banned regardless - I'd seen my fellow mods do this loads of times. That said, the still existing chat server uses entirely different software now whereas previously they were both using the chatspace server software, so I don't know how its currently set up.

In this area at least, the church doesn't really invest highly in local technology. The church is known for its use of technology, but that's primarily at the headquarters and select locations. The photocopier in our clerk office is an inkjet, probably the cheapest model the bishop from two generations ago could find.

Luckily, I married a night owl - my wife would happily sleep in each morning if she didn't have responsibilities to deal with, just like myself. I don't think I could have married a morning person - my other half being up at the crack of dawn each morning would drive me insane.

I haven't even implied that the church has intended to hide their history. My only claim was that I wasn't surprised that the subject hasn't just "come up" in conversation, despite the OP being a member of the church for a lengthy period of time. You're referring to something entirely unrelated to my post, so I'm unsure as to why I was quoted?