Hacker News new | past | comments | ask | show | jobs | submit login

Sure, the framers meant to protect the information, not the paper stock. But they gave a right against a particular way of accessing that information. They prohibited warrentless searching or seizing--i.e. infringing your property rights in--the paper, not a blanket right against the government collecting that information by any means.

If the framers had intended to protect the information regardless of source, whether or not it was contained in your papers and effects, they would have done so. The framers did not have Facebook, but they would have understood the importance of sensitive information held by third parties. They were merchants, bankers, wealthy farmers, and lawyers. They would have been able to conceive of, for example, the government collecting manifests from a shipper to prosecute a merchant for evading taxes. Or subpoenaing books from an accountant. The fundamental legal question underlying a big chunk of the surveillance issue--can the government force Facebook to give it information Facebook has about a user--has been teed up ever since subpoenas and accountants existed (both a couple of hundred years prior to the founding).

What the framers did not contemplate is that one day the government would not have to infringe your property rights to get all your personal information.




Is it maybe an analogy problem?

At the time of the framing, your accountant had your information, but he was also authorized to know it. Nobody at Google is authorized to read my email or even I expect look at who I'm corresponding with. It's all done by machine.

And the whole concept of "property" as inside a machine is unusual. Is an email on a server like a letter on an accountant's desk, or is it like a letter on my desk in my apartment which I lease from someone else?

Was the government in 1780 allowed to subpoena the Post Office for your mail?


> Nobody at Google is authorized to read my email or even I expect look at who I'm corresponding with. It's all done by machine.

The "machine" versus "Google employee" distinction isn't a compelling one. The computer is programmed by a human agent of Google to scan your email, collect information, and use that information for Google's purposes. Also, wouldn't your reasoning allow the government to avoid any allegations of 4th amendment violations by pointing to the NSA computer that does the actual scanning?

> And the whole concept of "property" as inside a machine is unusual. Is an email on a server like a letter on an accountant's desk, or is it like a letter on my desk in my apartment which I lease from someone else?

It's not unusual. Property is defined by the bundle of rights you have with respect to something, whether that something is tangible or intangible.[1] A lease is a property right that limits what the lessor can do. Your landlord cannot, except under certain exceptions, enter your apartment and look through your desk (or send a robot to do the same). Your landlord has no interest in the things inside your apartment, which remain solely your property. None of that is true for many types of digital information held by third parties. Google explicitly retains the right to scan your emails and use the collected information for commercial purposes. At some point, Google retained quite extensive rights over what you put on Google Docs (although they've narrowed that in a TOS change). Facebook retains quite extensive rights over what you post.

The 1878 case of Ex Parte Jackson addresses the Post Office issue. It distinguishes between sealed letters (protected by the 4th amendment), and things like postcards that are open to inspection, even if they are not routinely inspected (not protected). Arguably, most clear-text online traffic falls in the latter bucket.

All of that being said, my point is that you certainly could conjure up a right to digital privacy from the "penumbras" of the 4th amendment. But the opposite view--that no such right exists--is pretty logical too. Certainly, I think logical enough that you can't say that the text of the 4th amendment compels you to find that such a right exists.

[1] This should not be a foreign concept to programmers. It's very much like a capability: https://en.wikipedia.org/wiki/Object-capability_model.


The right to freedom from search is not about envelopes. Arguments about cleartext online email cannot stem from paper equivalents - it must be about intent, how it affects our lives, not some rule-lawyering view.

Further, when govt attempts to prevent citizens from putting email into secure envelopes then its clear what's going on. Its goes from "I can easily read your email; thus its not protected" to "You must submit all you email for inspection!" That's clearly the sort of thing the 4th amendment is intended to protect from.


> Also, wouldn't your reasoning allow the government to avoid any allegations of 4th amendment violations by pointing to the NSA computer that does the actual scanning?

That's assuming the scanning never results in any information being conveyed to a person or recorded anywhere someone might eventually read it. That wouldn't provide much use to the government.

> None of that is true for many types of digital information held by third parties.

That depends on the third party. Not all email providers do that. And if scanning your email to target advertising was the determinant of whether the government could read it without a warrant, email providers would stop doing that or people would stop using them.

And then wouldn't it change based on whether the scanning is done client side or server side?

> Arguably, most clear-text online traffic falls in the latter bucket.

That puts a different spin on the whole encryption debate. If not encrypting traffic allows the government to read it without a warrant, a government encryption ban takes on a whole new meaning.

And the traffic increasingly is encrypted. Hosts are increasingly using TLS for HTTP and SMTP.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: