Unless you consider a team of young editors focused more on bureaucracy, edit counts, and sockpuppets than accuracy and a vast crew of 12-15 year olds arguing about My Chemical Romance being classified as "emo" your peers, no, it's not peer reviewed. The number of experienced, talented veterans in a given field editing Wikipedia is *tiny*.
It's easier to attack the network no matter what, for two reasons: 1) If you fail, you don't die. 2) Nobody notices when you succeed, and you're free to do whatever with the information you've got.
If someone notices you've failed (or succeeded), you're likely to be prosecuted in your country of residence. Unless you're hacking for the government, in which case... exactly nothing happens.
Wheras if you fail at dropping a nuke (i.e. the nuke somehow gets destroyed by a "missile defense system") you die. Quickly. And if you succeed, you probably die, slowly, as whatever country you attacked or their allies retaliate in kind.
Now they'll just have to use a *real* rootkit and (mostly un-)hook the calls regmon uses to monitor. A) Stop being paranoid, they're probably scanning the registry in order to check for common bots. B) If you're going to be paranoid, don't buy computer software to start with, any of it could be installing a rootkit and defeating your regmon. C) (You've at least got this one figured out) Don't play WoW
Yeah, this is a brilliant idea until you realize that A) server-side movement means that when the 1000 people playing in the internet cafe in China log on at the same time, they all start seeing their world jerk around B) server-side movement would increase Blizzard's bandwidth usage significantly and most importantly, C) calculating the movement for several million users on the server side sucks, a lot.
So they chose to make a smoother game experience for the majority of legit users, save money on bandwidth, and load up their server farm less. In exchange they have to pay a few kids to write Warden. Ooh.
Yeah, we have those "organized groups" who "press a particular view" in this country. They're called Democrats and Republicans, and a majority of politically active Americans are members of one or the other. So, when Slashdot introduces politics, the politicians move in, and due to the nature of the "average" techie internet-board user (aka Slashdot user) as a young leftist, it's agreement with the young leftist opinions that happens. It's not exactly... difficult to figure out.
They *WANT* the P2Pers to leave. P2Pers who might leave make up at most 3-5% of their customers, and probably use 50-60% of all bandwidth. The P2Pers pay the same price as everyone else and use 10-15 times the bandwidth. The return for Comcast if they leave (the ability to oversell more connections at the same price to the average NASCAR fan) is a lot higher than the cost of losing a few customers.
No it's not; look at the sales of the games which were released across multiple consoles and PC and I bet the PC sold higher. PC is still leading, deal with it.
Though I'm really not sure what the grandparent was trying to say as he basically listed console games and then said "look, PC is better."
Civ IV is a great example though, it's a high-selling, fun game which could never be adapted well to console; it uses a mouse (for examples on why porting this is a BAD idea see Starcraft 64).
Crysis might take to much power to run on a console (that's what they've been saying) but I honestly think that's BS; they just don't want to port it.
Anyway, though, I can just apply your argument in reverse and say there's no reason why Halo 3 couldn't have been released for PC right now.
But does that mean console gaming is dying?
I think not.
Have you ever tried using https exclusively on a production web server? Some people don't have infinite amounts of money to spend on the CPU to encrypt every byte of their homepage every time someone hits it... What's really needed is a signed HTTP solution that doesn't require full-stream encryption; if the user is submitting no data and the data being served is not secret, illegal, confidential, etc. there is no reason for full-stream encryption but a signature would prevent this sort of attack.
I dunno, I'm 16 and few of my friends are into Web2.0. The ones who are tend to A) Run Ubuntu B) Be unable to do anything without a tutorial (this seems to be a trend amongst Ubuntu users too, where did the ability to figure things out yourself go?) C) Obsess over vector tracing to make icons (maybe this is why web2.0 has so damn many icons?) D) Not have a girlfriend
Good suggestion.
People in my area started a WISP (magnolia road internet co-op) and after a few initial hitches (T1s are VERY expensive for the amount of bandwidth provided) they seem to be doing okay (they're almost 3 years in now and are financially stable with a service that is generally positively regarded).
I would have used their service if DSL hadn't have become an option here.
Your *only* option is to see if there's a WISP in the area, or to see if you're close enough to the phone CO to get ISDN. If you have the big money you could also put out for a T1 but that will probably run you upwards of $300USD/month. I used a WISP called IonSky/WisperTel here in Colorado for 4 years (until DSL came to my house two weeks ago, FINALLY). Oddly I still don't have cell service at all (ever since AMPS went away there has been no coverage whatsoever here). It was overall terrible but better than dial-up and far more economical than ISDN/T1. I also had ISDN for a few months many years ago but it was expensive and overall isn't that fast (it is reliable and always-on though, which is a bigger deal than you might think). So, coming from a similar situation, I'll tell you: Find a WISP or it's ISDN for you. Or move, if it's really that big a deal. Dial-up isn't even suitable for SSHing in and doing a little bit of remote admin, it's downright unusuable in today's age.
That's because nobody cared when they did.
When CDMA2000 first came out in the US several carriers used them and then realized that NOBODY CARED because the phones were still locked.
Which is the *same situation* as with GSM.
If GSM didn't basically require a SIM card as an integral part of the network, you can be sure T-Mo and CingularT&T would be getting rid of them ASAP.
p.s. I'm using an unlocked Motorola Hollywood on Sprint right now...
Uh, no, that would have something to do with that CDMA was a more attractive and cheaper-to-implement cellular system at the time. Sorry, no conspiracy there. *EVERY* phone carrier in the US *was* just as bad as Verizon. p.s. you can add an unlocked CDMA phone (if you can find one) to your Verizon plan using a form online. Verizon do have terrible customer service and screw over the customer repeatedly, but that *WAS* just an American phone company thing. This lawsuit makes them several times worse than the rest of the phone carriers though.
By definition it is; however, I wasn't trying to "paint you with the communist brush" or whatever.
But that would also go against BUSINESS, and that's the issue with trying to mix "free-market" capitalism with socialism. The US's method of trying to throw money at private enterprise is clearly a flawed attempt to implement socialism, however, attempting to i.e. divert US troops to perform work is also an issue, what do the "real"/"career" cable-layers do then?
Having the government hire squadrons of public servants for every job is also a flawed idea, since bureaucracy doesn't manage people very well, and this is the reason why the "throw money at the private sector" method is attempted in the first place.
The US is actually perfect proof of why your socialist ideas don't work everywhere. We *do* pay telecoms to build our infrastructure out of our supposedly "low" (they're actually pretty average unless you're rich and can dodge them or poor and mostly-exempt) taxes. We provide them with *billions* in tax breaks and subsidies. And what do they do? Put it in marketing and/or pocket it and run away.
US infrastructure in general is bad (railroads, normal roads, etc.) because it's actually quite a bit *older* than a lot of Europe's. WWII decimated Europe and from the ashes rose modern roads, an effective rail system, and electrical service. A lot of Europe's infrastructure is 60-70 years old. The US has been hacking up and tacking on solutions for hundreds of years. Nobody wants to mess with the status quo.
While I'm sure there is "pressure" from teleco lobbyists on the FCC commissioners and I'm sure this does affect a lot of their decisions (lobbyists "affect" read: pay money for every decision in US government today), I don't think BPL is the best case for you to use for your conspiracy theories. BPL is really, truly flawed. Think about it. You're transmitting high-frequency signals over giant unshielded wires. You are basically sending high-frequency data through an enormous antenna. The interference potential is *huge*, and it shouldn't be allowed to spread unchecked. There are strategies for minimizing interference but they make it so slow as to be pointless.
On the other hand, many development companies (including the one I'm working for) are forcing their developers to use Vista at work so that the next generation of their application is assured to work with Vista without screwing around after QA realizes there are 1000 stupid little Vista bugs. Production end-user environments are sticking with XP because it works and doesn't require insane hardware, development environments are going Vista. I'm guessing this is where a lot of Microsoft's enterprise Vista sales are coming from. The end-users will catch up eventually, because of Microsoft and their forced upgrade cycles (trust me, Microsoft is pressuring the end-users *heavily* to move to Vista). This is all quite depressing, since Vista is the most terrible platform I have had the displeasure of working with (broken driver infrastructure due to DRM crap, broken IPv6 because Microsoft are just lazy, it goes on and on.)
The thing is that the problem isn't in the application processing; it's in X's processing. CFS (which I have run) does not help with X and GUI applications at all. As a matter of fact it made things worse for me, because some processes (Firefox especially) send huge chunks of X requests to the server at once. With CFS, X, because it has the highest "need" for CPU and is niced to a very high priority on many desktop distributions to "improve responsiveness" blocks all other applications from processing, leading to slowness (Firefox "flickering" pages as it sends chunks of X requests off while it's still trying to render the rest).
Attempting to nice X to a lower priority only makes things worse; then your GUI applications block up X and it doesn't help to have your GUI applications processing when you can't see what they're doing!
What really needs to happen is X needs to either go away or be fixed. Linux *desperately* needs less stupid Beryl/Compiz/compiz fuzion extreme lol edition or whatever they're calling it these days, and instead someone needs to create a windowing server which gives each window a draw thread, BeOS style.
Another scary bug (perhaps the scariest, since it appears to be the one that most reliably/repeatably occurs) is AI88: Microcode Updates Performed During VMX Non-root Operation Could Result in Unexpected Behavior. From what the errata says, unless the host software has specifically disallowed access to parts of the MSR, a VMX guest/non-root system could reload the CPU microcode. This leads to a whole universe of complicated data theft/code execution/etc. exploits that will probably never be created due to their complexity. However, it also leads to a very, very, very simple DoS/crash exploit (load some bad microcode, crash the CPU).
Do you not know how to scroll to the right? Or you could just, you know, try it yourself, since it's quite easy and I've documented how to do it. Nice troll.
Apple includes CoreFoundation.dll and CoreGraphics.dll, which have the same exports as the OSX frameworks. Therefore it's possible to use the OSX CoreFoundation and CoreGraphics headers to link to the Windows DLLs natively and create native Windows "psuedo-OSX" apps. I believe CoreFoundation.dll has been around with WebObjects for Windows NT for a while, but I think CoreGraphics.dll is a new Apple "release" (I remember some anger over Apple not porting CoreGraphics when WebObjects/NT first came out). I've documented some of what I've poked around today (just a screenshot and simple description for the moment) at http://pages.brianledbetter.com/
Wrong. The new API changes give applications "write access" to Facebook which they didn't have months ago. Applications can publish news feed stories, create a box on profile pages, and create their own Facebook-integrated and Facebook-URLed FBML "canvas" page, or *embed an iframe into the Facebook layout*. This is a new change that I see going in terrible directions (imagine giant flash-powered ugly userboxes from hell and 10,000 "BOB IS USING FACEBOOK CUSTOMIZER 1.0" news feed advertisments).
Unless you consider a team of young editors focused more on bureaucracy, edit counts, and sockpuppets than accuracy and a vast crew of 12-15 year olds arguing about My Chemical Romance being classified as "emo" your peers, no, it's not peer reviewed.
The number of experienced, talented veterans in a given field editing Wikipedia is *tiny*.
It's easier to attack the network no matter what, for two reasons:
1) If you fail, you don't die.
2) Nobody notices when you succeed, and you're free to do whatever with the information you've got.
If someone notices you've failed (or succeeded), you're likely to be prosecuted in your country of residence. Unless you're hacking for the government, in which case... exactly nothing happens.
Wheras if you fail at dropping a nuke (i.e. the nuke somehow gets destroyed by a "missile defense system") you die. Quickly. And if you succeed, you probably die, slowly, as whatever country you attacked or their allies retaliate in kind.
The "shady bars" are called IRC (and I hear that they exist, for real, in Russia, but I've never been there so I can't actually say).
Uhh... really? You act like it never happens, and sure, that's a sensationalized white paper, but guess what? It's more common than you seem to think.
I laughed at your comment because you present it with such a sarcastic tone, but it's *entirely true*.
Li-ion batteries actually catch fire and burst quite nicely. :)
I think they're okay
Now they'll just have to use a *real* rootkit and (mostly un-)hook the calls regmon uses to monitor.
A) Stop being paranoid, they're probably scanning the registry in order to check for common bots.
B) If you're going to be paranoid, don't buy computer software to start with, any of it could be installing a rootkit and defeating your regmon.
C) (You've at least got this one figured out) Don't play WoW
Yeah, this is a brilliant idea until you realize that A) server-side movement means that when the 1000 people playing in the internet cafe in China log on at the same time, they all start seeing their world jerk around B) server-side movement would increase Blizzard's bandwidth usage significantly and most importantly, C) calculating the movement for several million users on the server side sucks, a lot.
So they chose to make a smoother game experience for the majority of legit users, save money on bandwidth, and load up their server farm less. In exchange they have to pay a few kids to write Warden. Ooh.
Blizzard suck anyway, though.
Yeah, we have those "organized groups" who "press a particular view" in this country. They're called Democrats and Republicans, and a majority of politically active Americans are members of one or the other.
So, when Slashdot introduces politics, the politicians move in, and due to the nature of the "average" techie internet-board user (aka Slashdot user) as a young leftist, it's agreement with the young leftist opinions that happens.
It's not exactly... difficult to figure out.
They *WANT* the P2Pers to leave. P2Pers who might leave make up at most 3-5% of their customers, and probably use 50-60% of all bandwidth.
The P2Pers pay the same price as everyone else and use 10-15 times the bandwidth.
The return for Comcast if they leave (the ability to oversell more connections at the same price to the average NASCAR fan) is a lot higher than the cost of losing a few customers.
No it's not; look at the sales of the games which were released across multiple consoles and PC and I bet the PC sold higher. PC is still leading, deal with it. Though I'm really not sure what the grandparent was trying to say as he basically listed console games and then said "look, PC is better." Civ IV is a great example though, it's a high-selling, fun game which could never be adapted well to console; it uses a mouse (for examples on why porting this is a BAD idea see Starcraft 64). Crysis might take to much power to run on a console (that's what they've been saying) but I honestly think that's BS; they just don't want to port it. Anyway, though, I can just apply your argument in reverse and say there's no reason why Halo 3 couldn't have been released for PC right now. But does that mean console gaming is dying? I think not.
Have you ever tried using https exclusively on a production web server?
Some people don't have infinite amounts of money to spend on the CPU to encrypt every byte of their homepage every time someone hits it...
What's really needed is a signed HTTP solution that doesn't require full-stream encryption; if the user is submitting no data and the data being served is not secret, illegal, confidential, etc. there is no reason for full-stream encryption but a signature would prevent this sort of attack.
Apple has said that the new update will PROBABLY brick phones. Not that it *might*.
This isn't them saying they can't cover some corner case, this is them trying to scare people who have unlocked their iPhones.
And you don't have the update, so you CANNOT say that Apple will not brick phones.
While I too believe "OMG THEY R BRICKIN US" comments are overboard, they are what Apple intended and it is a course that they could take.
I dunno, I'm 16 and few of my friends are into Web2.0.
The ones who are tend to
A) Run Ubuntu
B) Be unable to do anything without a tutorial (this seems to be a trend amongst Ubuntu users too, where did the ability to figure things out yourself go?)
C) Obsess over vector tracing to make icons (maybe this is why web2.0 has so damn many icons?)
D) Not have a girlfriend
Good suggestion. People in my area started a WISP (magnolia road internet co-op) and after a few initial hitches (T1s are VERY expensive for the amount of bandwidth provided) they seem to be doing okay (they're almost 3 years in now and are financially stable with a service that is generally positively regarded). I would have used their service if DSL hadn't have become an option here.
Your *only* option is to see if there's a WISP in the area, or to see if you're close enough to the phone CO to get ISDN. If you have the big money you could also put out for a T1 but that will probably run you upwards of $300USD/month.
I used a WISP called IonSky/WisperTel here in Colorado for 4 years (until DSL came to my house two weeks ago, FINALLY). Oddly I still don't have cell service at all (ever since AMPS went away there has been no coverage whatsoever here). It was overall terrible but better than dial-up and far more economical than ISDN/T1.
I also had ISDN for a few months many years ago but it was expensive and overall isn't that fast (it is reliable and always-on though, which is a bigger deal than you might think).
So, coming from a similar situation, I'll tell you: Find a WISP or it's ISDN for you.
Or move, if it's really that big a deal.
Dial-up isn't even suitable for SSHing in and doing a little bit of remote admin, it's downright unusuable in today's age.
That's because nobody cared when they did. When CDMA2000 first came out in the US several carriers used them and then realized that NOBODY CARED because the phones were still locked. Which is the *same situation* as with GSM. If GSM didn't basically require a SIM card as an integral part of the network, you can be sure T-Mo and CingularT&T would be getting rid of them ASAP. p.s. I'm using an unlocked Motorola Hollywood on Sprint right now...
Uh, no, that would have something to do with that CDMA was a more attractive and cheaper-to-implement cellular system at the time.
Sorry, no conspiracy there.
*EVERY* phone carrier in the US *was* just as bad as Verizon.
p.s. you can add an unlocked CDMA phone (if you can find one) to your Verizon plan using a form online.
Verizon do have terrible customer service and screw over the customer repeatedly, but that *WAS* just an American phone company thing.
This lawsuit makes them several times worse than the rest of the phone carriers though.
By definition it is; however, I wasn't trying to "paint you with the communist brush" or whatever. But that would also go against BUSINESS, and that's the issue with trying to mix "free-market" capitalism with socialism. The US's method of trying to throw money at private enterprise is clearly a flawed attempt to implement socialism, however, attempting to i.e. divert US troops to perform work is also an issue, what do the "real"/"career" cable-layers do then? Having the government hire squadrons of public servants for every job is also a flawed idea, since bureaucracy doesn't manage people very well, and this is the reason why the "throw money at the private sector" method is attempted in the first place.
The US is actually perfect proof of why your socialist ideas don't work everywhere.
We *do* pay telecoms to build our infrastructure out of our supposedly "low" (they're actually pretty average unless you're rich and can dodge them or poor and mostly-exempt) taxes. We provide them with *billions* in tax breaks and subsidies.
And what do they do?
Put it in marketing and/or pocket it and run away.
US infrastructure in general is bad (railroads, normal roads, etc.) because it's actually quite a bit *older* than a lot of Europe's. WWII decimated Europe and from the ashes rose modern roads, an effective rail system, and electrical service. A lot of Europe's infrastructure is 60-70 years old.
The US has been hacking up and tacking on solutions for hundreds of years. Nobody wants to mess with the status quo.
While I'm sure there is "pressure" from teleco lobbyists on the FCC commissioners and I'm sure this does affect a lot of their decisions (lobbyists "affect" read: pay money for every decision in US government today), I don't think BPL is the best case for you to use for your conspiracy theories. BPL is really, truly flawed. Think about it. You're transmitting high-frequency signals over giant unshielded wires. You are basically sending high-frequency data through an enormous antenna. The interference potential is *huge*, and it shouldn't be allowed to spread unchecked. There are strategies for minimizing interference but they make it so slow as to be pointless.
On the other hand, many development companies (including the one I'm working for) are forcing their developers to use Vista at work so that the next generation of their application is assured to work with Vista without screwing around after QA realizes there are 1000 stupid little Vista bugs.
Production end-user environments are sticking with XP because it works and doesn't require insane hardware, development environments are going Vista. I'm guessing this is where a lot of Microsoft's enterprise Vista sales are coming from.
The end-users will catch up eventually, because of Microsoft and their forced upgrade cycles (trust me, Microsoft is pressuring the end-users *heavily* to move to Vista).
This is all quite depressing, since Vista is the most terrible platform I have had the displeasure of working with (broken driver infrastructure due to DRM crap, broken IPv6 because Microsoft are just lazy, it goes on and on.)
The thing is that the problem isn't in the application processing; it's in X's processing. CFS (which I have run) does not help with X and GUI applications at all. As a matter of fact it made things worse for me, because some processes (Firefox especially) send huge chunks of X requests to the server at once. With CFS, X, because it has the highest "need" for CPU and is niced to a very high priority on many desktop distributions to "improve responsiveness" blocks all other applications from processing, leading to slowness (Firefox "flickering" pages as it sends chunks of X requests off while it's still trying to render the rest).
Attempting to nice X to a lower priority only makes things worse; then your GUI applications block up X and it doesn't help to have your GUI applications processing when you can't see what they're doing!
What really needs to happen is X needs to either go away or be fixed. Linux *desperately* needs less stupid Beryl/Compiz/compiz fuzion extreme lol edition or whatever they're calling it these days, and instead someone needs to create a windowing server which gives each window a draw thread, BeOS style.
Another scary bug (perhaps the scariest, since it appears to be the one that most reliably/repeatably occurs) is AI88: Microcode Updates Performed During VMX Non-root Operation Could Result in Unexpected Behavior.
From what the errata says, unless the host software has specifically disallowed access to parts of the MSR, a VMX guest/non-root system could reload the CPU microcode.
This leads to a whole universe of complicated data theft/code execution/etc. exploits that will probably never be created due to their complexity. However, it also leads to a very, very, very simple DoS/crash exploit (load some bad microcode, crash the CPU).
Do you not know how to scroll to the right?
Or you could just, you know, try it yourself, since it's quite easy and I've documented how to do it.
Nice troll.
Apple includes CoreFoundation.dll and CoreGraphics.dll, which have the same exports as the OSX frameworks.
Therefore it's possible to use the OSX CoreFoundation and CoreGraphics headers to link to the Windows DLLs natively and create native Windows "psuedo-OSX" apps.
I believe CoreFoundation.dll has been around with WebObjects for Windows NT for a while, but I think CoreGraphics.dll is a new Apple "release" (I remember some anger over Apple not porting CoreGraphics when WebObjects/NT first came out).
I've documented some of what I've poked around today (just a screenshot and simple description for the moment) at http://pages.brianledbetter.com/
Wrong.
The new API changes give applications "write access" to Facebook which they didn't have months ago.
Applications can publish news feed stories, create a box on profile pages, and create their own Facebook-integrated and Facebook-URLed FBML "canvas" page, or *embed an iframe into the Facebook layout*.
This is a new change that I see going in terrible directions (imagine giant flash-powered ugly userboxes from hell and 10,000 "BOB IS USING FACEBOOK CUSTOMIZER 1.0" news feed advertisments).