Group items tagged

The "Facebook Subpoena/Search Warrant Guidelines" from the Cryptome site are dated 2008, so there's a chance they've been superseded. The document spells out how law enforcement and intelligence agenices should go about requesting information about Facebook users, and details what information is turned over. Following is what Facebook will turn over about you, taken verbatim from the guide: Types of Information Available User Neoprint The Neoprint is an expanded view of a given user profile. A request should specify that they are requesting a “Neoprint of used Id XXXXXX”. User Photoprint The Photoprint is a compilation of all photos uploaded by the user that have not been deleted, along with all photos uploaded by any user which have the requested user tagged in them. A request should specify that they are requesting a “Photoprint of user Id XXXXXX”. User Contact Info All user contact information input by the user and not subsequently deleted by the user is available, regardless of whether it is visible in their profile. This information may include the following: Name Birth date Contact e-mail address(s) Physical address City State Zip Phone Cell Work phone Screen name (usually for AOL Messenger/iChat) Website With the exception of contact e-mail and activated mobile numbers, Facebook validates none of this information. A request should specify that they are requesting "Contact information of user specified by [some other piece of contact information]". No historical data is retained. Group Contact Info Where a group is known, we will provide a list of users currently registered in a group. We will also provide a PDF of the current status of the group profile page. A request should specify that they are requesting "Contact information for group XXXXXX". No historical data is retained. IP Logs IP logs can be produced for a given user ID or IP address. A request should specify that they are requesting the "IP log of user Id XXXXXX" or "IP log of IP address xxx.xxx.xxx.xxx". The log contains the following information: * Script – script executed. For instance, a profile view of the URL http://www.facebook.com/profile.php?id=29445421 would populate script with "profile.php" * Scriptget – additional information passed to the script. In the above example, scriptget would contain "id=29445421" * Userid – The Facebook user id of the account active for the request * View time – date of execution in Pacific Time * IP – source IP address IP log data is generally retained for 90 days from present date. However, this data source is under active and major redevelopment and data may be retained for a longer or shorter period. Special Requests The Facebook Security Team may be able to retrieve specific information not addressed in the general categories above. Please contact Facebook if you have a specific investigative need prior to issuing a subpoena or warrant.

Comcast The Comcast document is labeled "Comcast Cable Law Enforcement Handbook," and is dated 2007, so there's a possibility that it, too, has been superseded. As with the other documents, it explains how law enforcement agenices can get information, and details what information is available. There's a great deal of detail in the 35-page document, which describes what Internet, phone, and television information will be turned over. For example, here's the IP information it will make available: Comcast currently maintains Internet Protocol address log files for a period of 180 days. If Comcast is asked to respond for information relating to an incident that occurred beyond this period, we will not have responsive information and can not fulfill a legal request. (Comcast can process and respond to preservation requests as outlined below in this Handbook.) As expected, Comcast will also turn over the emails, including attachments, of those who use Comcast's email service, but "In cases involving another entity’s email service or account, Comcast would not have any access to or ability to access customer email in response to a legal request." Information Comcast turns over to law enforcement agencies varies according to the request. For example, a grand jury subpoena will yield more information than a judicial summons, as you can see in the excerpt below. Comcast notes, though, that this is just a sample, and that "Each request is evaluated and reviewed on a case by case basis in light of any special procedural or legal requirements and applicable laws." So the examples "are for illustration only."

For those who worry about privacy, though, all of this information is small potatoes. The real worry is about the use of what are called pen registers or trap-and-trace devices, which essentially capture all of your Internet activity --- the Web sites you visits, the emails you send and receive, IM traffic, downloads, and so on. Here's what the document says about them: Pen Register / Trap and Trace Device Title 18 U.S.C. § 3123 provides a mechanism for authorizing and approving the installation and use of a pen register or a trap and trace device pursuant to court order. All orders must be coordinated prior to submission to Comcast. Law enforcement will be asked to agree to reimburse Comcast's reasonable costs incurred to purchase and/or install and monitor necessary equipment. See "Reimbursement," below.

