I think the standard these days is the passive underwater sonars - the likes that were deployed on crucial choke points during cold war. Cant's seem to recall the name of the currently declassified system though:/
Someone who runs Windows. In an environment where upgrading to SP1 is unlikely (runs on at least Windows 7 vanilla, exits on SP1 - can also be explained by assuming more sophisticated detection on SP1 boxes), yet both x86 and x64 versions are in use (two versions of binaries - so perhaps previous versions with variants?), someone who is running a particular software package the name of which is known and which follows the normal windows software installation procedures (key hash generation and the fact it's looked up from under the program files - can be a distraction though!).
I actually think that the program files path is a distraction. The actual key is a hash of a particular known file in a system, the non-ascii entry in the program files is ether a null result to be matched against or an extra test.
Which, for me, is the scariest bit. Having such a precise knowledge of a target system, yet still bothering to target it with a release-in-the-wild trojan does imply a few things...
Communicators were fecking brilliant, especially as in the early days of GSM you had to do a ISDN simulated modem session whenever you needed a connection. Packet data/GPRS came fair few years later. 9210 (the pinnacle in my view) was a masterpiece. EPOC/Psion level of usability and ease. It even had a as_you_type filtering of the contact book! (unheard of at the time) and proper telnet clients (SSH wasn't a big thing yet then).
To be honest on occasions the browser was horrible due to the operator trying to 'make it better' for you. I still want to find whoever made the 'optimizing' proxy for Vodafone (UK) in 2007 and do horrible things to their kids, family, pets and property.
*(kidding. I've forgotten the company name now, it was a proxy solution. It was absolutely horrendous though)
Forget the blackberry (it was, and still is, a one trick pony), but the point about original RAZR fucking up the rest of the industry while the capabilities were already there holds absolutely true.
I'll go one step further and say that Carmack (and I remember his rant back in... 2006?) is indeed an idiot. The CPU was never a limitation, it was always around the memory bandwidth. Once you were working in nice pre-allocated byte arrays as a fixed bounds state machine (absolutely okay for anything game related) you were flying...
Define a difference between J2ME and 'native' application. Motorola V3 (all shit around 2005-2007) and the platform used on most of the Motorola phones at that time was J2ME. Which lead to some interesting findings like having well written J2ME applications beating the FPS of native interface 3x.
Android is not native as well. Doesn't hold it back much. iOS is arguably native, but still within a sandbox.
The status is an interesting one - mind, there's also the whole concept of the overseas territories. And quite a few of T&C's specifically excludes those.
What about using one that is actually run by US government as honeypot op? They seem to stay up and any issues with control would be resolved (as in - the FBI is already taking a network dump under controlled enough provisions, just trust them).
Completely disagree. Would you really want to be in a position to say that the US military has been actively circumventing licensed content access provisions?
It might be a US warship, but it's not in the fucking USA, where the southpark episodes are licensed to be shown!
Frankly, if you don't value your uptime worth x why bother? There is no magical pill and if your current infrastructure fails to handle existing load there's nothing you can prudently do without shelling out additional money (or time - which IS money).
If it all seems to work all right, just make sure you back-up and monitor your existing hardware for possible failures.
Linux still uses X. Regardless of how far away it's abstracted with dirty ugly hacks, it's still X.
So - for desktop use - no, it's NOT technically better. And it has little to do with the drivers not being open, but rather the religious insistence of nutters to keep the useful, flashy, graphics, you know - desktop, bits out of where they could work.
Slashdot Mirror
Oh, tell more?
I think the standard these days is the passive underwater sonars - the likes that were deployed on crucial choke points during cold war. Cant's seem to recall the name of the currently declassified system though :/
Give it 6 months, Microsoft might just get desperate enough...
Ain't going to happen. The only viable energy source (nuclear) is being opposed by everybody it seems.
Because SMS is a store and forward system. There is no way to authenticate origin, only destination (well, implicitly, by it being reachable).
And it's been already decompiled and it takes a local, available only on a target system, parameter as a key input. It's elegant, I grant them that.
And it wouldn't be likely the target computers would be running it.
Someone who runs Windows. In an environment where upgrading to SP1 is unlikely (runs on at least Windows 7 vanilla, exits on SP1 - can also be explained by assuming more sophisticated detection on SP1 boxes), yet both x86 and x64 versions are in use (two versions of binaries - so perhaps previous versions with variants?), someone who is running a particular software package the name of which is known and which follows the normal windows software installation procedures (key hash generation and the fact it's looked up from under the program files - can be a distraction though!).
I actually think that the program files path is a distraction. The actual key is a hash of a particular known file in a system, the non-ascii entry in the program files is ether a null result to be matched against or an extra test.
Which, for me, is the scariest bit. Having such a precise knowledge of a target system, yet still bothering to target it with a release-in-the-wild trojan does imply a few things...
*tip of a hat to one old-timer to other*.
Communicators were fecking brilliant, especially as in the early days of GSM you had to do a ISDN simulated modem session whenever you needed a connection. Packet data/GPRS came fair few years later. 9210 (the pinnacle in my view) was a masterpiece. EPOC/Psion level of usability and ease. It even had a as_you_type filtering of the contact book! (unheard of at the time) and proper telnet clients (SSH wasn't a big thing yet then).
To be honest on occasions the browser was horrible due to the operator trying to 'make it better' for you. I still want to find whoever made the 'optimizing' proxy for Vodafone (UK) in 2007 and do horrible things to their kids, family, pets and property.
*(kidding. I've forgotten the company name now, it was a proxy solution. It was absolutely horrendous though)
BTW, Google, keep the Motorola engineers, they make fantastic radios, but lay their programmers off. Those guys suck.
Somebody yet again summarises the essence of Motorola. This statement has been true for last 10 years.
This. This shouldn't be at 0 (where it is now).
Forget the blackberry (it was, and still is, a one trick pony), but the point about original RAZR fucking up the rest of the industry while the capabilities were already there holds absolutely true.
I'll go one step further and say that Carmack (and I remember his rant back in ... 2006?) is indeed an idiot. The CPU was never a limitation, it was always around the memory bandwidth. Once you were working in nice pre-allocated byte arrays as a fixed bounds state machine (absolutely okay for anything game related) you were flying...
Define a difference between J2ME and 'native' application. Motorola V3 (all shit around 2005-2007) and the platform used on most of the Motorola phones at that time was J2ME. Which lead to some interesting findings like having well written J2ME applications beating the FPS of native interface 3x.
Android is not native as well. Doesn't hold it back much. iOS is arguably native, but still within a sandbox.
Approx. 2006. SonyEricsson sorted this out in their JP6 engine (by JP7 it was smooth).
Approx. 2002 actually. This is when the J2ME runtime was finalized well enough to be stable and usable.
Fun trivia fact. First J2ME capable phone was Siemens SL45i. Sexy little beast. Look it up, you'll be envious.
Yeah. One was capable, documented and predictable. The other one was Symbian.
Before I'm downmodded into oblivion - I was/am a commercial mobile software developer since 2003.
Was original iPhone a month after its release a featurephone or a smartphone?
Not many people remember, but there was already a fairly healthy ecosystem in J2ME software, especially sites like getjar.com.
There isn't such a thing as a 'nice bourbon' on this planet. Some like this vile dishwasher like liquid, but it's nether nice, nether whisky. ;)
The status is an interesting one - mind, there's also the whole concept of the overseas territories. And quite a few of T&C's specifically excludes those.
What about using one that is actually run by US government as honeypot op? They seem to stay up and any issues with control would be resolved (as in - the FBI is already taking a network dump under controlled enough provisions, just trust them).
Completely disagree. Would you really want to be in a position to say that the US military has been actively circumventing licensed content access provisions?
It might be a US warship, but it's not in the fucking USA, where the southpark episodes are licensed to be shown!
Frankly, if you don't value your uptime worth x why bother? There is no magical pill and if your current infrastructure fails to handle existing load there's nothing you can prudently do without shelling out additional money (or time - which IS money).
If it all seems to work all right, just make sure you back-up and monitor your existing hardware for possible failures.
"We don't serve potential muslims" would do just fine. Clear-cut, acceptable and efficient.
Linux still uses X. Regardless of how far away it's abstracted with dirty ugly hacks, it's still X.
So - for desktop use - no, it's NOT technically better. And it has little to do with the drivers not being open, but rather the religious insistence of nutters to keep the useful, flashy, graphics, you know - desktop, bits out of where they could work.