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


Forgot your password?

Comment NYT and Twitter attacked (Score 4, Insightful) 169

and nothing of value was lost...

Seriously, there's something I've never understood about electronic "warfare": unless you attack real targets and do something useful, such as penetrating your enemy's command network to steal plans or cryptographic keys or something, what's the point?

Comment Re:The NSA is violating the Constitution (Score 5, Insightful) 107

The Snowden story is the tip of the iceberg. Whatever happens to him, whether he escapes the wrath of the US authorities or he gets caught and "rendered", will serve as a reminder to the world of what the US is turning (or has turned) into. His pizza, and whatever else he does, is very useful to know about in that respect: it keeps him in the limelight, and continues to discredit the administration.

Incidentally, none of the US powers that be is "asleep at the wheel": they're all very actively working against their constituents and against the population to keep themselves and their rich friends rich and in power.

Comment I think the wider story here is (Score 5, Insightful) 362

How using Facebook at all can bring harm to you in real life.

Case in point: a colleague's teenage daughter applied for a summer job at the local supermarket, got selected and went to a job interview. The interviewer asked her to "describe herself". She did, and the interviewer then said "that's not what your Facebook says. Thank you, we'll call you." She's only 16 and she wasn't doing anything particularly public or outrageous on Facebook. It hit her hard and my colleague says she's been kind of depressed by the rejection she's faced.

As for me, I've learned the hard way 13 years ago (before Facebook but after Google) that the internet never forgets, and whatever you say will come back to haunt you eventually. As a result, I've learned to shut my trap online whenever possible.

Comment Re:Surface (Score 1) 633

Failure of Windows 8
Failure of Xbox One
Failure of Vista
Failure of the Kin
Failure of the Zune
Failure of Windows Phone 7
Failure of Windows Phone 8

Ummmm, what the fuck is a Kin?

[Checks Wikipedia Kin]
Kin was a mobile phone from Microsoft, manufactured by Sharp Corporation...
Microsoft invested two years and about US$1 billion developing the Kin platform.

How the fuck do you spend a billion dollars, and and fail so hard that a geek's geek had to google the name?

You can add Bing to the list of failures, considering that "google" is now an English language dictionary verb synonym for "search", and "Bing" is just an annoying sound that hasn't earned dollar #1 of profit.


Comment Re:Misinterpretation *By Linux* (Score 1) 280

I found it surprising that it seemed to be saying that most of the devices responded in under a microsecond, while others were over 10ms.

I'm pretty sure it was a single device that was tested 227 times.

The spec actually says the host must send a 20 ms wake up signal, then wait quietly for 10 ms. If we start counting from the beginning of the quiet period (the end of the wake up signal) then you get the odd seeming result that the device is usually ready "instantly <1 ms" and sometimes takes 13 ms. But if we start counting from the beginning of the wake-up signal we get the more reasonable seeming result that the device usually completes waking up in <21 ms and sometimes took up to 33 ms. The device was in violation of the spec in the occasional cases where the it took >30 ms to complete the activation.


Comment Re:Welcome to EE (Score 2) 280

Atleast with the case of xHCI the 10ms is actually a minimum for both -- the specs do not indicate a maximum for the hardware to resume at all.

That's not how specifications work. Both sides are required to obey the spec for things to work. A minimum for one side is a maximum for the other side.

It's like we have a lunch break specification. The specification says that on a lunch break he must wait a minimum 30 minutes before sending the employee more work to do. This means the employee has a maximum 30 minutes to finish lunch.

What is happening here is that the employer (the computer) is obeying the spec. It's waiting the required minimum time, then sending a message "here's some work to do". The employee (the USB device) is late, still lingering out to lunch (in violation og the lunch rules) when he gets the work message. This employee (device) is responding "I'm not ready, I quit" and goes home (device disconnect).


Slashdot Top Deals

Almost anything derogatory you could say about today's software design would be accurate. -- K.E. Iverson