Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Image

Chinese iPad Factory Staff Forced To Sign 'No Suicide' Pledge Screenshot-sm 537

An anonymous reader writes "Employees at Foxconn facilities in China, used to manufacture the iPhone and iPad, were forced to sign a pledge not to commit suicide after over a dozen staff killed themselves over the last 16 months. The revelation is the latest in a series of findings about the treatment of workers at Foxconn plants, where staff often work six 12-hour shifts a week, 98 hours of overtime in a month, and live in dormitories that look and feel like prison blocks."

Comment Reuters neutrality (Score 1) 575

Sony said on Wednesday that Anonymous targeted it several weeks ago using a denial of service attack in protest of Sony defending itself against a hacker in federal court in San Francisco.

Since when does taking a hardhacker to court constitute "defending yourself"? They might be defending their DRM or EULA or something but the article makes it sound objectively unreasonable for anyone to be upset with them...

Comment *Your* Location? (Score 1) 164

Bad article, worse summary. Google isn't, like, quantizing your habits or anything. Or, maybe they do, but at the very least that isn't what the emails say.

"I cannot stress enough how important Google's wifi location database is to our Android and mobile product strategy," Google location manager Steve Lee told founder Page in the memo. "We absolutely do care about this because we need wifi data collection in order to maintain and improve our wifi location service."

It's not a database of your location, it's a crowd-sourced database of positioning information used to help users determine their location. When you encounter a previously unrecorded wifi network or somesuch and you're using this feature (it has a disclaimer about this), you anonymously add it to Google's database so other users using the feature can triangulate their position that much faster. There's a concern in the article that someone could hijack this process on Google's end and record personal information, but as far as we know from these emails and what they've said publicly, this information isn't being kept, in fact there's an encryption scheme to protect it. It's different from the Apple issue where the information was a) unencrypted b) identifiable (because it's on your phone) c) timestamped (and therefore more useful than "here's everywhere I've been in my life!") There's certainly the issue of privacy for the wifi network owners, but my point is the summary's misrepresenting the story here.

Comment Re:There are three stores on my Archos 43 (Score 1) 153

Additionally there are Android apps (for instance OpenWNN, which handles the Japanese input I mentioned), that already exist, that are free, and are included with some distributions but not available on the Market as anything but "enhanced" bloatware. Yes when I have some time I'll be happy to distribute it myself (I already said "do it yourself" is an option), my point is that this hasn't been done, instead there are multiple repackagings.

Comment Re:Big deal (Score 0) 153

Except the thing that annoys me is that in many cases this software exists and is free, it's just not ported or in the store. There's no reason to pay for it, but this choice doesn't reach end users. I'm sure the FOSS community will adapt sooner or later to the app store model, but I wonder if by that point anyone will be dumping their favorite app for the more private and ad-free equivalent.

Comment Re:Big deal (Score 1) 153

I don't think so. Everyone I know regularly uses all sorts of Android apps that require permissions they don't need. Last I checked you can't even find a free Japanese input program or even an emulator on the marketplace that doesn't require internet access. And at least one of these isn't much more than a privacy-invasive wrapper of gpl code. There was that article a while back about how the vast majority of apps send back user information, and with this as the norm there's often nothing a user can do except port their own apps. What we really need is more effort on the developer side to release clean free apps, but unfortunately there's little personal benefit to doing that.

Comment Re:Timestamps (Score 1) 318

To reiterate: Yes this is more work, but apparently it takes more work to make a cache not be a log. If you indiscriminately recorded all information, that would be a gross breach of privacy, regardless of how inconvenient it would be for the programmers to do something else. This is an example of the same kind of thing. The information can be used to track a user. This has already happened. Apple is expected to avoid this, if possible. It's possible. Hence outrage. A few extra instructions in this process will not affect performance.

We're both asserting our points. You're doing so with provocative language and an attitude. Therefore I'm the troll.

Comment Re:Timestamps (Score 1) 318

Here's one way the timestamp could be helpful: "Hmm. I don't have any of the towers in range cached. I don't have any clue where I am. I better do two things: 1) Assemble a list of towers & hotspots in range, and query for their locations; 2) Look back at the most recent towers & hotspots in my cache, and assume I'm near them for the purposes of beginning map data retrieval." Cell network connections are high latency, and not always high speed. Minimizing the time required before you can start displaying usable information to the user is a feature, not a bug.

You don't need a timestamp for that. You can just number cache batches in the order they were fetched. You know, 1, 2, 3...

Than to sit there saying "Today is Wednesday the 27th of April. Find and purge all entries in the cache that were created before April 20th!", due to the existence of month boundaries, and the simple fact that extra calculation is required every time you do this - making for less efficient software.

It's a bit shift. Nothing is simpler than a single ARM instruction. If you do that you're working with more like 3/4 of a day, but that's good enough for our purposes here.

I'm sorry that you're confined to your home, but not all of us must - or wish to - operate under those constraints.

Stay classy.

Comment Re:Timestamps (Score 1) 318

What are you talking about? A lookup is triggered by a cache miss. Each location batch can be labeled by anything, it doesn't need to be the exact time. This information is useless for any part of the process besides dumping the cache because, like you said, users can travel all over the place in a short period of time. This makes the timestamp not a great heuristic of what batch you want, not that batch lookup would even affect performance in any perceivable way.

Comment Re:Timestamps (Score 1) 318

Your initial question was why they needed timestamps to at all. That question has been answered.

No it hasn't. If they're only retaining records for a week, then once again why do you still timestamps? Everything in the retention period should be "good" data now.

Slashdot Top Deals

Real Users never use the Help key.

Working...