They were short and to the point. A video game is made by many people practicing many artistic disciplines. It is absurd to think that the final product isn't art.
Fortinet did an analysis of this. http://blog.fortinet.com/all-your-drives-are-belong-to-us/ It simply backs up the partiton table and rewrites the MBR. It's fixable without paying the ransom.
http://www.facebook.com/topic.php?uid=196994196748&topic=23238 They started a discussion group right on the Cooks Source Facebook page. 5 pages of links showing Cooks Source republishing content stolen from elsewhere. There's a blog somewhere else that took it further, I'll have to look for that.
The internet detectives went back through previous issues and found that almost every article ever published in this mag was lifted from somewhere else. They never had an ounce of original content. All they did was take other's work and try to profit off it. Eventually they got caught. How anyone can feel sorry for them is mind boggling.
It's not Verizon's responsibility to do anything unless people on their network are breaking laws. Last time I checked, general trolling was not against the law. (If it were, half the internet would be shutdown.
Wikipedia needs to get their act together and secure their own site better. The fact that they're even considering blocking editing from /6s and /8s is absurd.
Slashdot isn't always the most timely place to see things, but it's usually at least accurate. Too bad this made it through today.
whisper_jeff writes "I work in a design studio where the production director is also the owner's son (translation = he can do no wrong). He is fond of accessing a designer's computer via filesharing and working directly on files off of the designer's computers rather than transferring the files to his computer to work on them there. In so doing, he causes the designer's computer to grind to a near-halt as the harddrive is now tasked with his open/save requests along with whatever the designer is doing. Given that there is no way he's going to change his ways (since he doesn't see anything wrong with it...), I was wondering if there was a way to throttle a user's shared access to a computer (Mac OSX 10.5.8) so that his remote working would have minimal impact on our work. Google searches have revealed nothing helpful (maybe I should Bing it... :) so I was hoping someone with more technical expertise on Slashdot could offer a suggestion."
After analyzing data from a radar device aboard last year's Indian Chandrayaan-1 mission to the Moon, NASA scientists have found what they estimate to be 600 million metric tons of water ice in craters around the Moon's north pole. "Numerous craters near the poles of the Moon have interiors that are in permanent sun shadow. These areas are very cold and water ice is stable there essentially indefinitely. Fresh craters show high degrees of surface roughness (high circular polarization ratio) both inside and outside the crater rim, caused by sharp rocks and block fields that are distributed over the entire crater area. However, Mini-SAR has found craters near the north pole that have high CPR inside, but not outside their rims. This relation suggests that the high CPR is not caused by roughness, but by some material that is restricted within the interiors of these craters. We interpret this relation as consistent with water ice present in these craters. The ice must be relatively pure and at least a couple of meters thick to give this signature."
Apple was well into their lawsuits against Pystar in October. Why would you purchase a product that from a company that was getting them sued, especially when most reporting at the time was that Pystar was probably going to lose?
Arrington isn't suing for breach of contract. He isn't suing for on any grounds related to the IP. To me, this suit is simply intended to sic legal costs on Fusion Garage since they backed out of whatever verbal or implied deal that they had with Arrington, and he's mad about it. The claims aren't frivolous, but they're pretty weak, and not what Arrington has said the actual problems were.
eldavojohn writes with an update to the CRU email leak story we've been following for the past two weeks. The peer-reviewed scientific journal Nature has published an article saying the emails do not demonstrate any sort of "scientific conspiracy," and that the journal doesn't intend to investigate earlier papers from CRU researchers without "substantive reasons for concern." The article notes, "Whatever the e-mail authors may have said to one another in (supposed) privacy, however, what matters is how they acted. And the fact is that, in the end, neither they nor the IPCC suppressed anything: when the assessment report was published in 2007 it referenced and discussed both papers." Reader lacaprup points out related news that a global warming skeptic plans to sue NASA under the Freedom of Information Act for failing to deliver climate data and correspondence of their own, which he thinks will be "highly damaging." Meanwhile, a United Nations panel will be conducting its own investigation of the CRU emails.
harrymcc noted a story talking about what might be the end of Google Gears. The concept has always been interesting, but it seems that Google is beginning to think of Gears as more of a proof of concept, and that focus will shift to HTML5, which has the same functionality.
Prevx admitted that Microsoft was correct, so continuing to trash them for it seems pointless. I'm fairly certain that they don't test patches against malware infected machines to check for issues, nor would I really expect them to. No software developer should be forced to account for all possible malware effects in their code. Nothing would ever be released!
An anonymous reader writes "At Virginia Tech, a new orchestra will be debuting a unique and original sound. Scoot over winds and brass, strings and chorale — it is time to make room for the laptop orchestra."
Link to Original Source
Link to Original Source
sirguinness writes "Microsoft spent several days investigating claims by security vendor PrevX that the company's latest security updates had caused a registry problem that was in turn causing some Windows machines to display a black screen. The Microsoft Security Response Center could find nothing in the updates that was causing the problem, and neither could the company's support organization. "The company has found those reports to be inaccurate and our comprehensive investigation has shown that none of the recently released updates are related to the behavior described in the reports. While we were not contacted by the organization who originally made these reports, we have proactively contacted them with our findings. Our support organization is also not seeing this as an issue. The claims also do not match any known issues that have been documented in the security bulletins or KB articles," Christopher Budd, security communications lead for the MSRC, said in a statement."
Link to Original Source
Link to Original Source