In his decision, Judge Robert Cleland said that CAN's case "must fail" because the company did not provide evidence that White had intended to profit from the domains. He did acknowledge, however, that White made some attempt to damage CAN's business by climbing the search rankings, but that it was only to warn other potential customers—an action that is protected under the First Amendment. Because White's websites didn't represent themselves as the real company websites for CAN and they provided accurate contact information, they were clearly gripe sites and did not infringe on CAN's marks. As noted by TechLaw, the ruling included some extra details about what is required (or in this case, not required) to qualify as a "gripe site." careeragentsnetworks.biz did not include a disclaimer stating that it is not affiliated with CAN, for example—something that many gripe sites do for the explicit purpose of avoiding lawsuits like this—but that didn't make a difference in the ruling. The decision has been applauded as a victory for the First Amendment, but is a frustrating one for trademark holders. Companies have been notoriously unhappy with the existence of gripe sites, though not everyone gives into legal threats. In 2007, we covered a case involving an Ars reader who was fighting a legal battle against Lowe's over his site, lowes-sucks.com, and in 2009, Goldman Sachs made headlines for trying to bully the creator of Goldmansachs666.com into shutting the site down. When we spoke with EFF staff attorney Corynne McSherry in 2007, she told us that the courts have been clear that "gripe sites like this are protected—in fact, they want people to speak freely and share information about their experiences with various companies." As long as they don't represent themselves as the real company, it seems the courts are still on the side of dissatisfied consumers.

University of Edinburgh law lecturer Andres Guadamuz wrote a blog entry this week highlighting some particularly troubling aspects of the IIPA's 301 recommendations. The organization has condemned Indonesia and several other countries for encouraging government adoption of open source software. According to the IIPA, official government endorsements of open source software create "trade barriers" and restrict "equitable market access" for software companies. The profound absurdity of this accusation is exacerbated by the fact that Indonesia's move towards open source software was almost entirely motivated by a desire to eliminate the use of pirated software within the government IT infrastructure. It's important to understand that Indonesia has not mandated the adoption of open source software or barred government agencies from purchasing proprietary commercial software. The Indonesian government issued a statement in 2009 informing municipal governments that they had to stop using pirated software. The statement said that government agencies must either purchase legally licensed commercial software or switch to free and open source alternatives in order to comply with copyright law. This attempt by Indonesia to promote legal software procurement processes by endorsing the viability of open source software has apparently angered the IIPA. In its 301 recommendations for Indonesia, the IIPA demands that the government rescind its 2009 statement. According to the IIPA, Indonesia's policy "weakens the software industry and undermines its long-term competitiveness" because open source software "encourages a mindset that does not give due consideration to the value to intellectual creations [and] fails to build respect for intellectual property rights." The number of ways in which the IIPA's statements regarding open source software are egregiously misleading and dishonest are too numerous to count. The IIPA seems to have completely missed the fact that there is a very robust ecosystem of commercial software vendors in the open source software market and that open source software is at the heart of some of the most popular consumer electronics products that are sold in the United States. It has clearly become an important part of the US software economy and increasingly serves as an enabler of innovation and technological progress. In light of the profitability of Red Hat and other open source leaders, it seems absurd to contend that open source software adoption will weaken the software industry or reduce its competitiveness. In fact, the emergence of open source software has contributed to creating a more competitive landscape in the software industry by offering alternative business models that enable smaller companies to gain traction against the dominant incumbent players. The IIPA's position is profoundly hypocritical, because many parts of the US government, including the Department of Defense, have issued their own memos endorsing open source software adoption. The IIPA's disingenuous move to equate open source software with piracy reeks of desperation. The BSA and other IIPA members are likely losing sleep over open source software because that development model and approach to licensing will empower developing countries to build their own domestic IT industries, eliminating the need for them to tithe to American software giants. It's another failing of the 301 review, which Big Content wants used to coerce other countries into adopting ever-more-stringent copyright laws.