Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:One YouTube problem solved. One more to go... (Score 1) 61

Except, you see, that humans are in portrait orientation most of the time (as the name suggests, you see), and we're the majority of subjects of mobile video. And, since so many people are watching video on phones, it turns out that the majority of screens are also in portrait orientation most of the time. So, really, the problem is crummy playback systems that fail to present vertical videos at the maximum possible size.

Comment Re:BS detector went off and is overheating (Score 1) 309

Anyway, yes it turns out with just log, square root, and multiplication, you can assemble any whole number between 0 and infinity with just four fours. Fairly useless, but a neat puzzle.

Four fours, plus an arbitrarily large number of unary operators like square root, which feels like cheating.

Comment Safari also lazy-loads tabs (Score 1) 766

Unfortunately, modern browsers are so stupid that they reload all the tabs when you restart them. Which takes ages if you have a hundred of tabs. Opera was sane: it did not reload a tab unless you asked for it.

Safari doesn't reload background tabs until you switch to them. (Unlike Chrome, which does try to open every tab at once, hammering the internet connection, the processor, and the RAM.)

Comment Re:Um (Score 1) 492

So if someone with peanut allergies receives a candy bar with peanuts, they open it and take a bite. The sender is liable for damages?

If the sender knows they have an allergy to peanuts and marks the package deceptively to trick the target into eating it, then yes that's assault or attempted murder. (Heck, there's even an iZombie episode about this exact means of assassination.)

Comment Re:Want to guess why? (Score 4, Informative) 192

No new coal plants were added, and solar became the top new source of generating capacity.

Want to guess why? Because one is subsidized and the other was successfully taxed and regulated out of existence.

No, it's for the same reason there was no capacity added from burning whale oil, namely that it's not economical. Natural gas (#2 on that list) is what kicked coal to the curb, not environmental regulation. There's lots of articles covering this, such as this one from not-exactly-a-bastion-of-liberal-thought Reason magazine.

Comment Re:Motor whine (Score 2) 361

It takes a while to learn it. I bike regularly in a place with a lot of electric cars, and I realized that I few months ago, I had internalized their particular noise and could now sense they were in my blind spot. Until I retrained my brain to recognize them, though, I had been filtering them out because they were not what I had learned cars sound like for the last few decades.

Comment Re:Curly braces = good. Indents = bad. (Score 3, Insightful) 173

The biggest problem with indentation-as-structure is that tools in general support it poorly. When cutting-and-pasting or moving code around, it's easy to mess up the indentation of the code being transformed. By contrast, I can move around brace-delimited code sloppily, then tell my IDE to auto-indent, and it looks nice and legible. (It also acts as a form of error-checking; if the resulting indentation looks weird, it's a strong signal that I've screwed my blocks somewhere.)

Comment Just ban common passwords (Score 2) 148

The solution is to just ban common passwords. Start with a list of dictionary words and leaked credentials from other sites, and simply ban the use of said passwords for accounts on your site. That's what Arenanet does for Guild Wars 2. You also ban new passwords as too many people try using them. As for messaging, you just straight up tell the user "That password is too well-known. Try something more creative."

You don't even need to store the password to implement popularity-based bans. When a user enters a new password, hash it and store the hash in a table (just the password hash, not the associated account). Each time someone else uses that password, increment the count. When it hits N, just ban new uses of that password, and optionally force current users of that password change it on login (by checking the plaintext they just entered against the banned hashes). (Meanwhile, store a salted hash associated with the account id for login purposes, to make it harder to crack passwords if your hashes get leaked.)

Slashdot Top Deals

A computer without COBOL and Fortran is like a piece of chocolate cake without ketchup and mustard.

Working...