The "cloud" hate is strong here so I suppose I shouldn't be surprised that nobody has mentioned this yet, but this is quite simply a non issue. Box and Dropbox allow you to share files publicly, but it is not the default. While each have had genuine security issues in the past, this is not one. This is simple, common user ignorance. Both services have proper and secure sharing methods to share documents with other users of the service that require authentication on both ends.

What happens is:

- User clicks "Share dropbox link" from the context menu OR user places file into a pre-configured public folder
- User gives link to recipient
- Recipient enters it into a browser with one of those horrible combo search/url bars
- Link is indexed by the search engine

The important thing to remember is that that link does not exist before the user selects that action. These links also expire, and there is also an "Unshare" explicit action.

Nuclear, obviously. The energy crisis was solved 50 years ago. Our will to implement the solution just vanished under a haze of ignorance and propaganda.

Hit the enter key from time to time, son. Nobody will be able to get through that.

The psychology of disenfranchisement has been turned on you, and it's working. Don't let it.

Most of the world knows that the more guns there are in the hands of citizens, the more shootings and gun crimes there are.

Most of the world _might_ think this, but know it? I've seen evidence for that assertion and it's inverse. I don't know which is sound, nor do I care. Clearly mere legal ownership rates is not the most important factor in gun violence considering you can find evidence to support any position you wish to take on that one.

And I'm pretty sure those people were "properly trained" in the use of the automobile.

By whom? In every state I've lived in drivers license requirements are so lax they might as well just stop pretending and rubber stamp every application. I'm "pretty sure" hardly anyone has been "properly trained" in the use of an automobile in the USA.

You'd only need 5ish drives to match raw throughput, but to match IOPS, the more important factor in enterprise uses, you'd need 250 of the fastest 15k drives you can find just to match a single average SSD, and that's if you run them with RAID 0. If you wany any sort of redundancy that number is going to get a lot bigger.

Nearly every SAN out there offering flash capability is limited by the CPU, software, and bus speeds. SAN vendors also love to severely mark up flash drives.

I feel much like you, and I attribute it to there being nothing particularly interesting or new about the Pi. It's just a small, cheap computer. I've installed and configured linux on a hundred systems big and small, and I learned everything this thing can teach me a long time ago.

DIY is fun and can be a great learning experience, but it ends there. After that it turns into a time sink just to keep the damn thing going for no gain other than to learn what having a second job is like. If you just want something to use let somebody else deal with the hassle of making sure it works and keeps working. Let someone else design the UI, negotiate relationships with 3rd parties for commercial application support, keep an eye on security issues, fix that random idiotic HDCP issue with that new TV, deal with that bug in ffmpeg, etc.

A bullshit practice being common is not really a great reason to prepetuate the practice. Now is about the best chance we'll get to change the culture around this sort of entertainment to stop seeing this sort of double dipping as normal or, worse, expected.

I don't think cable companies use to pay for commercial supported networks, but that landscape slowly changed. It use to make sense. The cable company was paid for distribution and the networks covered their expenses with advertising. Now the cable company must pay for access to the network, and the network _still_ advertises. This model has moved to the likes of Hulu where Hulu must pay for both distribution and the content. However, now the ad revenue _also_ goes to Hulu instead of directly to the network.

It's all one giant pile of fuckery letting the finer aspects of the typical fucked up economic model around cable companies shine and persist.

"... rights are the fundamental normative rules about what is allowed of people or owed to people, according to some legal system, social convention, or ethical theory." - http://en.wikipedia.org/wiki/Rights

That seems a reasonable definition of rights for this discussion. Applying this to geekoid's comment, "He wanted to use political force to deny rights to people", is prefectly valid. The right existed in the legal sense prior to the passage of the proposition. Political force was being used to "re-remove" (deny) the right.

You are absolutely correct the "governmental advantages" associated with marriage are, indeed, privileges in the legal sense, but that's beside the point. Marriage itself is a right that places those who obtain married status into a class that enjoys specific privileges.

I do agree that marriage is not a _natural_ right, but a civil one. Marriage is, afterall, and entirely human legal creation. That the right existed in the state prior to prop 8 does result in it being an explicit attempt to deny a pre-existing civil right. However, even if that had not been the case, it is still possible to deny a right that has not been expressly granted in the past. To put it as simply as possible; "Can I have this?", "No" - Denied.

Of course all of this completely ignores the ethical issue which you so nicely opened up in your final sentence. However, I'll leave that fo rother commentors. The irony of one who would deny rights on the grounds of thinly veiled bigotry (but it's just my opinion!) calling those who would grant them bigots is not lost on most.

I'm actually embarassed for you, /.

wth..

I'd most definitely like to have that information. I'm always scanning for pedestrian timers so I'd definitely use it. However, the person that hit you was either not paying attention, tailgating, or both. From a defensive driving posture that info may have helped, but, as an alternative defensive action, I'd probably have just kept going rather than slam my brakes.

I would make the claim that perhaps you were speeding to need to slam the brakes in the first place, but there's been enough discussion of yellow light timers here that it may very well have been timed to shortly allowing benefit of the doubt. If that's the case I'd make the claim that the issue to fix is the yellow light timing and not work arounds like this to deal with poor timing.

To sum up, this information shouldn't be needed to prevent being rear ended at an interestion with a light turning red, and I don't think the addition of it would help under proper conditions. The original stated use, efficiency gains, remains the most sensible.

The guy behind you couldn't manage to pay enough attention to avoid colliding with vehicle directly in front of him. What makes you think he has the mental capacity to plan ahead when the planning process requires actual thought? It saddens me, but I don't think technical solutions will matter here so long as people like that are in total control of the vehicle.

How is it a filesystem in the unix philsophy? It's monolithic in the worst possible way; a clumsy mess of layering violations. One analogy would be if someone said "http would be so much better if it wasn't for those pesky tcp, ip, and ethernet layers!"

I remain bitter that all of that work into advanced data protection, volume management, and efficiency features was wasted on a single filesystem instead of placed in device mapper where they belong. Then ext4 could have useful features such dedupe, load balancing, compression, etc. Hell, if proper layer constraints and software design were used FAT16 could have these features!

Shame on ZFS, shame on BTRFS, and shame on the community for supporting these abominations.

I find the little things often neglected such as:

Ctrl-A to select all
Triple Click
The ability to select text from e.g. labels to copy at all..
Proper ordering of widgets for tab
Click radio button/check box label

Etc.

If applications could just get the basics right it'd go a long way.

Which is interesting considering ScreenOS has among the most annoying CLIs I've ever used. However, the web interface is so freaking good that I don't care.

I'm going to miss it when Juniper finally kills it..