Group items tagged

In spite of its new whizz-bang CEO, Prudential is a slow-moving but very reliable organization with a level of integrity that is trusted by policyholders. Frankly, that's what you want in an insurance company. I have had a modest U.K. pension with one of its competitors since 1980, and I am constantly worried that some leveraged buyout (LBO) artist will step in, take it over, change the computer system so that information gets lost, outsource customer service, and drive the company into bankruptcy. If you're buying life insurance or pension services, you want a company that's not going to disappear in the next 30 years, and doesn't change its address or computer system too often. Avoid a company like the plague if it is run by whiz kids. However, that's what AIG was like. We know how AIG operated; a guy who thought betting the ranch on the credit default swap market was a good idea ran it. Its Asian operation is no doubt full of similarly clever ideas. Even in the unlikely event that everything there is on the level, the cultural clash with an old-fashioned British insurance company is huge. And why would you pay a PREMIUM for an AIG operation? Like the Kraft/Cadbury deal, Prudential's takeover of AIA is value-destroying. Also like Kraft/Cadbury, it looks likely to destroy a valuable part of the British economy that millions of people have relied upon for generations - only this time the destruction will be caused by the buyer rather than the target. As shareholders we need a new form of corporate governance. Those in management are hired hands. In the old days, large shareholders used to treat management as they would have treated their butler - and management was equally deferential to the owners of substantial percentages of the company's capital. That's how capitalism is supposed to work - with resources deployed in the interests of the owners of capital. We know that system works; economics shows us why it works. The alternative, with resources deployed to satisfy the egos and fill the pockets of the hired hands, has no theoretical justification and little practicality - just as a big country house run in the interests of the butler would be a mess. As capitalists, we must work together to restore capitalism!

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.

Bloomberg.com has reported that the Obama administration is planning to launch an official complaint against China with the World Trade Organisation (WTO) pertaining to the country's stringent web censorship policies. Illinois Senator Richard Durbin has announced that he plans to pass a legislation that will allow the government to prosecute US internet companies if they violate the human rights of their customers when a foreign government asks them to do so. 

Stack was upset that §1706 did precisely what it was designed to do: Deprive him of the chance to exploit independent contractor status to avoid paying taxes through non-filing or through the understatement of income, overstatement of deductions, and avoidance of income tax withholding. In spite of the overwhelming advantages attendant to employee status, Joe Stack desperately wanted to be treated as an independent contractor for one simple reason: It would have made his tax protesting easier.4 Footnotes: ¹  We have met many taxpayers who worked as independent contractors for years without so much as a peep of protest until they realized, ex post facto, that it might have better for them to have been treated as employees. In our experience, workers tend to be content with their independent contractor status until one of the following happens: They get fired or quit They get hurt on the job They get sued for something they did while on the job They need a bank loan (and employment verification)  ²  If Stack had been an independent contractor and was subsequently “fired” by his principal, my hunch is it would have taken him less time to file a claim for unemployment compensation than it takes Apolo Ohno to finish short track. ³  Indeed, §1706 was included in TRA ‘86 because the CBO had estimated that the government was losing up to 30% of taxes because independent contractors were either not reporting all of their income on their tax returns or were claiming fraudulent or questionable deductions against that income. 4   Like all tax protestors, Stack knew that once the IRS had collected his taxes through payroll withholding it would never give it back to him based on previously refuted tax protestor arguments. Consequently, his only chance of avoiding taxes was to control his own tax payments and then use his frivolous arguments to evade or at least defer paying taxes.