<div id="popup_box_thanks" style="display:none" onClick="close_popup_thanks('popup_box_thanks', 'ts')"><br>Thanks for submitting your tip! All submissions are moderated by an editor before appearing online. We've reset the form so you can enter another tip. Or you can close the tip submission box. <div class="x_close" id="thanks_upper_right"><a href="javascript:void(0)" onmousedown="close_popup_thanks('popup_box_thanks', 'ts'); return true;">Close</a></div></div>
<div class="tbf_row"><div class="tbf_wide_extra_top not_bold">Please submit only technical tips that will help other TidBITS readers better use their Macs, iPhones, and related software and hardware. All product announcements should be sent to <a href="mailto:releases@tidbits.com">releases@tidbits.com</a>.</div></div>
<div class="tbf_left">URL</div><div class="tbf_right"><input type="text" value="" name="tip_link_url" tabindex="3"><span class="tip_description"><br>Enter the URL to a Web page that supports your tip.</span></div>
</div>
<div class="spacer"></div>
<div class="tbf_row">
<div class="tbf_left">Linked text</div><div class="tbf_right"><input type="text" value="" name="tip_link_label" tabindex="4"><span class="tip_description"><br>Enter the name of the page linked above.</span></div>
<div class="tbf_wide"><input type="submit" value="Preview Your Tip" name="preview_tip" onClick="fill_preview('tipbits_enclosure_preview', 'ts', this.form); return false;" tabindex="7"> <input type="submit" value="Send Us Your Tip!" name="submit_this_tip" onClick="handle_tip_submission('ts', '', this.form, 'tip'); return false;" tabindex="8"></div>
</div>
<div class="spacer"></div>
<div class="tbf_row">
<div class="tbf_wide"><span class="fine_print">When you submit a tip, you give us permission to use it. Read <a href="javascript:void(0)" onClick="generic_show_hide('tip_terms')">our terms</a> for more details. All submissions are reviewed before publication.</span></div>
<div class="tbf_wide"><span class="fine_print">Our terms: By submitting a tip, you agree to assign TidBITS Publishing Inc., a non-exclusive, worldwide, perpetual license to reproduce, publish, and distribute your tip in connection with the TidBITS Web site and associated products in any media. You agree that you created the content you submitted, and that you have the right to assign us this license. You give us permission to use your name, but your email address won't be publicly displayed or shared. We review all submissions before publication, and reserve the right to select which submissions we feel are appropriate for our readers and to edit those we publish.</span></div>
<div id="comment_thanks" style="display:none" onClick="close_popup_thanks('comment_thanks', 'comm')"><br>Thanks for submitting a comment! Please check your email for a link that, when clicked, will verify that you're a real person and cause your comment to appear immediately. <div class="x_close" id="comment_upper_right"><a href="javascript:void(0)" onmousedown="close_popup_thanks('comment_thanks', 'comm'); return true;">Close</a></div></div>
<div class="tbf_wide"><span class="fine_print">Our terms: We reserve the right to edit or delete any comment, so please post thoughtfully. We use your email address <i>only</i> to send you a one-time verification message confirming that you posted this comment. We also store your address to allow you to verify using other Web browsers in the future. For more info, see our <a href="http://db.tidbits.com/privacy.html">privacy policy</a>.</span></div>
<li><a href="/feeds/tidbits.rss" title="Subscribe via RSS" class="gettb">RSS <img src="/images/feed-icon-12x12.gif" width="12" height="12" border="0" class="nav_img" alt="Subscribe via RSS"></a></li>
<li><a href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=276986548" title="Subscribe to the podcast" class="gettb">Podcast <img src="/images/feed-icon-12x12_podcast.gif" width="12" height="12" border="0" class="nav_img" alt="Subscribe to the postcast"></a></li>
<li><a href="http://www.twitter.com/TidBITS" title="Get Article Updates via Twitter" class="gettb">Twitter <img src="/images/feed_icon_12x12_twitter.png" width="12" height="12" border="0" class="nav_img" alt="Get Article Updates via Twitter"></a></li>
<li><a href="http://www.facebook.com/pages/TidBITS/195314925519" title="Go to the TidBITS Page at Facebook" class="gettb">Facebook <img src="/images/feed_icon_12x12_facebook.gif" width="12" height="12" border="0" class="nav_img" alt="Go to the TidBITS Page at Facebook"></a></li>
<li><a href="javascript:void(0)" title="Sections" class="tabhead" onClick="return showhide('articleslist')">Sections <span id="articleslist_triangle"><img src="/images/nav_triangle_open.gif" width="9" height="9" border="0" class="navtriangle" id="articleslist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" onClick="return showhide('stafflist')" title="Staff" class="tabhead">Staff <span id="stafflist_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="stafflist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" title="Issues" class="tabhead" onClick="return showhide('issuelist')">Weekly Issues <span id="issuelist_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="issuelist_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="javascript:void(0)" onClick="return showhide('abouttidbits')" title="About TidBITS" class="tabhead">About TidBITS <span id="abouttidbits_triangle"><img src="/images/nav_triangle_closed.gif" width="9" height="9" border="0" class="navtriangle" id="abouttidbits_tri_image" alt="Click to show or hide the contents of this section."></span></a></li>
<li><a href="http://www.thedatarescuecenter.com/">The Data Rescue Center</a></li>
</ul><div class='sponsor_sidebox_bottom'> </div>
</div>
<!-- end sponsor_sidebox -->
</div> <!-- end leftcolumn div -->
<!-- end left column -->
<!-- begin centercolumn_border -->
<div id="centercolumn_border">
<div class="center_top">Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling <a href="http://www.takecontrolbooks.com/?pt=TB-TAGLINE" style="color:yellow">Take Control</a> ebooks.</div>
<!-- begin centercolumn -->
<div id="centercolumn">
<!-- begin rightcolumn_container -->
<div id="rightcolumn_container">
<!-- begin rightcolumn -->
<!-- rightcolumn is embedded within centercolumn so featured text wraps around it -->
</div><!-- end tearoffbox_wide_container for watchlist items -->
<!-- begin tearoff box wide -->
<div class="tearoffbox_wide_container">
<div class="tearoffbox_wide_tips">
<div class="tip_display">
<div class="tips_sponsor_logo">
</div>
<h6>Enabling Auto Spelling Correction in Snow Leopard</h6>
<p><p>In Snow Leopard, the automatic spelling correction in applications is not usually activated by default. To turn it on, make sure the cursor's insertion point is somewhere where text can be entered, and either choose Edit > Spelling and Grammar > Correct Spelling Automatically or, if the Edit menu's submenu doesn't have what you need, Control-click where you're typing and choose Spelling and Grammar > Correct Spelling Automatically from the contextual menu that appears. The latter approach is particularly likely to be necessary in Safari and other WebKit-based applications, like Mailplane.</p></p>
</div>
<div class="tearoffbox_wide_bottom_tips">
<div style="padding-bottom:35px"><div class="tip_display" style="float:left"><p><br><a href="/tipbits/205">Link to this tip</a></p></div><div class="tip_display" style="float:right; width:150px">
<div class="tbf_wide_80" id="hc_rc_4712">To help us avoid automated posts and misuse of our site, please enter the words below.</div><div class="x_close_row" id="hc_upper_right2_4712"><a href="javascript:void(0)" onmousedown="HidePopupContent('hc_4712', 'hc', '4712'); return true;">Close</a></div>
<div class="featured_meta"><div class="meta_article">07 Aug 2000 | <a href="/article/6070?print_version=1">Print <span class="shift_up"><img src="/images/printer_icon.gif" alt="Printer-Friendly Version of This Article" border="0" width="9" height="10"></span></a></div></div>
<div id="article_box_4712"><P>Apple Computer announced last week that it has sued up to twenty-five anonymous defendants for posting information on the Internet that Apple considers to be proprietary trade secrets. The complaint, filed in a California state court (Superior Court for Santa Clara County, where Apple's headquarters is located), seeks "an injunction against further disclosure of Apple's trade secrets as well as monetary damages."</P><P><<A HREF="http://www.apple.com/pr/library/2000/aug/2lawsuit.html">http://www.apple.com/pr/library/2000/aug/ 2lawsuit.html</A>></P><P>Although I had not received a copy of the actual complaint by press time, published reports and sources indicate that Apple is suing "John Doe 1" for acting, alone or in conspiracy with up to 24 other anonymous defendants ("John Does 2 through 25"), to post confidential information about the Power Macintosh G4 (Gigabit Ethernet) and Apple Pro Mouse before those products were announced. In conjunction, Superior Court Judge Gregory H. Ward issued a subpeona to Yahoo seeking identifying information on two GeoCities Web sites where Apple trade secrets were allegedly posted. (GeoCities is a division of Yahoo Incorporated.)</P><P><<A HREF="http://db.tidbits.com/article/06049">http://db.tidbits.com/article/06049</A>></P><P>The concept of suing unknown individuals over revealing truthful information can be confusing, so let's briefly walk though exactly what's happening.</P><P><STRONG>Why Apple Cares</STRONG> -- MacNN's report on the lawsuit includes quotations from the complaint Apple filed. (Other reports are available from CNET, TechWeb, and ZDNN.) In part, the complaint says, "In Apple's experience, public knowledge of future products often lessens sales of existing Apple products. As a result, Apple maintains and protects Future Product Information as a trade secret." Any semi-serious Macintosh watcher knows that Apple keeps details of unreleased products as secret as possible, but sometimes people think this is merely so Steve Jobs can surprise an audience with new product announcements. It's more involved than that.</P><P><<A HREF="http://www.macnn.com/feature.php?id=101">http://www.macnn.com/feature.php?id=101</A>><BR><<A HREF="http://news.cnet.com/news/0-1006-200-2416345.html">http://news.cnet.com/news/0-1006-200- 2416345.html</A>><BR><<A HREF="http://www.techweb.com/wire/story/TWB20000802S0022">http://www.techweb.com/wire/story/ TWB20000802S0022</A>><BR><<A HREF="http://news.excite.com/news/zd/000802/15/apple-says-trade">http://news.excite.com/news/zd/000802/15/apple- says-trade</A>></P><P>The personal computer industry learned early on that being too forthcoming about future plans can affect the present. The Kaypro computer company set the classic example way back in the early 1980s - by revealing details of a hot new machine too far in advance, sales of the company's existing (and only) model dried up, and delays in the new model left the company with virtually no sales for well over a year. In addition, by the time Kaypro did get its new model out the door, the competition - well-informed of what they could expect - had already nullified most of its competitive advantages. Kaypro held on for another year or two before collapsing completely.</P><P>Apple has seen this effect as well, and not just in ancient history. In the just-ended third quarter of fiscal year 2000, Apple posted smaller-than-expected revenues and unit sales, largely due to iMac sales that failed to meet predictions. Apple saw early in the quarter that iMac sales were slowing down, and when analysts asked, Apple CFO Fred Anderson said the company believes it was because iMac customers were waiting for new models - by the end of the quarter, it had been nine months since the last update, when previous updates had come at no more than six-month intervals. Although Apple's quarter was strong in all other respects, that dip in iMac sales was enough to spawn a string of "Is Apple's Recovery Faltering?" stories, potentially starting the same kind of self-fulfilling prophecy cycle that sent Apple into the toilet in 1996 and 1997. (You may remember that although Apple had serious business practice issues that needed repair, sales did not drop until the public was deluged with "Apple Is Doomed" stories.)</P><P>Given the unique nature of products like the Power Macintosh G4 Cube and the plethora of stories leaking out well ahead of the machine's announcement - and the observable and repeated effect advance knowledge can have on Apple's business - the company has apparently decided to play hardball. Apple is already extremely strict with employees who are believed to have leaked information, but in some recent cases, Apple has not been able to find out who's responsible for the leaks. That's where the lawsuit comes in.</P><P><STRONG>Anonymous Defendants</STRONG> -- It seems counter-intuitive to file a lawsuit when you don't know who you're suing. Yet part of the legal process is called <EM>discovery</EM>, where attorneys for each side query and, via the jurisdiction of the court, subpoena relevant witnesses in an effort to uncover truth. Discovery compels witnesses to answer questions under oath and to surrender information that, without the court's backing, third parties would never have to reveal.</P><P>By filing against unknown persons, Apple is essentially representing to the court that with the full weight of discovery, Apple will be able to determine who the defendants are reasonably quickly, and then will amend the complaint to name them explicitly. That's not an optional step - it's not fair to let Apple conduct volumes of discovery with witnesses when the individuals being sued haven't even been notified of the lawsuit, and they can't be served with papers until they're named. (By contrast, consider that criminal charges are rarely filed anonymously in the U.S. - courts frown on the full power of the police not being able to name a defendant, viewing anonymous charges as end-runs around statutes of limitations.)</P><P>Look at it from Apple's point of view. Accurate and confidential information belonging to Apple was posted on the Internet, and the only people who had access to it were under contractual obligation not to reveal it - either as employees of Apple Computer or as third-party developers or business partners who had signed non-disclosure agreements. Someone, or some entity like a corporation, broke a contract by either posting that information or permitting that information to come into possession of a third party who posted it (although in the suit, Apple warrants that it has been informed and believes that John Doe 1, the primary defendant, the one who actually posted the information, is an individual). Apple has legitimate legal cause against that individual, but it has to use discovery to find out that person's name.</P><P>That's why Apple immediately had Yahoo served with subpoenas for identifying information about two accounts allegedly used to post confidential information on AppleInsider's bulletin boards. Yahoo may not have correct name and address information for those Web sites or email accounts, but it should have logs of the IP addresses that the owner used to access them. Apple is hoping those addresses will be Apple's own static IP addresses in its class A address space (17.x.x.x); the company will then map the address back to a specific connection, see who owned it at that period in time, and voila! They've found the culprit.</P><P><<A HREF="http://forums.appleinsider.com/cgi-bin/Ultimate.cgi?action=intro">http://forums.appleinsider.com/cgi-bin/ Ultimate.cgi?action=intro</A>></P><P>If the IP address belongs to a cable modem, DSL, or even a dial-up modem pool, Apple can then have the ISP subpoenaed to match the IP address at the time the site was created to a given customer record, and that leads to the name of the defendant as well.</P><P><STRONG>Apple's Real Goal</STRONG> -- Once Apple has figured out who leaked the information, I believe that will be the end of the lawsuit. Rather than go to the expense of a trial in a futile attempt to recover money the leaker probably doesn't have, Apple wants to know who it is so he can be cut off. He'll be fired for breach of contract if he works for Apple. If he works for a third-party developer or business partner, Apple will pressure that company to fire the leaker as well, upon threat of not getting any more information from Apple or facing a corporate breach-of-contract suit for violating the non-disclosure agreement.</P><P>If Apple had intended to go after the sites that published the information, the company might not have filed a California state lawsuit. California has a state shield law that allows reporters to refuse to divulge their sources in civil court proceedings with less fear of being held in contempt of court. The law does not specifically include Web publications, but neither does it specifically exclude them. Either way, the shield law would be an obstacle to Apple's discovery, defeating the main purpose of filing a complaint. What's more, the two major rumor sites are both located on the East Coast of the U.S. - AppleInsider with MacNN in Washington, DC, and Mac OS Rumors in Portland, ME. Since California courts have no power to subpoena people more than 50 miles away from where a hearing is held, both sites are by definition outside the jurisdiction of the lawsuit.</P><P><<A HREF="http://www.gulker.com/ppagla/mediaguide/04shield.html">http://www.gulker.com/ppagla/mediaguide/ 04shield.html</A>></P><P><STRONG>That First Amendment Again</STRONG> -- When Adobe sued MacNN in late May for misappropriation of Photoshop 6 trade secrets, Adobe took a big PR hit from angry Macintosh users. Some felt Adobe was trying to punish Web sites for its own inability to keep information confidential; others felt it was an abuse of the U.S. First Amendment that grants freedom to the press. In MWJ, we pointed out that no matter how MacNN got the information, the site probably had a First Amendment right to publish it at that point.</P><P><<A HREF="http://db.tidbits.com/article/05977">http://db.tidbits.com/article/05977</A>></P><P>Apple, having learned from this dust-up, is going after the people who leaked the information in the first place, not those who published it on the Web. Such a tactic avoids the entire messy issue, with one possible exception: once identified, the defendant could assert that because he posted the information on his own GeoCities Web site, he himself is a publisher. He could then maintain that he got the information from someone else and try to invoke something like the shield law to keep that person's identity secret. However, if the webmaster is an Apple employee or employee of an Apple business partner, Apple will still fire him or pressure for him to be fired, arguing that even if this person didn't create the pictures, he surely should have known they were Apple trade secrets. Apple achieves its goal either way.</P><P>The strategy also prevents the rumor sites from facing an uncomfortable choice in Federal court - reveal sources or potentially be held in contempt. In the 03-Aug-00 edition of the Wall Street Journal, Piu-Wing Tam quotes Sydelle Pittas, attorney for Ric Ford's MacInTouch, as saying that Apple's action against the anonymous source was just fine. "Apple has a perfect right to go after anyone it feels has violated a confidentiality agreement," she said. Pittas's comments probably shouldn't be construed as MacInTouch policy towards legal action on sources, but without the protection of something like the California shield law, a publisher risks jail when protecting an anonymous source. That's a tough choice.</P><P>Ironically, had someone leaked information to a traditional media reporter (newspaper, television, magazine) in the state of California, his identity might be beyond Apple Computer's legal reach. But by posting in public forums with an identifiable account, the leaker has apparently removed the Web sites from the loop - they're not even asked to divulge his identity because he left enough clues for Apple to find him via subpoenas. Remember that if you're tempted to bargain your conscience and your contracts for a shot at fleeting Web fame.</P><P>[Matt Deatherage is the publisher of MDJ, MWJ, and MMJ - daily, weekly, and monthly subscription-based newsletters for serious Macintosh users. Free trial subscriptions for all three are available. The trial subscription to MMJ contains the full MDJ Power 25 articles in which TidBITS Publisher Adam C. Engst ranked #2 behind Steve Jobs.]</P><P><<A HREF="http://www.macjournals.com/">http://www.macjournals.com/</A>></P><!-- Apple Gets Serious About Plugging Leaks Matt Deatherage --></div>
<!-- end article text -->
<!-- PayBITS -->
<p> </p><div class="sponsorbox">
<div class="sponsortext"><A HREF="http://www.smithmicro.com/tidbits"><IMG SRC="http://db.tidbits.com/images/badges/StuffItDeluxe2010.gif" ALT="" HEIGHT="50" WIDTH="50" BORDER="0" ALIGN="left"></A>StuffIt Deluxe 2011 has everything you need to backup, encrypt,<br />share, and compress all of your photos, audio and documents.<br />Compress it. Secure it. Send it. Try StuffIt Deluxe 2011 today!<br />Click here for a free 30-day trial: <<a href="http://stuffIt.com/tidbits/">http://stuffIt.com/tidbits/</a>></div>
