Ever read the moderation FAQ? Just cause you dislike him or his ideas doesn't give you a right to push an agenda. This is a fair comment - how do we deal with languages we don't know and can't even type?
A brick would be you turn it on, and it flashes the screen in bright colors hysterically all the while playing the modem version of Jimi Hendrix.. well, Ok, it just turns back off usually.
No - there's no real issue there other than something is mysteriously blocking the phone from recognizing the SIM card. I'm sure it'll be fixable somehow.
Are the core Vista kernel developers any better? No, Microsoft takes EVERY stupid idea VERY seriously! From my experience writing windows kernel drivers - I can say with a straight face that each and every one of those idiot ideas has been implemented directly into the NT kernel.
Just pure speculation on my part - but I believe you need a "common carrier" of some sort of wave to setup entanglement. It makes sense to build this into a chip so that you can alter the setup at run time.
I suppose eBay is busy cleaning up their "bad reputation." Flame bait? Troll! Yeah right...
I've been in their shoes - writing code and managing millions of credit cards on a web-facing travel application. I have code certified to FIPS 140.2 - I know what it takes to get there.
If they fail customer safety standards they will get my ridicule, as a customer and as an industry colleague.
I have NO problem calling inadequate, dangerous, and reckless companies "stupid idiots." Millions of people TRUST eBay with credit worth billions of dollars - and they have repeatedly failed.
Being called a stupid idiot should be the LEAST of their worries.
I've seen too many incidents of hackers gaining access into the eBay admin systems - forum takeovers, listing problems, and such.
Is it so hard to audit your network, code, and such? Well, yes - it takes WORK. Not only is it required for Sabanes-Oaxly, but I would think that risking a huge business like this would be enough of a motivator.
I'd love to say I'm special, as I am a security engineer, but come on! There's thousands of geeks with the background to clean this up. Get Crackin!
Thirdly, locks are pointless if they are easily circumvented by anyone with a web browser. No they're not - locks are a simple way to get you to renew your contract - on a phone you're already paid for. Locks are meaningless otherwise - as you've either purchased the phone outright (pay as you go) or are under a contractual obligation and will end up paying for it in the end.
We can't have it both ways - either we need a law which states that all users have a right to be unlocked after their contract is over (paid off or expired) - or we can go along with this hokey hacker versus network approach with bricked phones.
Well, if Apple had a standard way to unlock the phone á la codes and such then this wouldn't have been a problem. They over-engineered the SIM lock software mechanism - knowing that people have the ability and right to unlock their phone.
This is a standard issue in the phone world - and I find it hard to understand why EVERY other phone on the market can be unlocked without bricking the phone.
I always unlock my phones, or buy unlocked ones - I want to have the ability to walk away from a carrier if they do't treat me right and keep my very expensive equipment.
No, this is a threat along the lines of "This is a very nice store you've got Mr. Donatello - it would be a shame to see it burned down, eh?"
You keep speaking of a Model Release - but what matters here is intent. Virgin was perfectly within the rights given to utilize the photo - it was assigned a CC license.
The CC license assumes that the person completely owns the image rights - and that person was the photographer.
But the photographer was ignorant of the law concerning peoples rights to their own likeness. And since the photographer expected and received nothing in compensation (a key point in US contract law) I really doubt there's anything to be recovered here other than a C&D or a libel claim.
If anything - Virgin may "settle" for a token amount. And I'm betting that is the point of the case in totality.
Every time the government limits freedom, there must be an underlying principle of justice - it can not be arbitrary nor largely unequal. Yes, I concede that it would be possible to have a limited censorship on the internet - as we have seen in China.
But make no mistake - there is no such thing as complete censorship in any society.
Finally, you fall asleep at the wheel of your clapped out ancient buick and drive straight into a liquor store, causing a tremendous fire that takes out half of your town and the newspaper prints a front-page story entitled "How could this have happened?" Oh man, that's TOTALLY AWESOME! How big was the explosion??? That would SO ROCK. I hope the puppies are all right though.
Seriously though... there's plenty of number THREE type people living painful "can't stand myself" lives - getting ready for that divorce, remarriage, joining the nudist club - whatever. You can say number three looks better - but happiness is a fickle thing.
To thine own self be true, as the old saying goes.
It does not work. I'm tried quite a few of them, to be sure.
But there is one exception - and amazingly it works great. Arnica Montana is amazing stuff. All it does is stop compression-type injuries from swelling.
Ya know book sellers tried to do the same thing at the turn of the last century. They placed licenses in the front cover of the books preventing resale of the books.
Isn't it funny that this action led to the Doctrine of First Sale in 1908?
Essentially a Doctrine of first sale only guarantees you the ability to resell. The rest of the so-called "rights" in a EULA are bound by US Contract law - and are probably not legal, at least in the USA. It's a bit murky as of now - and it's certain that factions on both sides of the argument will continue to lean heavily on the courts and congress.
I'm sure that SCOTUS will eventually get a case and hopefully the whole argument will be put to rest.
Well, likely it is because we can't reliably fingerprint children until they're a few years old. It would likely work with ink - but silicon and optical readers have great difficulty with small fingers.
The important point, which the vast majority of posters here are missing, is that the problem should never even exist in the first place.
They know why.. it's the kernel-mode encryption required to send audio to the card. There's two engineering failures here: 1. thread locking is accomplished by raising the interrupt level to DPC (KeAcquireSpinLock) 2. Requiring several steps/levels of encryption to interract with the audio card.
The real issue is a combination of utilizing DPC interrupts for basic thread locking (which thrashes the scheduler during long halts) and encryption (which requires long halts).
The real fallacy, IMHO, is thatMS thinks that because it's in kernel mode that it's immune or safer from attacks - so they created lots of "security features" in the kernel. In many ways this makes attacks much simpler - as you can simply move your code into kernel mode which has fewer limits than user mode!
Understood - it's just that oftentimes people overlook the basic issues. He could get by without having to spend much time & effort - just a little basic knowledge of databases could go a long way. He mentioned 1-2 second queries and I suspected he's just missing the basics.
Ok, first up: 1. Check all your SQL and run it through whatever profiler you have. Move things into views or functions if possible. 2. CHECK YOUR INDEXES!! If you have SQL statements running that slow, the likely cause is not having proper indexes for the statements. Either make an index or change your SQL. 3. Consider using caching. For whatever platform you're on there's bound to be decent caching.
That's just the beginning... but the likely cause of most of your problems. We could go on for a month about optimizing.. but in the end if you just stuck with what you have and checked your design for bottlenecks you could get by just fine.
Give the man a point! hehehe
Dude.. moderators are out of control.
Ever read the moderation FAQ? Just cause you dislike him or his ideas doesn't give you a right to push an agenda. This is a fair comment - how do we deal with languages we don't know and can't even type?
Still not a brick...
A brick would be you turn it on, and it flashes the screen in bright colors hysterically all the while playing the modem version of Jimi Hendrix.. well, Ok, it just turns back off usually.
No - there's no real issue there other than something is mysteriously blocking the phone from recognizing the SIM card. I'm sure it'll be fixable somehow.
Just pure speculation on my part - but I believe you need a "common carrier" of some sort of wave to setup entanglement. It makes sense to build this into a chip so that you can alter the setup at run time.
I suppose eBay is busy cleaning up their "bad reputation." Flame bait? Troll! Yeah right...
I've been in their shoes - writing code and managing millions of credit cards on a web-facing travel application. I have code certified to FIPS 140.2 - I know what it takes to get there.
If they fail customer safety standards they will get my ridicule, as a customer and as an industry colleague.
I have NO problem calling inadequate, dangerous, and reckless companies "stupid idiots." Millions of people TRUST eBay with credit worth billions of dollars - and they have repeatedly failed.
Being called a stupid idiot should be the LEAST of their worries.
Argh... Sarbanes-Oxley, I hate that spelling...
You stoopid idiots!
I've seen too many incidents of hackers gaining access into the eBay admin systems - forum takeovers, listing problems, and such.
Is it so hard to audit your network, code, and such? Well, yes - it takes WORK. Not only is it required for Sabanes-Oaxly, but I would think that risking a huge business like this would be enough of a motivator.
I'd love to say I'm special, as I am a security engineer, but come on! There's thousands of geeks with the background to clean this up. Get Crackin!
Well, you can get unlocked phones right now. You don't get a discount on the service - but they're available. Amazon sells them.
I agree with you concerning the rest - phone companies are slightly above mobsters on my book.
We can't have it both ways - either we need a law which states that all users have a right to be unlocked after their contract is over (paid off or expired) - or we can go along with this hokey hacker versus network approach with bricked phones.
Well, if Apple had a standard way to unlock the phone á la codes and such then this wouldn't have been a problem. They over-engineered the SIM lock software mechanism - knowing that people have the ability and right to unlock their phone.
This is a standard issue in the phone world - and I find it hard to understand why EVERY other phone on the market can be unlocked without bricking the phone.
I always unlock my phones, or buy unlocked ones - I want to have the ability to walk away from a carrier if they do't treat me right and keep my very expensive equipment.
No, this is a threat along the lines of "This is a very nice store you've got Mr. Donatello - it would be a shame to see it burned down, eh?"
You keep speaking of a Model Release - but what matters here is intent. Virgin was perfectly within the rights given to utilize the photo - it was assigned a CC license.
The CC license assumes that the person completely owns the image rights - and that person was the photographer.
But the photographer was ignorant of the law concerning peoples rights to their own likeness. And since the photographer expected and received nothing in compensation (a key point in US contract law) I really doubt there's anything to be recovered here other than a C&D or a libel claim.
If anything - Virgin may "settle" for a token amount. And I'm betting that is the point of the case in totality.
Caveat emptor, of course.
Every time the government limits freedom, there must be an underlying principle of justice - it can not be arbitrary nor largely unequal. Yes, I concede that it would be possible to have a limited censorship on the internet - as we have seen in China.
But make no mistake - there is no such thing as complete censorship in any society.
Seriously though... there's plenty of number THREE type people living painful "can't stand myself" lives - getting ready for that divorce, remarriage, joining the nudist club - whatever. You can say number three looks better - but happiness is a fickle thing.
To thine own self be true, as the old saying goes.
Aye Matey - soon we'll be a sailin our pirate ships o'er the internet! Me crew shall pillage vast new oceans and search for precious booty!
You know it's full of precious booty!
It does not work. I'm tried quite a few of them, to be sure.
But there is one exception - and amazingly it works great. Arnica Montana is amazing stuff. All it does is stop compression-type injuries from swelling.
Ya know book sellers tried to do the same thing at the turn of the last century. They placed licenses in the front cover of the books preventing resale of the books.
Isn't it funny that this action led to the Doctrine of First Sale in 1908?
Essentially a Doctrine of first sale only guarantees you the ability to resell. The rest of the so-called "rights" in a EULA are bound by US Contract law - and are probably not legal, at least in the USA. It's a bit murky as of now - and it's certain that factions on both sides of the argument will continue to lean heavily on the courts and congress.
I'm sure that SCOTUS will eventually get a case and hopefully the whole argument will be put to rest.
Well, likely it is because we can't reliably fingerprint children until they're a few years old. It would likely work with ink - but silicon and optical readers have great difficulty with small fingers.
The important point, which the vast majority of posters here are missing, is that the problem should never even exist in the first place.
They know why.. it's the kernel-mode encryption required to send audio to the card. There's two engineering failures here:
1. thread locking is accomplished by raising the interrupt level to DPC (KeAcquireSpinLock)
2. Requiring several steps/levels of encryption to interract with the audio card.
The real issue is a combination of utilizing DPC interrupts for basic thread locking (which thrashes the scheduler during long halts) and encryption (which requires long halts).
The real fallacy, IMHO, is thatMS thinks that because it's in kernel mode that it's immune or safer from attacks - so they created lots of "security features" in the kernel. In many ways this makes attacks much simpler - as you can simply move your code into kernel mode which has fewer limits than user mode!
Well, actually I'm a daily vim user... LOL... I just didn't have a clue as to when command/filename completion was added to VI.
Pretty sure I've seen predictive input for a LONG time... some examples..
Cell phone input (T9 & iTap circa 1995)
PDA writing interfaces (Newton?)
Shell command line completion. (bash, ksh)
Visual Studio 6...
Emacs
Windows 3.1 tablet edition
Automatic spell checking correction ( MS word 95, possibly before)
I'm sure there's tons more here... but wiring a dictionary up to an input is obvious prior art, no matter how you spin it.
Thanks, all good advice.
Understood - it's just that oftentimes people overlook the basic issues. He could get by without having to spend much time & effort - just a little basic knowledge of databases could go a long way. He mentioned 1-2 second queries and I suspected he's just missing the basics.
Ok, first up:
1. Check all your SQL and run it through whatever profiler you have. Move things into views or functions if possible.
2. CHECK YOUR INDEXES!! If you have SQL statements running that slow, the likely cause is not having proper indexes for the statements. Either make an index or change your SQL.
3. Consider using caching. For whatever platform you're on there's bound to be decent caching.
That's just the beginning... but the likely cause of most of your problems. We could go on for a month about optimizing.. but in the end if you just stuck with what you have and checked your design for bottlenecks you could get by just fine.