Domain: 216.239.37.104
Stories and comments across the archive that link to 216.239.37.104.
Stories · 3
-
Innocent File-Sharers Could Appear Guilty?
daveo0331 writes " New Scientist has an article about what could be a promising defense strategy for people targeted by the RIAA. Basically, anyone on the Gnutella network can frame other users by making it look like someone is hosting RIAA music, even though they're not. Therefore, the RIAA's "evidence" against file sharers is theoretically unreliable and wouldn't stand as good a chance of holding up in court. No mention of whether this has anything to do with the RIAA's eagerness to settle the lawsuits out of court. The article is based on a research paper (PDF link, HTML version) posted anonymously to a web hosting service in Australia." -
Deregulation and Niagara Mohawk - Is There a Story?
It's just a few hours after the Northeast U.S. power outage, and facts are trickling in; as of right now, it looks like an accidental overload knocked out a large part of the Niagara Mohawk power grid. A few years ago, California went through rolling blackouts that were largely due to a poorly-executed deregulation of that state's power industry. The question that's probably occurring to many of us is, did late-'90s deregulation play a role in today's power event? I don't know the answer, so I'm turning it over to you -- moderators, please check links and up-mod the most informative, pro or con. Here is some information to get you started: "We support deregulation 100 percent..." (N-M spokesman, 1997; notes N-M wanted to sell generators and "concentrate on the transmission and distribution of energy" -- did it?); N-M made some bad investments and is scheduled to request a rate hike (did it?); and N-M's own website says: "Deregulation [has] changed the laws and regulations governing the electricity industry to promote competition..." (how so?). -
Including Source for a Potential Hacking Tool?
rajinder asks: "What are the experiences of Slashdot folk when it comes to including the source code of a security tool in their final year dissertation? I have a project in mind that I want to submit that can be used by admins to evaluate the security of their wireless network(s), but it could just as easily be used for their nefarious purposes. Before I submit the idea, I wanted to see if anyone knew of potential hurdles I would have to face. Anybody ever done something similar? The official rules about what is allowed is available in this PDF [or the HTML version], but I don't see anything relevant to my dilemma (the relevant section is 2.4, page 9) UK university-system specific info would be appreciated, but I plan on carrying on my education in the US, so info from either side of the pond would be good. Does anyone know if I would be able to GPL the code afterwards and put it out there? Would it remain property of the University or the student that wrote it?"