Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment I actually have prior art for this (Score 1) 323

My final year project for my CS degree was pretty much doing what this patent describes, and it was submitted in 2008, two years ahead of this patent being filed. I even have a conference paper (published with my project supervisor) published in the same year, so there's lots of hard evidence. I also know that there's a few other projects that could claim prior art to this patent, and precedes my own work. I'm pretty sure there's more than enough prior art in the world to blow this out of the water should it be challenged in court. Heck, I'm surprised the USPTO had the gall to allow this one through at all.

Comment Re:Do you want a job as a software developer? (Score 1) 520

IMHO you should change that to just "Do something on the side to improve your skills and experience in the area you want to be in." :)
Even if it's the area you currently work in. If you don't love the thing you're either already working in or want to work in enough to do so, then it's the wrong thing for you.


Submission + - Can You Beat A Computer At Rock Paper Scissors? ( 1

tekgoblin writes: " It looks like the New York Times has created a game that uses artificial intelligence to outsmart you. It uses a simple game called Rock, Paper, Scissors which is pretty much known by everyone on the planet by now. The computer tries to mimic human reasoning by building on simple rules and statistical averages. So based on the rules of the game and your previous moves, the computer tries to make predictions on your next move. The game has 2 modes, the first being Novice where the computer learns the game from scratch, and veteran where the computer has experience of over 200,000 rounds of previous experience."

Comment Re:70% if the revenue? (Score 1) 280

I'm sure they can claim that the IP agreement was just for the W7 app and these new ports are exempt from the agreement. So now they own the IP for your ports and still get 30% from the revenue of the original W7 app. They most likely also charge a 30% fee for the apps listing.

Of course, you could always use the W7 app as a litmus test for popularity and if you then think you can make some real cash, leave you MS job and then write the ports.

Comment Re:Attack by prononymous? (Score 1) 143

I have a sourceforge project. All I did was pull down the repo to another location and run a diff on my working repo and the one I pulled down. There were no unexpected differences. I'm struggling to see why this is so hard to understand. It's simple to figure out if your project has changed in an unexpected way. It also easy to overwrite the repository on the sourceforge server with a clean one if you are suspicious.

Seriously, an attack this public will not catch out many projects. And I fail to see how someone would be able to "prove" that a project stole code when it's been made so public that SF was compromised. Just that fact would cast a huge amount of doubt over that sort of claim. Especially when one of the developers hands over an untainted version from their home machine for inspection.

Comment Re:Attack by prononymous? (Score 1) 143

Um...each developer will have a working copy on their local machine. This is most likely to be the last known good version. A quick diff will show up the changes that they've recently made and they can verify that the differences are valid. It's really not that complicated.

If someone wants to go through the trouble of hacking the version control to the point it can propagate to the developers machine, stop them from reverting changes that may have been pulled down just before the repositories were locked down, I'm pretty sure they'd be smart enough to break into sourceforge without making such a big mess and alerting everyone. We can go around with increasingly unlikely scenarios forever but the fact is, a quick check is all that's realistically required.

Comment Re:Attack by prononymous? (Score 1) 143

It's simple for the devs, now alerted to a potential compromise, to just branch the repo and do a quick diff between the last known good revision and the one on the server. I doubt a big public attack is going to compromise many projects and those it does manage to compromise are probably mismanaged anyway.

Slashdot Top Deals

The solution of this problem is trivial and is left as an exercise for the reader.