> Now Microsofties could complain that the open source proponents are whining unfairly about this and it is resticting their, "Freedom to innovate". To that I say simply this, "How about you instead spend the effort on making your browser work like everyone else's?"
Agreed!
So, Microsoft, when is IE (Internet Explorer) going to support WebGL, like every browser does?
"cost growth and execution problems were based on the fact that no GMR radios were ever even tested by potential users until 2010. After 13 years in the pipeline, what those users saw was a radio that weighed as much as a drill sergeant, took too long to set up, failed frequently, and didn't have enough range."
That's OK - it is your choice to remain in denial. After you are dead you will realize the missed opportunity to know. Fortunately you will keep getting opportunities until you do, so no worries mate.
> Why would lag enable (item-related) hacks? I know Blizzard games have had some duping hacks involving induced lag over the years, but that's just crappy code. Agreed; but it did. Duping in Diablo 1 was trivial -- just by dropping items on the ground and picking them up fast.
> As long as you don't trust your clients, there's just no opening for item-related hacks. In theory yes, in practice no. If you don't trust the client for anything you a) overload your servers b) introduce > 100 ms responses that players find unacceptable i.e. See Bungie's awesome networking talk on "I Shot You First" http://www.gdcvault.com/play/1014345/I-Shot-You-First-Networking
6. Pirate because the software is no longer available for sale. (and the company is trying to hawk their "new" improved version when the old version does everything you need.) Commercial software sucks in this regard; at least with open-source, sure the old version may no longer be supported but at least you can legally download and use it. i.e. WinXP, TrueSpace, Vivacity, etc.
> wasn't the biggest complain about Diablo 2 the fact that it was wide open to cheating/hacking due to the fact that you could bring online the stuff you acquired offline?
Only the hackers played open b.net -- that lets you import your offline characters
Most of the people played closed b.net -- the servers and game are 100% on Blizzard's server. It was more hack-resistant, but nothing is ever 100% hack-proof (due to lag).
There was a bad bug where you could "fuse" items in closed b.net but that was fixed pretty fast. Duping bugs kept getting found due to the sheer determination of hackers wanting to understand and tear apart the client code. The game is mostly hack-free these days with 1.13; the biggest problem is the spam-bots which has almost completely killed the community. Everyone plays in private games.:-/
> it is very likely they also know how you salt and/or create the user-specific string. so in that case, trying to find the password by a user still becomes trying all possible password until you find one that matches.
False, if the the site is using double passwords.
If you passwordHash2( userId + passwordHash1( plaintext )) good luck even trying to "crack" that password.
Functions passwordHash1 and passwordHash2 could be the same one-way-hash or passwordHash2 could be the "super" strong one-way-hash. As long as both are sufficiently "strong enough" you are fucked.
> You don't need "expertise" in religion (whatever that means) to know that religions are `the stupid virus`, and that Mormonism in particular is really fucking stupid.
Oh please. Atheists are just are ignorant as Theists. At least the Agnostics are intelligent enough to admit it.
Ironically, the Gnostic is off in the corner staying silent watching the humor in it all.
Re:Switched to Mate desktop, not going back.
on
GNOME 3.6 Released
·
· Score: 2
They *still* can't put the close button on the left side *apart* from the minimize / maximize buttons?
Do those guys even understand the first thing about UI design??
Why can't teachers for each subject get together every year andcoordinate the subject in textbooks?
Textbooks should be freely available to all (digitally) with NO copyright so that ALL can learn. It is insane to copyright facts, and their presentation when it is being used to educate the general populace. The *basis* of civilization is founded the core principle of sharing. Sharing goods, sharing knowledge, etc.
> 2) People who, like me and the rest of my department, change it every month can't anymore, because months have 31 days and it must be changed after 30.
Agree that is annoying. For this, I use this trick: append the month number as 2 digits on the end of your password. i.e. Let's sat is Feb which is month 2, then the password would be: MySuperDuperPassword02
That way you should only be at most 1 number off.
> It also has increased the out time for people who are waiting for a password reset and therefore the workload for the IT department. That's another area where people screw up security. If you are going to require frequent password changes, then the turn-around-time MUST be extremely short, else you are just going to frustrate your users.
> Inconsistent password policies for length, characters and expiry date.
We _really_ need standards for passwords & passphrases: minimum LENGTH and SYMBOLS included.
If you site can't handles passwords / passphrases around ~ 96 characters long with the characters (space) 0x20 - 0x7E, your site is *broken*.
The same crap with usernames. Stop limiting me to a max username length of 12 characters A-Z,a-z because your shitty architect / programmer / DB guy doesn't have a clue about security.
I propose a multi-tiered system with a schema like:
NAME#@%
PASS#@%
Where
# is the max length allowed * 16
@ represents which glyphs are allowed to be. Higher is better, which each level including the characters from the previous set A = A-Z (0x41-0x5A) B = a-z (0x61-0x7A) C = 0-9 (0x30-0x39) D = space,!-/ (0x20-0x2F) E =:-@ (0x3A-0x40) F = [-` (0x5B-0x60) G = {-~ (0x7B-0x7E) % is the number of months the password is valid for.
Examples: NAME1C0 is 16 characters, in range: A-Z,a-z,0-9, 0 = never expires PASS6G3 is 6*16 = 96 characters, in range 0x20.. 0x7E, expires in 3 months
Then we flame & shame the idiots, er sites, that use crappy username and password polices.
> I can tell the difference but I'd be willing to bet money an audiophile would be unable to tell a uncompressed 24/96 from a 192 kbps LAME encode of the same source (even on his best setup).
You would of 1/2 lost that bet with this audiophile.
1/2 lost? It depends on the music *type*.
For pop/rock, it is almost impossible to tell the difference. For classical or jazz you most definitely can tell the difference!
If I must convert to crappy mp3 format, I transcode down to 256 kbps minimum using LAME. Most of the time I just rip to a lossless format since drive space on portable players is finally become big enough and cheap enough.
Just because you don't have a clue about high performance Javascript nor WebGL doesn't mean the post is a troll; When you are trying to hit 60 frames/sec even 10 ms can make a difference when you have to resort to stupid language tricks like pre-increment to optimize a brain-dead language because the interpretor is stupid.
Maybe you could tell me why even Google is interested in high-performance Javascript; there implementation is called V8. From their homepage at https://developers.google.com/v8/
"V8 is Google's open source high-performance JavaScript engine, written in C++ and used in Google Chrome, the open source browser from Google. It implements ECMAScript as specified in ECMA-262, 3rd edition, and runs on Windows XP and Vista, Mac OS X 10.5+, and Linux systems that use IA-32, ARM or MIPS processors. V8 can run standalone, or can be embedded into any C++ application. To see just how fast V8 is, look at the benchmarks. A good introduction to some of the core concepts that make V8 so fast can be found in the 2012 Google I/O "Breaking the JavaScript Speed Limit with V8" video (slides). "
Instead of adding absolutely nothing of value to the conversation why don't you do something productive and learn how Javascript is implemented so you can see first hand how much overhead the implementation of Javascript has: http://code.google.com/p/v8/source/browse/trunk/src/
Come back when you are interested in learning how to write fast JS; you might actually learn a thing or too.
/sarcasm Oh, that's a great philosophy - I'll be an asshole because these other people are not able to respect my difference of opinions so I'll disrespect theirs too.
> Having access to a firearm is the most common method of suicide in the United States,
Blaming the symptom doesn't fix the root cause. ANY tool can be used for either good or bad but by your logic we should ban cars because they kill the same amount of people as guns.
"In 2009 there were 31,236 gun deaths nationwide for a rate of 10.19 per 100,000 and 36,361 motor vehicle deaths (both occupant and pedestrian) nationwide for a rate of 11.87 per 100,000 (both totals include data only for the 50 states). Source: WISQARS database, National Center for Injury Prevention and Control, Centers for Disease Control and Prevention."
Slashdot Mirror
> Now Microsofties could complain that the open source proponents are whining unfairly about this and it is resticting their, "Freedom to innovate". To that I say simply this, "How about you instead spend the effort on making your browser work like everyone else's?"
Agreed!
So, Microsoft, when is IE (Internet Explorer) going to support WebGL, like every browser does?
Please mod parent up.
Link has actual information on specifically why Minecraft currently doesn't pass cert., and what can be done about it.
sad but true & funny ...
Here's a crazy idea or two ...
1. You know, maybe they could stop wasting money on an inanimate object called "terror". And/or stop trying to kill people who think different.
http://freemarketmojo.files.wordpress.com/2009/09/dat2010mint.jpg
2. Or maybe stop wasting money on undeployed and under-developed tech ...
http://arstechnica.com/information-technology/2012/06/how-to-blow-6-billion-on-a-tech-project/
Nah, that's just crazy talk ...
That's OK - it is your choice to remain in denial. After you are dead you will realize the missed opportunity to know. Fortunately you will keep getting opportunities until you do, so no worries mate.
> Why would lag enable (item-related) hacks? I know Blizzard games have had some duping hacks involving induced lag over the years, but that's just crappy code.
Agreed; but it did. Duping in Diablo 1 was trivial -- just by dropping items on the ground and picking them up fast.
> As long as you don't trust your clients, there's just no opening for item-related hacks.
In theory yes, in practice no. If you don't trust the client for anything you
a) overload your servers
b) introduce > 100 ms responses that players find unacceptable
i.e.
See Bungie's awesome networking talk on "I Shot You First"
http://www.gdcvault.com/play/1014345/I-Shot-You-First-Networking
How do you observe what happened "before" the Big Bang? ;-)
Considering that money is energy, then yes, the only way to end capitalism is with *true* Free Energy.
You missed case 6.
6. Pirate because the software is no longer available for sale. (and the company is trying to hawk their "new" improved version when the old version does everything you need.) Commercial software sucks in this regard; at least with open-source, sure the old version may no longer be supported but at least you can legally download and use it.
i.e. WinXP, TrueSpace, Vivacity, etc.
http://en.wikipedia.org/wiki/TrueSpace
http://www.topazlabs.com/vivacity/
> wasn't the biggest complain about Diablo 2 the fact that it was wide open to cheating/hacking due to the fact that you could bring online the stuff you acquired offline?
Only the hackers played open b.net -- that lets you import your offline characters
Most of the people played closed b.net -- the servers and game are 100% on Blizzard's server. It was more hack-resistant, but nothing is ever 100% hack-proof (due to lag).
There was a bad bug where you could "fuse" items in closed b.net but that was fixed pretty fast. Duping bugs kept getting found due to the sheer determination of hackers wanting to understand and tear apart the client code. The game is mostly hack-free these days with 1.13; the biggest problem is the spam-bots which has almost completely killed the community. Everyone plays in private games. :-/
> but that doesn't mean I 100% know for sure that there is no personal god.
Which is ignorance. *You* don't *know*.
There is indeed a way to *know*. You don't know because you don't know your True Self.
> It's just the evidence I have found so far points to not.
FTFY.
If you are looking outwards you will *never* find it; the solution is to look *inwards*.
> it is very likely they also know how you salt and/or create the user-specific string. so in that case, trying to find the password by a user still becomes trying all possible password until you find one that matches.
False, if the the site is using double passwords.
If you passwordHash2( userId + passwordHash1( plaintext )) good luck even trying to "crack" that password.
Functions passwordHash1 and passwordHash2 could be the same one-way-hash or passwordHash2 could be the "super" strong one-way-hash. As long as both are sufficiently "strong enough" you are fucked.
> You don't need "expertise" in religion (whatever that means) to know that religions are `the stupid virus`, and that Mormonism in particular is really fucking stupid.
Oh please. Atheists are just are ignorant as Theists. At least the Agnostics are intelligent enough to admit it.
Ironically, the Gnostic is off in the corner staying silent watching the humor in it all.
They *still* can't put the close button on the left side *apart* from the minimize / maximize buttons?
Do those guys even understand the first thing about UI design??
> because how could Time itself start 14.6 Billion years ago?
. /sarcasm What! You mean don't follow the dogma/nonsense that out of nothing came time and space!? Heretic! ;-)
--
"If energy can neither be created nor destroyed, then logically the universe must of have ALWAYS existed."
> the ability of some insignificant bags of protoplasm on an insignificant planet near a run of the mill star,
Wow - with self esteem like that, no wonder you feel like crap. :-)
Why can't teachers for each subject get together every year andcoordinate the subject in textbooks?
Textbooks should be freely available to all (digitally) with NO copyright so that ALL can learn. It is insane to copyright facts, and their presentation when it is being used to educate the general populace. The *basis* of civilization is founded the core principle of sharing. Sharing goods, sharing knowledge, etc.
Agreed.
Time to coin Murphy's Law on Software Deployment? :-)
"In theory dev, test, and prod are in sync, in practice they rarely are."
> 2) People who, like me and the rest of my department, change it every month can't anymore, because months have 31 days and it must be changed after 30.
Agree that is annoying. For this, I use this trick: append the month number as 2 digits on the end of your password.
i.e.
Let's sat is Feb which is month 2, then the password would be:
MySuperDuperPassword02
That way you should only be at most 1 number off.
> It also has increased the out time for people who are waiting for a password reset and therefore the workload for the IT department.
That's another area where people screw up security. If you are going to require frequent password changes, then the turn-around-time MUST be extremely short, else you are just going to frustrate your users.
I've posted about this in the past http://slashdot.org/comments.pl?sid=3001279&cid=40757735
> I can tell the difference but I'd be willing to bet money an audiophile would be unable to tell a uncompressed 24/96 from a 192 kbps LAME encode of the same source (even on his best setup).
You would of 1/2 lost that bet with this audiophile.
1/2 lost? It depends on the music *type*.
For pop/rock, it is almost impossible to tell the difference.
For classical or jazz you most definitely can tell the difference!
If I must convert to crappy mp3 format, I transcode down to 256 kbps minimum using LAME. Most of the time I just rip to a lossless format since drive space on portable players is finally become big enough and cheap enough.
Just because you don't have a clue about high performance Javascript nor WebGL doesn't mean the post is a troll; When you are trying to hit 60 frames/sec even 10 ms can make a difference when you have to resort to stupid language tricks like pre-increment to optimize a brain-dead language because the interpretor is stupid.
Since obviously you don't know anything about high performance Javascript I would recommend you start here:
http://en.wikipedia.org/wiki/Minification_(programming)
Maybe you could tell me why even Google is interested in high-performance Javascript; there implementation is called V8. From their homepage at https://developers.google.com/v8/
"V8 is Google's open source high-performance JavaScript engine, written in C++ and used in Google Chrome, the open source browser from Google. It implements ECMAScript as specified in ECMA-262, 3rd edition, and runs on Windows XP and Vista, Mac OS X 10.5+, and Linux systems that use IA-32, ARM or MIPS processors. V8 can run standalone, or can be embedded into any C++ application. To see just how fast V8 is, look at the benchmarks. A good introduction to some of the core concepts that make V8 so fast can be found in the 2012 Google I/O "Breaking the JavaScript Speed Limit with V8" video (slides). "
Instead of adding absolutely nothing of value to the conversation why don't you do something productive and learn how Javascript is implemented so you can see first hand how much overhead the implementation of Javascript has:
http://code.google.com/p/v8/source/browse/trunk/src/
Come back when you are interested in learning how to write fast JS; you might actually learn a thing or too.
Can anyone clarify the event / story / background / context on this "history" please?
TIA.
/sarcasm Oh, that's a great philosophy - I'll be an asshole because these other people are not able to respect my difference of opinions so I'll disrespect theirs too.
Stay classy.
> Having access to a firearm is the most common method of suicide in the United States,
Blaming the symptom doesn't fix the root cause. ANY tool can be used for either good or bad but by your logic we should ban cars because they kill the same amount of people as guns.
"In 2009 there were 31,236 gun deaths nationwide for a rate of 10.19 per 100,000 and 36,361 motor vehicle
deaths (both occupant and pedestrian) nationwide for a rate of 11.87 per 100,000 (both totals include data only for
the 50 states). Source: WISQARS database, National Center for Injury Prevention and Control, Centers for Disease
Control and Prevention."
http://www.vpc.org/studies/gunsvscars.pdf