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

 



Forgot your password?
typodupeerror
×

Comment My bad Wikipedia experience (Score 3, Interesting) 564

I wanted to write an article about the Solovetskiy Stone, which is a monument to victims of political persecution in the former USSR erected by former Gulag residents right across the KGB headquarters.

I didn't want to create a user - sorry Jimbo, I just don't want to join your fan club. As a form of punishment, I was tormented with like a 17-step wizard with questions such as whether I am writing about a "MUSICAL GROUP, DJ, ALBUM, or SONG". After I finally got to the part where I write my part, it was unceremoniously deleted by the EarWig robot (eh?), because some of the text - basically the address of the place in Moscow - was copy-pasted from memorial.ru. And this is the site with a 10-page article listing the secondary characters in the Final Fantasy world. Sorry, somebody else would have to create this article instead of me and yes, I was shocked at how bad Wikipedia had got.

Comment The search results aren't too good (Score 1) 310

I tried searching for this phrase (don't ask why):
"six seven eight triple nine eight two one-by two"

Google gave me the correct results, Bing gave me something totally bizarre about the Oshkosh Titans.

I can add bells and whistles to the results myself using Greasemonkey, thank you. The server's responsible for good, relevant results, and this is not happening right now.

Comment Re:hang it on your wall? (Score 5, Informative) 120

Um, actually AES does hurt steganography since steganalysis tools have an easier time finding uniformly distributed payloads (such as AES ciphertexts) than somewhat biased payloads (such as standard text).

So, it would be easier to know that you have some data in there, but harder to know what the data is. Your call.

Take a look at this tutorial:
www.citi.umich.edu/u/provos/papers/practical.pdf

Comment Re:Huh? (Score 2, Interesting) 120

The App Engine cluster is not just a big dump truck of cycles you dip into on demand. The processing power is quantized into discrete machines. There's actually a nice scheduler there that checks how busy your app is and assigns new processors to handle it. This isn't a real-time process so there are transient periods with overload. On the long run, GAE will scale fine.

There are some nice vids about the architecture on the Google developer youtube channels.

Slashdot Top Deals

"Who alone has reason to *lie himself out* of actuality? He who *suffers* from it." -- Friedrich Nietzsche

Working...