Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

An indictnment is a charge; it is the prosecutors formal presentation of the evidence collected so far that show's that there's enough evidence that a trial should be held.

As such, it's fairly one-sided. It's just what the prosecutor has presented to a grand jury, and the grand jury has said "yeah, that looks like enough evidence that it's worth having a trial." Note also that grand juries these days pretty much always just rubber-stamp whatever the prosecutor puts in front of them.


I've posted this before on the subject, but I particularly like the description given by Ken White at Popehat:

"Rather than tread over the ground well-described by my colleagues in the criminal defense bar, today I'd like to describe something else for you: what a federal grand jury proceeding looks like. From 1995 through 2000, I presented cases of varying complexity to federal grand juries as a federal prosecutor in Los Angeles. That experience did not inspire confidence in the process. Rather, it taught me that the adage that a grand jury will indict a ham sandwich is an understatement. A better description would be that the prosecution can show a grand jury a shit sandwich and they will indict it as ham without looking up from their newspapers. The notion that the Supreme Court relies upon — that the grand jury has a "historical role of protecting individuals from unjust persecution" — is not a polite fiction. A polite fiction would have some grounding in reality. It's an offensive fiction, an impudent fiction, a fiction that slaps you across the face and calls your mother a dirty bitch."

http://www.popehat.com/2014/02/27/the-kaley-forfeiture-decis...


Yep, my answer when cp or scp is not working well is always to break out rsync, even if I'm just copying files over to an empty location.

I've had good luck with the -H option, though it is slower than without the option. I have never copied a filesystem with nearly as many files as the OP with -H; the most I've done is probably a couple million, consisting of 20 or so hardlinked snapshots with probably 100,000 or 200,000 files each. rsync -H works fine for that kind of workload.


You can use the arrow keys to navigate, which is a lot better than clicking "Continue" each time.


Arrow keys don't help much on a tablet or a phone.


Why do you think the author failed to understand the quote? It's pretty clear that the author understood the implication that self-interest causes cooperation, but is pointing out that there are other forces which cause cooperation as well, and that focusing too much on self-interest can diminish these other forces.


Because most people aren't in it for "fame and recognition" or "vanity"?

If I find a bug in a piece of software, or something misconfigured, I tend to report it and move on. I don't try to hide my identity before reporting it. A security vulnerability is just a bug or misconfiguration, that happens to be exploitable for nefarious purposes. The responsible thing to do is to notify those responsible, and anonymity doesn't help with that; they may need to follow up to ask questions to find out more details about it.

While there are some people in the security community who are prima donnas, who try to hype them selves and their exploits to gain recognition, this case does not appear to have anything to do with that. This is someone who sent a private email to those responsible, and then started seeing articles online and getting complaints emailed to his college about irresponsible hacking of other institutions websites in front of students.


Interesting. I think that the confusion arises because the Microsoft paper was many people's first exposure to the term, which led people to assume that they had coined the term. Based on the Wikipedia article, it looks like it is a relatively new term, with the first usage I could find in 2011, but that it does predate the Microsoft paper.

It looks like Dan Eckert coined the term for this video: https://vimeo.com/19441262 then later used it to refer to the general technique, for which he registered http://www.hyperlapse.com/ in 2012. Other people started using it, like https://vimeo.com/50238512, and now Microsoft and Facebook are both developing applications that both use the term to automatically create hyperlapse sequences.


Fire one, arbitrary restrictions lead to their own problems, with people having to implement workarounds that make their code more complicated and bug prone.

For another, notice that one of the features they used in this exploit was similar "adjustable lower limits"; changing ulimit values to defeat most of the value that ASLR provides.

In general, I think that using safer languages, like Rust, Go, Java, or even modern C++, is more likely to be the answer than imposing new arbitrary limits. These kinds of buffer overruns, failures to remember to free memory, and so on are all too common in C, and can be avoided if you just use safer languages and constructs that do bounds checking and automatic memory management.


> I'm sorry, but this is insane. No local government is going to allow these things to be buzzing around everywhere for no good reason.

