You can't just adjust for inflation like that. Prices have fallen drastically with advances in computing technology.
The Commodore 64 cost $595, which is around $1350 if you adjust for inflation. The XBox 360 costs about $300. And even if you don't adjust for inflation, the C64 still cost more.
The consoles are cheaper, so why aren't the games?
Yeah, I played 4.0. Never had the extension, but I do remember that its "high fidelity" mode was pretty sensitive. Just a touch on the joystick sent you into barrel rolls.
I did wish the documentation had listed all of the hotkey combinations needed to send commands to your wingmen on missions, though.
No doubt, but you can at least turn down the realism in that:
As with Black Shark a number of gameplay options provide the player with the possibility to customize the difficulty to their needs with the possibilities ranging from arcade settings to high realism simulator.
It sounds like only an actual fighter pilot would likely be very good at it. Unless it has an extremely simplified mode for beginners and non-pilots, it's probably far too complex for your average flight sim gaming fan.
A while back I added the hours for a business near where I live (their schedule is a little bit odd - they're only open Wednesday-Saturday). And you've always been able to report a problem with the map, as long as I can remember (although I don't think in some countries it allows that).
There are more low-hanging fruit for security holes, such as all the unpatched Windows XP machines at the nurses stations.
I'd presume that those aren't directly visible to the outside world. They only get traffic from outside your network when they explicitly request it, and then the routers open a temporary tunnel through the firewall to allow the connection to be made.
How is giving the IT tech a non-root account onto my OpenBSD machine going to work - is he really going to know how to probe it from the command line?
That I can't answer. I have no idea. I'd certainly hope that he knows what he's doing.
Truth be told - my suspicion was that he just wants to learn how I did it, so he can implement it for other depts and look the hero
Why - do you want to volunteer to build servers for other departments and maintain them? I doubt it. That's sort of his job. Let him. Sure, it'd be nice if he gave you some due credit, but in any event your department will know and your immediate superior should know, and those are about all the accolades that should really matter.
Lastly - your point about when I leave - please leave that to some other post/question - its off-point. If I left, my colleagues would know better than to expect IT to take over the server of Dr "Dorian".
It's not just who maintains it - it's what happens to it. Do you take it with you, since you paid for it, or does it stay there? If it doesn't officially belong to the hospital, they're relying on your good faith to leave it (and to have someone else trained enough to maintain it in your stead). And that isn't a personal thing... they may trust you, but if they get into the habit of making exceptions for people, sooner or later someone will leave on a sour note and decide to take equipment they'd donated with them. Probably not you - but sooner or later it'd happen. It'd be all-around best to just make it official that the equipment belongs to the hospital, if they're going to be using it. If that means you want to be reimbursed, ask to be reimbursed. If not, ask them to provide you with a receipt showing that you donated it and its value (and you might be able to get a tax deduction). They'll probably want you to continue to maintain it, but it shouldn't belong to you.
Because 99% of the time, expert-sexchange just blatantly copied the question and answer from another website, and they try to hide the answer to get you to pay to register to see it. When someone wants me to pay to get something that I could get for free elsewhere, my basic reaction is "no, fuck you, you greedy bastard."
Sort of like the MLB wants me to pay to listen to live baseball games online while they're being broadcast live on free AM radio... and I can't even go to the AM radio station's website and listen to their live "on-air" streaming audio. No, fuck you, you greedy bastards... if I wanted to hear them that badly I'd go buy a cheap portable AM radio - it'd be cheaper and last longer than a subscription to your website. I only care to listen to one team's games anyway. As an added bonus, the radio wouldn't consume available bandwidth on my internet connection.
It is not a matter of patient information getting out through the calendar itself. You'll have to rely to a certain extent on the users not to leak sensitive information, same as you rely on them not to write sensitive patient information on sticky notes and accidentally drop them in the parking lot.
Suppose you are 100% certain that the information stored in your calendar is not sensitive (e.g. "May 7-8: on-call Dr X"). So if you had to give some random guy physical access to that server, where would you want the server to be? Outside the hospital's network, obviously. Sure, your calendar is compromised, but at least then the rest of the network isn't, and the attacker hasn't gained a doorway into your network. For all you know there could be an unpatched vulnerability in whatever server you're running that can be exploited to give an attacker root, and then the attacker might as well have physical access to the server.
If it's theoretically possible that someone with a thumb-drive and physical access to your server could access files stored elsewhere on the network and compromise private patient data, then the IT department should take a very dim view of the request to open a port from the outside world into the network to your server until they're very certain that the server can't be exploited through that port. It's that simple.
Not to mention the fact that the hospital shouldn't be relying on equipment that is owned by one of the employees. If the employee leaves and takes the equipment, they're left in the lurch to get something else to replace it. Sure, you don't think it will happen, but ignore that possibility and sooner or later it will bite you.
However since you're just a software dev and not an IT admin you probably don't realize that any device attached to the network is a potential gateway through which someone could access the "calendar filled with patient info" that you thought only the employees could access. Especially a device with open ports through the firewall...
Rather, he said he needed IT to open a connection through the firewall, implying to me that this server is on the other side of the firewall; aka not on the network.
No, that would make no sense whatsoever. If you claim that you need a port opened, you clearly have something inside the network that listens on that port.
Quit trying to do IT's job for them. If you want a server for an iPhone-compatible calendar tool, the IT department should be the ones building and administrating the server.
I'm surprised they didn't disable the network port as soon as you told them you had an unauthorized server on the network.
They should not lose their account or have any obvious indication that the account's ability to report has been revoked, because that's just telling them to create another account. The report interface should still appear to work normally even if the user's "credibility" multiplier is zero.
When he said "locking" he didn't mean locking the group or its discussion board, he meant "locking" the Report feature. It'll still appear to work, of course - you can still "report" the group - but unbeknownst to you, your report goes straight to/dev/null and your reporting credibility actually gets automatically decreased.
DING DING DING! We have a winner! Despite your attempt to put disdain on the claim that Windows is broken, you managed to exactly state the problem.
You make it sound almost like it was an accident. And I wasn't attempting to "put disdain on the claim that Windows is broken", only pointing out the deficiencies that some people might care about but which I happen to not find to be deal-breakers.
Slashdot Mirror
When they're comparing graphene to steel, they always mean tensile strength. Hope this helps.
Also, this may be ten times stronger than steel, but it is still carbon, which makes it ten times more combustible than steel as well.
Sort of like diamonds are ten times more combustible than steel wool.
I don't think it's quite that simple...
All I need do is point to Unreal Tournament III... After that, any $60 title from them is a hard sell.
I'm not saying it's worth $60, but I'd definitely say it's totally incomparable to a $1 game, which was all Draaglom was suggesting.
You can't just adjust for inflation like that. Prices have fallen drastically with advances in computing technology.
The Commodore 64 cost $595, which is around $1350 if you adjust for inflation. The XBox 360 costs about $300. And even if you don't adjust for inflation, the C64 still cost more.
The consoles are cheaper, so why aren't the games?
Your $60 game should be incomparable to a $1 game, in terms of both gameplay and technology. If it's not, you are Doing It Wrong.
I think that's what they meant when they said "a $60 game that's really worth it".
Exactly my point. The simulator is a trainer, but TFS was treating it like a toy.
Yeah, I played 4.0. Never had the extension, but I do remember that its "high fidelity" mode was pretty sensitive. Just a touch on the joystick sent you into barrel rolls.
I did wish the documentation had listed all of the hotkey combinations needed to send commands to your wingmen on missions, though.
I'm aware. I didn't say "average gamer". And there's still such a thing as too realistic.
No doubt, but you can at least turn down the realism in that:
As with Black Shark a number of gameplay options provide the player with the possibility to customize the difficulty to their needs with the possibilities ranging from arcade settings to high realism simulator.
Very cool - thanks. Although those do rather reinforce my point.
It sounds like only an actual fighter pilot would likely be very good at it. Unless it has an extremely simplified mode for beginners and non-pilots, it's probably far too complex for your average flight sim gaming fan.
tl;dr: It's a training tool, not a game.
If you got fired you aren't eligible for unemployment benefits.
The ends don't justify the means.
A while back I added the hours for a business near where I live (their schedule is a little bit odd - they're only open Wednesday-Saturday). And you've always been able to report a problem with the map, as long as I can remember (although I don't think in some countries it allows that).
There are more low-hanging fruit for security holes, such as all the unpatched Windows XP machines at the nurses stations.
I'd presume that those aren't directly visible to the outside world. They only get traffic from outside your network when they explicitly request it, and then the routers open a temporary tunnel through the firewall to allow the connection to be made.
How is giving the IT tech a non-root account onto my OpenBSD machine going to work - is he really going to know how to probe it from the command line?
That I can't answer. I have no idea. I'd certainly hope that he knows what he's doing.
Truth be told - my suspicion was that he just wants to learn how I did it, so he can implement it for other depts and look the hero
Why - do you want to volunteer to build servers for other departments and maintain them? I doubt it. That's sort of his job. Let him. Sure, it'd be nice if he gave you some due credit, but in any event your department will know and your immediate superior should know, and those are about all the accolades that should really matter.
Lastly - your point about when I leave - please leave that to some other post/question - its off-point. If I left, my colleagues would know better than to expect IT to take over the server of Dr "Dorian".
It's not just who maintains it - it's what happens to it. Do you take it with you, since you paid for it, or does it stay there? If it doesn't officially belong to the hospital, they're relying on your good faith to leave it (and to have someone else trained enough to maintain it in your stead). And that isn't a personal thing... they may trust you, but if they get into the habit of making exceptions for people, sooner or later someone will leave on a sour note and decide to take equipment they'd donated with them. Probably not you - but sooner or later it'd happen. It'd be all-around best to just make it official that the equipment belongs to the hospital, if they're going to be using it. If that means you want to be reimbursed, ask to be reimbursed. If not, ask them to provide you with a receipt showing that you donated it and its value (and you might be able to get a tax deduction). They'll probably want you to continue to maintain it, but it shouldn't belong to you.
Because 99% of the time, expert-sexchange just blatantly copied the question and answer from another website, and they try to hide the answer to get you to pay to register to see it. When someone wants me to pay to get something that I could get for free elsewhere, my basic reaction is "no, fuck you, you greedy bastard."
Sort of like the MLB wants me to pay to listen to live baseball games online while they're being broadcast live on free AM radio... and I can't even go to the AM radio station's website and listen to their live "on-air" streaming audio. No, fuck you, you greedy bastards... if I wanted to hear them that badly I'd go buy a cheap portable AM radio - it'd be cheaper and last longer than a subscription to your website. I only care to listen to one team's games anyway. As an added bonus, the radio wouldn't consume available bandwidth on my internet connection.
It is not a matter of patient information getting out through the calendar itself. You'll have to rely to a certain extent on the users not to leak sensitive information, same as you rely on them not to write sensitive patient information on sticky notes and accidentally drop them in the parking lot.
Suppose you are 100% certain that the information stored in your calendar is not sensitive (e.g. "May 7-8: on-call Dr X"). So if you had to give some random guy physical access to that server, where would you want the server to be? Outside the hospital's network, obviously. Sure, your calendar is compromised, but at least then the rest of the network isn't, and the attacker hasn't gained a doorway into your network. For all you know there could be an unpatched vulnerability in whatever server you're running that can be exploited to give an attacker root, and then the attacker might as well have physical access to the server.
If it's theoretically possible that someone with a thumb-drive and physical access to your server could access files stored elsewhere on the network and compromise private patient data, then the IT department should take a very dim view of the request to open a port from the outside world into the network to your server until they're very certain that the server can't be exploited through that port. It's that simple.
Not to mention the fact that the hospital shouldn't be relying on equipment that is owned by one of the employees. If the employee leaves and takes the equipment, they're left in the lurch to get something else to replace it. Sure, you don't think it will happen, but ignore that possibility and sooner or later it will bite you.
However since you're just a software dev and not an IT admin you probably don't realize that any device attached to the network is a potential gateway through which someone could access the "calendar filled with patient info" that you thought only the employees could access. Especially a device with open ports through the firewall...
In that case he should just move it to port 80 and be done with it. No, it's obviously inside the network.
Rather, he said he needed IT to open a connection through the firewall, implying to me that this server is on the other side of the firewall; aka not on the network.
No, that would make no sense whatsoever. If you claim that you need a port opened, you clearly have something inside the network that listens on that port.
5. ???
6. Get fired.
Seriously, I think you forgot those steps. What you wrote sounds exactly like a handbook on how to get fired.
Quit trying to do IT's job for them. If you want a server for an iPhone-compatible calendar tool, the IT department should be the ones building and administrating the server.
I'm surprised they didn't disable the network port as soon as you told them you had an unauthorized server on the network.
They should not lose their account or have any obvious indication that the account's ability to report has been revoked, because that's just telling them to create another account. The report interface should still appear to work normally even if the user's "credibility" multiplier is zero.
When he said "locking" he didn't mean locking the group or its discussion board, he meant "locking" the Report feature. It'll still appear to work, of course - you can still "report" the group - but unbeknownst to you, your report goes straight to /dev/null and your reporting credibility actually gets automatically decreased.
DING DING DING! We have a winner! Despite your attempt to put disdain on the claim that Windows is broken, you managed to exactly state the problem.
You make it sound almost like it was an accident. And I wasn't attempting to "put disdain on the claim that Windows is broken", only pointing out the deficiencies that some people might care about but which I happen to not find to be deal-breakers.