5 ms·
TL;DR: Agree to disagree! Google has been known to present as Python-urllib (a generic Python library) with no other references to Google ( http://www.user-age
by vy8vWJlco 14y ago
TL;DR: Agree to disagree!
Google has been known to present as Python-urllib (a generic Python library) with no other references to Google ( http://www.user-agents.org/cgi-bin/csv2html.pl?data=allagents.csv&template=detail.html&match=\bid_n_s_1159\b http://www.user-agents.org/cgi-bin/csv2html.pl?data=allagent... ). Their main bot currently presents itself as Mozilla and various mobile browsers ( http://googlewebmastercentral.blogspot.ca/2011/12/introducing-smartphone-googlebot-mobile.html http://googlewebmastercentral.blogspot.ca/2011/12/introducin... ), and plenty of others, albeit with a parenthetical reference (they used to actually present as Googlebot as the main agent, now they impersonate as the default).
http://en.wikipedia.org/wiki/Criticism_of_Google#Cached_data http://en.wikipedia.org/wiki/Criticism_of_Google#Cached_data
http://infolab.stanford.edu/~backrub/google.html http://infolab.stanford.edu/~backrub/google.html
$$4.3: Crawling the web:
It turns out that running a crawler which connects to more than half a million servers, and generates tens of millions of log entries generates a fair amount of email and phone calls. Because of the vast number of people coming on line, there are always those who do not know what a crawler is, because this is the first one they have seen. Almost daily, we receive an email something like, "Wow, you looked at a lot of pages from my web site. How did you like it?" There are also some people who do not know about the robots exclusion protocol, and think their page should be protected from indexing by a statement like, "This page is copyrighted and should not be indexed", which needless to say is difficult for web crawlers to understand.
That about sums it up: the laws largely reflect the foot-stamping of non-technical people who wanted copies to be more like apples on a tree and less like reflections in a pool. To be sure, it is possible to commit real crimes using the Internet: securities fraud (real fraud), invasion of privacy, uttering threats, etc, but copying itself should not be criminal.
>"I could just as easily argue it's fraud to restrict any copying via a network that functions for that purpose."
"Where is the appropriation by deception in this?"
The deception is of copying as appropriation, which I consider impossible. The appropriation on your part (the royal "you") is 1) the loss of my freedom to surf/access the net using the tools and methods of my choosing (with any user agent string or MAC I want, or by scanning an IP block, or by sending a multicast packet), and 2) your gain of copies as a store of value.
"Are you really claiming that people don't change MAC address in order to avoid being identified with previous use under a particular MAC address, that it's not solely to mask identity."
No, I am saying a MAC was not an identity to begin with. Sites use technical means to limit some access, while usually leaving others open (there has to be some way for users to get at the bits). Why should anyone assume those means left open shouldn't simply be used instead? (The discriminator could have discriminated further, to an arbitrary degree, since the rules only exist in software.)
Again, it boils down to your definition of "unauthorized" which is defined firmly in one camp (not that copy, it's mine!) and equally firmly but very differently in another camp (copying is easy; copying will always be easy). The people who regularly apply access controls and maintain the networks largely assume other people could too, if they wanted to, so what feels like "security" for one person (a MAC address) isn't considered "security" for others. (I'm not speculating about Aaron's views, I'm talking about mine. I agree, I don't think he did anything wrong.) The general feeling is one of all-or-nothing access amongst those who define the locks; part of the hacker/inquisitive mindset is not wanting there to be any locks they can't bypass.
That lock analogy is problematic. Using an elaborate means to copy is not the same as breaking into a building by climbing through a window. Copying (looking) doesn't cause bodily harm or deprivation, and so is not fraud. Lots of people want to claim it can cause financial harm, but I don't buy that one either. Non-commercial copyright infringement is basically free advertising: the sort of word-of-mouth you pay through the nose for. Paying up-front for a copy is absurd; you pay after you hear the minstrel, and you only pay if you liked the music. You can stop playing music for me, but you can't, with accuracy, call me a thief for listening or not paying.
Keep in mind I'm describing what I think should be, not what I think the laws are. You are free to disagree, but this is the context for my comments.
The Internet was, and is, and remains a copying (looking) free-for-all, where code is law. That doesn't make it a wild west that needs to be civilized either - there's nothing to civilize in the absence of copyright. It doesn't mean we have to pull in property and theft analogies... This is still exclusively about copying. As little as 10 years ago we all thought copying would bring some kind of digital salvation: access to all human knowledge. (Enter Wikipedia...) Turns out we want to monetize copying instead, so we are reducing individual freedoms and access rights. Yes, reducing. Give me a break. (For the sake of keeping up with your exasperations.) I already pay my ISP for the link. The copying is implied.
Copying is only scary because you don't know the person doing it - but they aren't doing it to you; copying isn't an injury.
I run an SSH server, and I prevent access to it as well. I also run a wireless access point with a pretty simple password. I don't care if someone uses the wireless if they find the password. Good on them. If they use it to commit a crime I do, but using it is not the crime. Similarly, if they find the password to the SSH server, also good for them; if they find the password to the SSH server and commit an actual crime, then there will be charges (though not from me unless I was the victim), but looking onto a property (a physical computer) is not a crime. You have to forget about that if you want to monetize information, but that's why there's a lack of common ground between the two camps: there's no property to speak of.
Admittedly, there are a number of laws based on the idea that copying should be illegal (copyright as an obvious example). I'm not ignorant of them, but I challenge them. (Granted, I probably wouldn't be willing to put myself in Aaron's situation to challenge them.) I think they can only be enforced at the cost of physical ownership rights and I'm a "law-as-code" kind of guy. I want to be able to believe that if someone didn't want me to copy something, I wouldn't be able to copy it, or I at least want us to admit that making a copy can't actually hurt someone (the copy itself, not what you might proceed to do with it).
- pbhjpbhj 14y agoThanks for your response, I'll keep this brief but I want to correct a few apparent misconcetions. >I am saying a MAC was not an identity to begin with // That's not important. The person accessing the system realised that it was being used to enforce a per person limitation. They spoofed MAC in order to misidentify their access. That misidentification was it appears to acquire documents in an attempt to publish them against the will of the license holders. I'm pro-copyright and patent as I genuinely believe that they are required to ensure proper compensation of authors/inventors. I use CC-BY primarily, which is facilitated by copyright. However, what I'm absolutely against is copyright or patent terms that don't stimulate innovation or artistic creation. Terms should be no more than about 9 years for either. >Turns out we want to monetize copying instead, so we are reducing individual freedoms and access rights. // We need fair exchange. Producing copyright works costs just like producing food or goods. Unless you give food, drink, shelter, etc., free to artisans then you can't demand their work to be free. Quid pro quo. I am absolutely sympathetic to the idea of releasing JSTOR data, indeed any and all scientific data, and applaud the apparent sentiment. But I'm not about to overlook the pretty obvious truth in order to promote that position - releasing JSTOR's data to the public would be a highly damaging commercial act. Morally justifiable IMO but certainly against the law. So, was aaronsw guilty, it appears certain from what I've read of the case that he was. >but looking onto a property (a physical computer) is not a crime // Fixing an image from a private property is in many jurisdictions (not sure on USA, most likely it's situationally variable). You're creating a false equivalence in any case, having your IP address is looking at your property from afar, logging in to your SSH and taking your files is picking the lock (or swinging the gate open) and walking in and taking something. Which brings us back to authorised. Unauthorised is "not authorised", that may seem pedantic truism but it moves towards the next point. Just because my door is wide open doesn't mean you have the right to access my house, you are authorised by active assent not by failure to prevent access. Running sshd with a weak password doesn't mean I'm authorised to access your computer, I'm clearly not authorised, I could perhaps run an exploit on it or brute-force it but that doesn't make me authorised to access it. If you truly hold the position you're espousing then presumably if someone takes money from you you'd consider it "authorised" because you failed to prevent them?
- 14y ago