You mean like all of the cars and trucks that are rumbling around everywhere for no good reason? They roar around everywhere, are incredibly dangerous, require billions of dollars of government funded infrastructure, and destroy the environment. No one would ever allow them to become common, when we have such alternatives as walking, bikes, trains, and the like, right? They're just crazy inefficient; a bike is so much more energy efficient for a single person, and a train is faster, safer, and more efficient for moving large numbers around.


The rise of the personal car involved a huge amount of corruption to accomplish, with municipalities basically gutting the better alternatives you propose on behalf of the emerging auto-industry.

So yes, I think sans massive government corruption, we don't see these kinds of technologies that are intrusive and inefficient rising to prominence.

Also, trucks hit a technological sweet spot that I don't think drones sit in. They have predictable and easily controllable failure modes; they're always traveling at eye level where they're relatively (easier) to spot; they have relatively high transport capacity, enabling multiple visits; etc.

The problem with drones that replace trucks is that I'm not sure we've actually gained much by having flying trucks all over the place - the increase in delivery time (which I'm not sure would actually be very high in the average case) would easily be offset by the danger of many low flying trucks.


> The rise of the personal car involved a huge amount of corruption to accomplish

They may explain the US, although I doubt it. It doesn't explain literally every single other industrialized nation in the world, including the many ones without a powerful auto industry.

> They have predictable and easily controllable failure modes

So will drones, once they mature. And despite all the predictability and controllability, trucks still fall over or get themselves wedged under bridges etc, shutting down traffic for hours.

> they're always traveling at eye level where they're relatively (easier) to spot

Except when they're around a corner, and it's not much help to a cyclist about to be crushed by a turning truck.

> they have relatively high transport capacity

For drones to be competitive they will have to be competitive with this fact. If you're right, drones will never take off (pun intended). If you're wrong, you're wrong.


I think people are overestimating the danger posed by drones, and underestimating the danger posed by trucks, just because drones are exotic and trucks are commonplace. I know a family who just lost half of its members to a truck, due to no fault of their own. Trucks are far from safe.


So, I think that the best way to address this would be to allow it to be mostly open. The default is for all notes from the doctors and patients visible to everyone; but doctors can write "hidden" notes that only other doctors are able to see.

In a lot of ways, I see this like a public bug tracker. For bug trackers, it's generally best for everyone to see all changes, to be kept up on what's going on and be able to most usefully provide extra information. But for security sensitive issues, or internal discussion that involves things that the end user needn't know about, many have a way of posting "protected" comments that only certain privileged users can see.


Where do you draw the line about what's "protected"? It seems pretty arbitrary, so easy to abuse.


In general, you have to put a certain amount of trust in your doctor.

They are helping you make pretty life altering decisions. Now, there is a bit of a cultural barrier where they aren't used to the idea of patients being as involved in their medical care, but on the whole, they are there to help you.

If you're really all that worried about your doctor writing lots of secret notes and not letting you see them, even once there's a system in place to allow you to easily collaborate with them, maybe it's time to get a new doctor?


And what if doctors just start writing everything in the secret notes? The situation sounds exactly like what has happened with the US government classification system.


How does hidden help? An honest response to a hypochondriac is pretty obvious to any other doctor. 100x "patient complains of y, tests show no evidence"


I know more about pediatrics than about other specialties, but there are several use cases for hidden commentary in pediatrics. One is commentary about how to handle the patient's parent, who may, for example, be well-meaning but verbally abusive to staff, and the practitioner needs to be know to be constantly reassuring to avoid confrontation. Another includes notes that are about the patient, but not legally allowed to be seen/read by the parent (who otherwise has rights to a child's medical record in the US until age 18), such as discussions around sexual activity or birth control.


Note that since Oracle basically closed ksplice, RedHat has developed kpatch and SuSE has developed kgraft, which are both similar ways of doing the same kind of thing, and there is some discussion going on about whether they can be merged or a better general purpose kernel patching method developed: http://wiki.linuxplumbersconf.org/2014:live_kernel_patching


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: