And what about those users who are using proxies, or VPNs? The problem is, there is no way to guarantee the correct time is shown if you can't trust the clients clock. And again, you are glossing over the fact, that those complaining are those who doesn't get why the fancy blinking lights aren't all knowing and just works [tm]
Do tell how they do that - getting the server clock is trivial, making sure your JS is keeping time accurate between requests is pretty much impossible.
Figuring out what time to show is bloody hard, especially since the people complaining are those who in the first go didn't manage to set up their computer correctly.
Oh, and a script pulling the time at intervals from some server(s) is going to be expensive; remember the massive amount of users and data the beeb handles.
Except unions and strikes only worked when you could force a plant to shut down.
These days, you can hire contractors to do most work remotely, they don't need to force their way through the barricades to start up heavy machinery.
I used to believe in unions, I live in Denmark where we have the famous Danish Model for unions; it has however, been shown by the government in the last couple of months, that unions are absolutely worthless and workers can be treated as slaves.
If you have a job, hope to god you get to keep it, because it gets harder and harder to get a new one.
He is more than likely getting disconnected due to the fact he is running services; not because of his data usage. Most private ISP contracts prohibits business usage of the connection.
The thing about hemp is it is bloody robust, you don't need GMO plants, you don't need nasty chemicals to make them grow - Earth, water and some sun and you are good to go.
Making stuff out of hemp is a very eco friendly thing to do. (And you don't need to use the smoke-able hemp)
To be honest I think she deserves to be expelled and while felony charge might be a bit harsh, it damned well should be illegal and carry punishment. Those bombs are fucking dangerous - when they go off, you have acid going in all directions - yeah, you might not kill people, but it will take your eyes out...
Really? The SIP servers I'm running are purely done in software; but after posting that I realized that they are targeting american companies, not European, so guess it's a non issue (for most people).
People are going to get robbed, there will always be someone trying to get rich easy.
If a robber expects you to be armed, he will step up his attack, so if he expects you to be unarmed, he will most likely come at you with a knife, if he expects you to carry a knife, he will come at you with a gun. If he expects you to carry a gun, he will *SHOOT* you, then take your gun and money.
Why the heck are you complaining? It's the non LTS that is getting cut in half, if you don't want to upgrade to latest and greatest, stick with LTS and you will be fine for a long long time!
Just put the stuff in memory based databases and/or steal the partition setup from Tails; that thing will wipe data faster than you can say "shit didn't mean to do that".
If you think debugging in the console has anything to do with debugging, you are missing out.
Connecting a debugger to python and stepping through your code is by far the smartest way to figure out what the freck is going on - no printing xyz all the time to see what happens. You just put a break point and you will have all the juicy goods, including stuff you didn't think of looking at.
Personally I use IntelliJ with the Python plugin (essentially PyCharm), it rocks.
Well, to make it a million to one chance he'd need to have one pilot blindfolded while a stewardess dances a waltz down the center, with the airplane going directly through a thunderstorm.
Actually that might not be enough - some smartphones stay on when powered off, which is why you are told to put your phone in airplane mode *before* turning it off.
Same goes for the aGPS, it will usually try to keep track of where it is for acquiring location faster, even when "off".
This is a major security issue and it affects *ALL* versions of postgres. Locking it down while updates are being created seems the right way to do it to me...
You are assuming it is a new problem, the approach they selected tells me they have found a *MAJOR* issue in several versions of PostgreSQL; that means it's old code.
They even say, keep an eye on this next release, because you (users) need to apply it at once - this isn't something that only affect latest build.
But a quick search for metasploit should get you going, perhaps add a Nessus scan and go watch some Def Con presentations on SQL injection and penetration testing http://www.youtube.com/user/ChRiStIaAn008 is a good place to start.
Slashdot Mirror
Very nice suggestion, definitely going to try it out.
And what about those users who are using proxies, or VPNs? The problem is, there is no way to guarantee the correct time is shown if you can't trust the clients clock. And again, you are glossing over the fact, that those complaining are those who doesn't get why the fancy blinking lights aren't all knowing and just works [tm]
Really?
Do tell how they do that - getting the server clock is trivial, making sure your JS is keeping time accurate between requests is pretty much impossible.
Figuring out what time to show is bloody hard, especially since the people complaining are those who in the first go didn't manage to set up their computer correctly.
Oh, and a script pulling the time at intervals from some server(s) is going to be expensive; remember the massive amount of users and data the beeb handles.
I think they did the right thing.
Just make sure you disable Excel
http://www.youtube.com/watch?v=qk_va2LLox4
(Added bonus, those guys are friggin hilarious, check out their other talks).
Except unions and strikes only worked when you could force a plant to shut down.
These days, you can hire contractors to do most work remotely, they don't need to force their way through the barricades to start up heavy machinery.
I used to believe in unions, I live in Denmark where we have the famous Danish Model for unions; it has however, been shown by the government in the last couple of months, that unions are absolutely worthless and workers can be treated as slaves.
If you have a job, hope to god you get to keep it, because it gets harder and harder to get a new one.
He is more than likely getting disconnected due to the fact he is running services; not because of his data usage. Most private ISP contracts prohibits business usage of the connection.
Magic, it's done by magic.
Except no one actually believed in the flat earth thing, it's a myth that we thought the world was flat...
The thing about hemp is it is bloody robust, you don't need GMO plants, you don't need nasty chemicals to make them grow - Earth, water and some sun and you are good to go.
Making stuff out of hemp is a very eco friendly thing to do. (And you don't need to use the smoke-able hemp)
Erm, Steve Jobs died of cancer; a cancer that might very well have been treatable, had he not been absolutely mental and gone for "natural" cure.
Not only do you need funding, you also need someone who believes in science (like Bill Gates, whom by the way does a heck of a lot for research).
Nope, still with the missing stuff there it doesn't make sense :-)
But that might just be because I'm slightly blind when it comes to mathematical proofs.
(Kinda like Zaphods sunglasses, but build into the brain, blacking out when stuff gets complicated)
To be honest I think she deserves to be expelled and while felony charge might be a bit harsh, it damned well should be illegal and carry punishment. Those bombs are fucking dangerous - when they go off, you have acid going in all directions - yeah, you might not kill people, but it will take your eyes out...
Really? The SIP servers I'm running are purely done in software; but after posting that I realized that they are targeting american companies, not European, so guess it's a non issue (for most people).
Try pointing out that the UK is part of EU and so far, software patents aren't valid?
Well, what then, when several companies have the same name? Just the US ones getting their name and everyone else has to change theirs or?
You got it the wrong way around.
People are going to get robbed, there will always be someone trying to get rich easy.
If a robber expects you to be armed, he will step up his attack, so if he expects you to be unarmed, he will most likely come at you with a knife, if he expects you to carry a knife, he will come at you with a gun. If he expects you to carry a gun, he will *SHOOT* you, then take your gun and money.
Why the heck are you complaining? It's the non LTS that is getting cut in half, if you don't want to upgrade to latest and greatest, stick with LTS and you will be fine for a long long time!
Well don't store data then?
Just put the stuff in memory based databases and/or steal the partition setup from Tails; that thing will wipe data faster than you can say "shit didn't mean to do that".
If you think debugging in the console has anything to do with debugging, you are missing out.
Connecting a debugger to python and stepping through your code is by far the smartest way to figure out what the freck is going on - no printing xyz all the time to see what happens. You just put a break point and you will have all the juicy goods, including stuff you didn't think of looking at.
Personally I use IntelliJ with the Python plugin (essentially PyCharm), it rocks.
Well, to make it a million to one chance he'd need to have one pilot blindfolded while a stewardess dances a waltz down the center, with the airplane going directly through a thunderstorm.
Or against a guy with a tank and an RPG...
Actually that might not be enough - some smartphones stay on when powered off, which is why you are told to put your phone in airplane mode *before* turning it off.
Same goes for the aGPS, it will usually try to keep track of where it is for acquiring location faster, even when "off".
And from Postgres we have:
http://www.postgresql.org/about/news/1454/
This is a major security issue and it affects *ALL* versions of postgres. Locking it down while updates are being created seems the right way to do it to me...
You are assuming it is a new problem, the approach they selected tells me they have found a *MAJOR* issue in several versions of PostgreSQL; that means it's old code.
They even say, keep an eye on this next release, because you (users) need to apply it at once - this isn't something that only affect latest build.
What's the point of "basic" security check?
But a quick search for metasploit should get you going, perhaps add a Nessus scan and go watch some Def Con presentations on SQL injection and penetration testing http://www.youtube.com/user/ChRiStIaAn008 is a good place to start.