http://abstract.cs.washington.edu/wiki/api.php?action=feedcontributions&user=Yanokwa&feedformat=atomPublicWiki - User contributions [en]2024-03-29T07:37:00ZUser contributionsMediaWiki 1.27.4http://abstract.cs.washington.edu/wiki/index.php?title=Banks_in_Seattle&diff=7807Banks in Seattle2009-09-06T16:16:26Z<p>Yanokwa: adding chuck</p>
<hr />
<div>[[Seattle life]] -> '''Banks in Seattle'''<br />
<br />
The following banks have offices and ATMs near/on UW campus. Where possible, links into bank web sites are directly to WA state services information, but you know...dynamic pages happen. <br />
<br />
*[http://www.schwab.com/public/schwab/home/account_types/brokerage/schwab_one_with_ic.html Charles Schwab] High Yield Investor Checking is a good deal. FDIC insured, interest bearing and no ATM fees.<br />
*[http://www.usbank.com/uw US Bank] ([http://www.usbank.com/cgi/cfm/find_us.cfm? ATM/branch locator]) - US Bank is "The Only Bank on Campus" having a full service branch location in the Husky Union Building as well as 10 UW ATM locations. Student Checking accounts are no minimum balance/service fee accounts with free checks and free non-US Bank ATM transactions. See the branch for details or call/e-mail Tom Powell, Branch Manager @ 206.543.2407 [mailto:thomas.powelljr@usbank.com Tom Powell]<br />
*[http://www.bankofamerica.com/wa/deposits/?statecheck=WA Bank of America] ([http://www.bankofamerica.com/help/index.cfm?template=locators.cfm ATM/branch locator]) - There is an ATM in the HUB - near the Subway. There is a branch on the Ave. at 47th, ATMs on Ave. and at [http://www.uvillage.com/ U. Village shopping center] (Note: The ATMs listed which have "University Village" as their location did not map properly on the Bank of America site as of 8 Sep 2001. U. Village is located down the hill northeast of campus.) <br />
*[http://www.key.com/ Key Bank] ([https://keyextp1.keybank.com/scripts/ndpluginisapi.dll/kcoLocators/pgSearch?link=qlatmbr ATM/branch locator]) - branch just west of the Ave. on 45th, ATMs there and at U. Village<br />
*[http://yp.yahoo.com/py/ypMap.py?Pyt=Typ&tab=B2B&tuid=10491070&ycat=26767949&city=Seattle&state=WA&zip=98105&country=us&slt=47.663101&sln=-122.299797&cs=5&ck=2649695907&stat=:pos:5:regular:regT:12:fbT:0 United Savings & Loan Bank] - branch two blocks west of the Ave. on 45th <br />
*[http://www.wamu.com/ Washington Mutual] ([http://clients.mapquest.com/wamu/mqlocator?screen=find&link=map&queryRadius=500&queryMax=5&queryUseOrigin=1&queryCenterOrigin=1&closestn=5&closestprox=1&miles=500&type=main&country=US&sqlcol1=ATM&sqlcnd1=like&sqlcol2=OFF_TYPE&sqlcnd2=like&sqlcol3=OFF_TYPE&sqlcnd3=like&sqlcol4=OFF_TYPE&sqlcnd4=like&sqlcol5=NAME&sqlcnd5=like&sqlval1=Y&sqlval2=FC&sqlval5=%25&streetaddress=&city=&state=&zip=98105&map_display=true ATM/branch locations]) - branch on Brooklyn Ave. (one street west of the Ave.) at 43rd, ATMs there and at U. Village <br />
*[http://www.wastatecu.org/ Washington State Employees Credit Union] ([http://www.wastatecu.org/x289.xml branch] and [http://www.cs.washington.edu/homes/toomim/map/ ATMs]) - Free access to any Credit Union's ATMs. (4 ATMs <1 mile from campus and ~100 downtown) - U. District branch, ATM, and drive-through on NE 45th St at 11th Ave NE (Intel Research Seattle building), ATM at the HUB near the etc. convenience store, see [http://www.cs.washington.edu/homes/toomim/map/ GoogleMapsATMs] or [http://www.co-opnetwork.org/public/consumers/index.cfm ATMs] for a complete list & map of free credit union ATMs. Students are eligible to join WSECU, plus most grad students are TAs or RAs, so technically we're state employees, too.<br />
*[http://www.wellsfargo.com/per/personal_finance.jhtml Wells Fargo Bank] ([http://www.wellsfargo.com/help/find_us.jhtml ATM/branch locator]) - branch on Ave. at 45th, ATMs there and lower on the Ave. at 41st<br />
*[http://www.becu.org/ Boeing Employees Credit Union] - All students are eligible. There's a branch on the Ave and as of 8 / 09 there's one Coming Soon! on 25th Avenue just above Blakeley.<br />
<br />
Banks not quite right near campus:<br />
<br />
* [http://www.homestreetbank.com/ HomeStreet Bank] - There's a branch at 35th and 82nd NE. I ended up closing my account because I wanted to transfer in and out electronically for free, and they told me I could and then it turned out there was a fee. So I'm not impressed. But if that doesn't matter to you, you could feel good about supporting a local bank that claims to do lots of community service. -- eherbst</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Optometrists_in_Seattle&diff=7609Optometrists in Seattle2009-02-18T21:45:01Z<p>Yanokwa: </p>
<hr />
<div>==Optometrists recommendations/information==<br />
<br />
====Yaw Anokwa, 02-18-2009====<br />
just plugging Bursett Optometry again. they allowed me to return a set of glasses even after i had purchased them. how awesome is that?<br />
<br />
====Tamara Denning, 07-April-2008====<br />
Another good experience with Bursett Optometry. I did have difficulties finding their building and parking garage the first time around, though.<br />
<br />
====Yaw Anokwa, 24-May-2007====<br />
Another thumbs up for Bursett Optometry.<br />
<br />
====From: Jochen Jaeger <jj@cs.washington.edu>====<br />
<br />
As it is only a 5 min walk away from SIEG I went to the<br />
University Vision Clinic (4115 Univ. Way, N.E, Suite 101).<br />
The team there was very nice and I got a thorough eye<br />
examination (took roughly one hour). First his assistant<br />
did some basic examination/questions and then Dr. Hovander<br />
continued with glass fitting and some more examinations.<br />
He patiently and competently answered all questions I had<br />
and did not push me to buy anything.<br />
I would recommend him.<br />
Only drawback. Instead of the 10$ out of pocket money<br />
I had to pay 20$ as the examination costs apparently<br />
70$ and the insurance only covers 60$ (from which you<br />
have to pay already 10$).<br />
<br />
====04 Feb 2002 Vibha Sazawal <vibha@cs>====<br />
<br />
For an OPTHAMOLOGIST...<br />
<br />
Brian Carey<br />
Seattle Eye M.D.s<br />
6th & Pine (downtown)<br />
<br />
http://www.eyemds.net<br />
<br />
Glasses only is $130, but only $100 if it's your first visit<br />
and if you don't want to claim any insurance. Contacts are<br />
$180?<br />
<br />
They test for glaucoma, retinal detachment,<br />
cataracts...things you should only worry about if you have<br />
family history. <--- This is a mis-conception ... family history of ocular disease increases a person's risk factor for getting the disease, but it does not completely rule out the possiblity of the person getting the disease. People are still advised to get annual eye exams to catch any problems before it advances. <br />
<br />
Don't go to the hospital just 'cause it's cheaper. You<br />
might just get a clueless resident.<br />
<br />
====24 Sep 2004 yasuhara====<br />
<br />
FYI a ton of CSE folks (myself included) continue to see Dr. Bursett (as commented on below), but she did move her office to the east side---no longer in the U. District. The new address and phone are 13715 Bel Red Rd, Bellevue, WA 98005, (425) 401-2020.<br />
<br />
UPDATE: Actually Ken, she moved back to the west side (Eastlake to be precise)...yay! Jessica<br />
<br />
UPDATE: Dr. Bursett's Current Contact Info:<br />
2323 Eastlake Avenue East<br />
Seattle, WA 98102 <br />
206-632-2237 -- kate<br />
<br />
====26 October 2000 Rachel Pottinger (rap@cs)====<br />
<br />
I recommend Bursett Optometry, 206-632-2237, 4545 15th Avenue NE #207;<br />
they know all about the insurance and had contacts for me on the spot,<br />
which has never happened to me before. I got out of there with a new<br />
pair of contacts for $24. She's used by about half the people in my<br />
office (224).<br />
<br />
====Craig Kaplan, Sep 2001====<br />
<br />
Lisa Bursett at 45th and 15th. She has a sixth sense for<br />
immediately choosing the one set of frames that's perfect<br />
for you, even if you didn't realize how good they were.<br />
<br />
==Advice for those looking for an optician if you have already have a prescription:==<br />
<br />
====9 Oct 2000 Ashish Sabharwal====<br />
<br />
I got new glasses a week ago from Colaizzo Opticians (1623 Queen Ann Ave N.).<br />
I think they have a better collection than the few shops I tried in<br />
U-district, especially if you want something "different" :)<br />
<br />
<br />
====9 October 2000 Adam Macbeth====<br />
<br />
I went to the place on the Ave (across from the bookstore) and they did a<br />
pretty good job.<br />
<br />
====6 October 2000 Gerome Miklau====<br />
<br />
There's kind of an upscale place in U Village that sells stylish<br />
frames. It's in the inner courtyard-type part of the mall. <br />
<br />
====6 October 2000 Ka Yee Yeung====<br />
<br />
I'm personally a big Costco fan. They sell glasses. But if you prefer a<br />
clinic-type of places, you can go to an optometrist.<br />
Oh, Costco is a lot less expensive, and we can claim our insurance even if<br />
we go to Costco.<br />
<br />
I have been terribly ribbed by some (bad) optometrists before. They<br />
charged me $150 for a pair of contact lenses. But I managed to get<br />
identical contact lenses at Costco for $40. But Costco probably doesn't<br />
carry very many fancy frames for glasses. <-- You must understand that Costco is a large corporation that is able to purchase and stock large quantities of contact lenses. They usually will get the bulk order of lenses at a reduced rate compared to private offices. This reduction is then passed onto the consumers. Private practices are not always readily able to make purchases that large, thus the cost for them is higher ... hence higher prices for the lenses.<br />
<br />
====6 October 2000 Steve Swanson====<br />
<br />
It depends on whether you want plastic or glass. I think everywhere pretty<br />
much does plastic. I am picky and wanted glass, and finally found that<br />
Eyes Right on the corner of the Ave and 46th or so (right next to futon of<br />
north america and catty corner from Costas) would do it. They deal with<br />
UW insurance I guess. Insurance got messed up with me, but I had some<br />
wierdness with the two insurance polcies I had at the time.<br />
<br />
If nothing else the guy that seems to own the place is really nice. <br />
<br />
====9 October 2000 Dan Grossman====<br />
<br />
I haven't had any experience with shops in Seattle, but I would caution<br />
that they are decidedly *not* all the same. Also, frame styles should not<br />
be your main criterion. One thing to pay attention to is the number and<br />
quality of technicians working there. When I first got glasses, it took<br />
several months and several adjustments before they were physically<br />
comfortable and properly functioning vision-wise. (Of course, I have<br />
bifocals, so that presents special difficulties.) If the store does not<br />
have a very helpful staff, you might get stuck paying for all sorts of<br />
adjustments you might have to make, not to mention the fact that your<br />
lenses might have flaws such as slight disparities in lens power, improper<br />
angle of insertion into the frames, etc.<br />
<br />
In my experience, you can tell a skilled and helpful technician by his/her<br />
grim determination to get the glasses looking, feeling, and "seeing" <br />
exactly right. Of course, most of this is exhibited *after* you've<br />
ordered the glasses, but you can also tell a lot by their attitude during<br />
the trying-on phase.<br />
<br />
====Optometrist/eyeglass shop recommentations from early April, 1997:====<br />
<br />
Marc Friedman <friedman>:<br />
<br />
(July 2, 1998)<br />
The least I can do is urge people NOT to go to Roosevelt Vision<br />
Clinic. I missed an appointment there, and paid their missed <br />
appointment fee on the spot. Nevertheless, they TERMINATED me as a<br />
patient without explanation and with no opportunity for rehabilitation.<br />
<br />
This may seem cost-effective to them, but it seems unprofessional to<br />
me. I mean, my car was stolen. But did they care? No. Don't go<br />
there.<br />
<br />
Dan Fasulo <dfasulo>:<br />
<br />
I recently got a couple of pairs of glasses from LensCrafters up at the <br />
Northgate mall. I didn't have time to comparison shop because I was in a <br />
hurry to replace some glasses that got left behind on a trip, but the <br />
salespeople were friendly and helpful and the glasses got made in an hour <br />
without a hitch. Their facilities seemed very modern.<br />
<br />
I also went to the on-site, independent optometrists, and, despite<br />
having fancier equipment than my hometown optometrist, they botched the<br />
prescription slightly the first time, which was annoying. On the other<br />
hand, they re-did the exam promptly and LensCrafters replaced the lenses<br />
for free. <br />
<br />
I also had to pick out frames since the old frames, along with the<br />
lenses, had been left behind in Colorado. :) The salesman was patient and<br />
helpful, and being a CS grad student, I *always* need help in identifying<br />
things that are fashionable. :) It seemed like a well-run place.<br />
<br />
Jack Lo <jlo>:<br />
<br />
I've gone to the Roosevelt Vision Clinic. It's been a good place for me to<br />
go. It's also on approved the grad student vision plan list, if you have<br />
grad student/appointee health insurance.<br />
<br />
Emin Gun Sirer <egs>:<br />
<br />
I have been going to Scott Jamieson at the Roosevelt Vision Clinic. He<br />
is competent and knowledgeable, and patiently answers all of my questions.<br />
He is affiliated with the student vision plan, so insurance picks up most<br />
of the costs. <br />
<br />
Amir Michail <amir>:<br />
<br />
I have had good experiences with Eye Associates Northwest. Their<br />
number is 206-386-2700. (However, my glasses are not "high powered".)<br />
<br />
Pat Tressel <tressel><br />
<br />
I tried for *years* to find someplace that could make even marginally<br />
usable high-diopter glasses, until...one of the dispensing opticians at<br />
the Virgina Mason clinic's optical shop ("Visual Effects" ;-) realized<br />
what was wrong. The prescriptions had always been filled with plastic<br />
lenses. But plastic has about half the index of refraction of glass,<br />
and the curvature required was so extreme with plastic that there was<br />
usually only one small region that was in focus. The optician ordered<br />
glass lenses, and -- voila! -- everything was in focus right to the<br />
edges of the lenses. So, no matter who you go to, don't let them talk<br />
you into plastic lenses. Instead, to keep the weight down, get frames<br />
with a small aperture. (You don't have to be a patient at Virginia<br />
Mason to have prescriptions filled at Visual Effects. They are likely<br />
more expensive than the mass-production shops. I have the vaguest of<br />
memories that the optician who helped me was named John.)<br />
<br />
I don't, unfortunately, know of an optometrist willing to take the time<br />
to work with low-vision patients. The last time I had my prescription<br />
checked, I had to go back and get tested a second time. A suggestion:<br />
Schedule the exam late in the day, when your eyes are tired, else you'll<br />
end up with a prescription that's adequate for a while after you wake up,<br />
but isn't sufficient by the end of the day.<br />
<br />
Michael Ernst <mernst>:<br />
<br />
I eventually went to Roosevelt Vision Clinic and saw Dr. Jamieson. I<br />
don't plan to return. While the office staff is helpful, friendly, and<br />
largely (not uniformly) competent, my glasses were mis-made (the bifocal<br />
line was too high) and after months I still don't have a<br />
comfortably-fitting pair of glasses. Also, I found Dr. Jamieson<br />
condescending and unhelpful (though he did give me a free second<br />
consultation in which he recommended a pair of computer glasses -- not<br />
covered by insurance, but in my case well worth the cost). Incidentally,<br />
those lenses were scratched when I first received them, too. It seems<br />
like this might be a reasonable place to go for someone with a weaker<br />
prescription than mine.<br />
<br />
Kurt Partridge <kepart>:<br />
<br />
i really like unversity vision clinic (recommended by others).<br />
dr. hovander seems competent, and is willing to give technical<br />
explanations for questions. last time i was there i started asking him<br />
some really fine points and he was pretty patient about all of them, and<br />
even admitted that he didn't know the answer to something (wish i remember<br />
how basic of a question is was :). also, the optician, monty, is<br />
excellent; i've always had problems with frames hurting behind the ears,<br />
and he adjusted them perfectly. he also suggested the pair of glasses<br />
that i currently have, which i've been very happy with. he's been an<br />
optician for something like 7 years now, and really enjoys it (i.e. he's<br />
not just doing it as a job).</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Doctors_in_Seattle&diff=7608Doctors in Seattle2009-02-12T02:18:43Z<p>Yanokwa: New page: [http://depts.washington.edu/hhpccweb/ Hall Health] - There's always Hall Health; they have some great doctors. The biggest downside is parking, should you wish to drive there. If you ha...</p>
<hr />
<div>[http://depts.washington.edu/hhpccweb/ Hall Health] - There's always Hall Health; they have some great doctors. The biggest downside is parking, should you wish to drive there. If you have small children, you can get a permit to park at N22 (disabled parking) across the street from Hall Health. Otherwise, it's a bit of a hike from E1.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Seattle_life&diff=7607Seattle life2009-02-11T21:31:16Z<p>Yanokwa: /* Seattle area */</p>
<hr />
<div>This page is for general information on living as a student in the [http://www.cs.washington.edu/ UW-CSE dept.] and the [http://en.wikipedia.org/wiki/Seattle Seattle] area. Grad students may also be interested in the [http://www2.cs.washington.edu/mediawiki/index.php/Grad_guide grad guide wiki] (CSE NetID required).<br />
<br />
Note that we have recommendations for various places in the Seattle area, as well as a compilation of mailing lists and so forth.<br />
<br />
Contributions and suggestions are welcomed! Just use the "edit" link on this page.<br />
<br />
Recommendations that don't fit in the existing categories:<br />
<br />
* [http://www.zipcar.com/ ZipCar] is a car sharing program that's great for occasional short trips if you don't want to own a car and rental is overkill. It was formerly FlexCar here before ZipCar bought them. You get your application and annual fees waived with your U-Pass! <br />
<br />
==Department info==<br />
*Mailing lists:<br />
**[http://mailman.cs.washington.edu/ mailman.cs]: the server that runs most of our departmental email lists. Includes three directories of mailing lists: [http://mailman.cs.washington.edu/mailman/listinfo/ public lists], [http://mailman.cs.washington.edu/uwnetid/auth/mailman/listinfo UW-restricted lists], and [http://mailman.cs.washington.edu/csenetid/auth/mailman/listinfo CSE-restricted lists].<br />
**[http://www.cs.washington.edu/people/mail/student-dist.html Mailing lists overview]<br />
*[http://www.cs.washington.edu/education/grad/current.html Graduate program]<br />
*[http://www.cs.washington.edu/lab/sw/restricted/donated-sw.html Donated software]<br />
*[http://www2.cs.washington.edu/mediawiki/index.php/Uns "Unsupported" software]<br />
*[http://www.cs.washington.edu/orgs/student-affairs/gsc/ Grad student affairs]<br />
<br />
==Life in the Allen Center==<br />
What you need to survive in your second home.<br />
*[[Restaurants that deliver]]<br />
<br />
==Extracurricular==<br />
*[[UW-CSE sports|UW-CSE Sports and Outdoors]]<br />
*[[Seattle fun]]<br />
*[[Ski Day 2007]]<br />
<br />
==Seattle area==<br />
These have been copied over and wikified from [http://www.cs.washington.edu/orgs/student-affairs/gsc/info.html the old pages]. Much of the content is outdated - please add your own recommendations and comments. A good way to find local businesses is with [http://maps.yahoo.com Yahoo! Maps]. Type in your address, or UW's<br />
(I use "15th and 40th AVE NE 98105"), and get a map. On the right there is a link entitled [http://yp.yahoo.com/py/ypBrowse.py?addr=15th+Ave+Ne+At+Ne+40th+St&csz=Seattle%2C+WA+98105 Find More Nearby...] that allows you to search the Yellow Pages by type or name. Bookmark for quicker access.<br />
<br />
*[[Auto mechanics in Seattle|Auto mechanics]]<br />
*[[Bakeries in Seattle|Bakeries]]<br />
*[[Banks in Seattle|Banks]]<br />
*[[Bicycle shops in Seattle|Bicycle shops]]<br />
*[[Broadband internet in Seattle|Broadband internet]]<br />
*[[Bookstores in Seattle|Bookstores]]<br />
*[[Car rental in Seattle|Car rental]]<br />
*[[Dentists in Seattle|Dentists]]<br />
*[[Department stores in Seattle|Department stores]]<br />
*[[Doctors in Seattle|Doctors]]<br />
*[[Electronics in Seattle|Electronics]]<br />
*[[Furniture in Seattle|Furniture]]<br />
*[[Groceries in Seattle|Groceries]]<br />
*[[Haircuts in Seattle|Haircuts]]<br />
*[[Hardware Stores in Seattle|Hardware]]<br />
*[[Housing in Seattle|Housing]]<br />
*[[Insurance agents in Seattle|Insurance agents]]<br />
*[[Long-distance calling in Seattle|Long-distance calling]]<br />
*[[Mobile phones in Seattle|Mobile phones]]<br />
*[[Optometrists in Seattle|Optometrists]]<br />
*[[Plumbers in Seattle|Plumbers]]<br />
*[[Restaurants in Seattle|Restaurants]]<br />
*[[Salons|Salons (Non-Haircut)]]<br />
*[[Storage in Seattle|Storage]]<br />
*[[Travel agencies in Seattle|Travel agencies]]<br />
*[[Veterinarian in Seattle|Veterinarian]]<br />
<br />
Also see Seattle's own wiki, [http://seattlewiki.org/ SeattleWiki].<br />
<br />
==Miscellaneous==<br />
*[http://www.cs.washington.edu/orgs/student-affairs/gsc/fellowships.html Fellowship taxes]<br />
*[http://www.cs.washington.edu/publications/mossybits/spring2000/ Mossy Bits]<br />
*[http://www.cs.washington.edu/orgs/student-affairs/gsc/history/ CSE department history]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6939Mac Users:Suggested Applications2007-10-27T10:30:44Z<p>Yanokwa: </p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
*[http://notational.net/ Notational Velocity] is an ultra-lightweight note-taking application.<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns]. Useful extensions are [http://www.downthemall.net DownloadThemAll] (speed downloader) and [http://www.getfirebug.com FireBug] (web programming). You should also try these speed [http://forum.addonsmirror.net/index.php?showtopic=2875 optimizations].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source.<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is for the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://skim-app.sourceforge.net/index.html Skim] lets you take (proprietary) notes on your PDFs.<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader, but no longer developed.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs.<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://bittyrant.cs.washington.edu/ BitTyrant] an in-house developed mod to Azureus that's more strategic.<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries..<br />
*[http://www.last.fm/group/iScrobbler iScrobbler] uploads what you listen to in iTunes to Last.fm. Annoying to download, it'll be one of the forum topics about a page down.<br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy.<br />
*[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
*[http://samba.anu.edu.au/rsync/ rsync] is the venerable command line tool. Useful options include -a -v -E and --delete.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://www.unrarx.com/ UnRarX] only does .rar files, but does them pretty well.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake.<br />
*[http://iterm.sourceforge.net/ iTerm] a full featured terminal emulation app written using Cocoa. Supports tabs.<br />
*[http://www.derlien.com/ Disk Inventory X] gives you an extremely useful graphical view of how space is used on your hard drive. Useful for cleaning up after yourself and your apps.<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/MISC/RDC2.0_Public_Beta_download.xml Microsoft RDC Beta] MS Client for Intel<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC<br />
<br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]<br />
<br />
==AntiVirus==<br />
Hahaha! No seriously, any antivirus solution will slow down your machine with all the scanning. Seeing as there are no known Mac viruses, the only reason to install it is to prevent spread of Microsoft macro viruses. I strongly recommend not installing any antivirus software and just regularly updating your OS software.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Society_and_technology&diff=6937Society and technology2007-08-29T07:49:46Z<p>Yanokwa: /* Other people */</p>
<hr />
<div>The society and technology interest group ('''soctech''') is an informal interest group that we are starting up among UW-CSE students to promote awareness of various social computing issues, in both CSE and the UW. We collaborate with other departments, with possible aims including the production of cross-departmental courses, lecture series, or white papers.<br />
<br />
Please visit our official [http://soctech.cs.washington.edu Society and Technology website].<br />
<br />
We have a mailing list, '''soctech@cs'''. Here's [http://mailman.cs.washington.edu/mailman/listinfo/soctech the public list info page].<br />
<br />
==Goals of the SocTech group==<br />
*'''Connecting the social concerns, legal landscape, and technical aspects of transformative technologies''': In the university, it is often easy to get lost daydreaming about abstract theories or caught up in the inner workers of some protocol or mechanical gadget. We want to step back and understand the larger context within which much of our research is taking place. How does technology get incorporated into people's everyday lives? What concerns are being raised about the technologies in question? Are there actions that can be taken to address these concerns?<br />
*'''Dialogue between disciplines''': We want to establish common vocabulary between groups with different expertise. Disciplines bring different frames of reference on the problems that we all confront--whether its technical perspectives from CS or EE or legal expertise from students of the law or a rich understanding of social forces from sociologists and communications folks. Addressing the many possiblities and problems that face our information-intensive society require dialogue across these boundaries.<br />
*'''Dialogue with the public''': It is easy for us to debate sociotechnical issues to our heart's content, but it won't have much impact unless we try to make connections with the public at large. A better informed public can make better decisions about its (and our) future. Our position as university elite does not mean that we need to be elitist.<br />
<br />
==Seminar==<br />
The '''society and technology seminar''' (CSE 590 T, formerly CSE 590 SO) is a weekly seminar that brings together students and scholars from a variety of fields to discuss the impacts of computing (and other technologies) on the larger world. If you have ideas for a future soctech seminar, or would be willing to organize one, please contact the [[Society and technology#Coordinators|current soctech coordinator]]!<br />
<br />
The course is organized by [[Society and technology|soctech@cs]] and listed under the UW Dept. of Computer Science and Engineering, but undergraduate and graduate students in all departments are encouraged to sign up. Enrollment is open; see the pages for individual quarter offerings for details.<br />
<br />
===Current and past quarters===<br />
* [[Soctech seminar, Spring 2007]]: RFID Case study: ORCA cards<br />
* [[Soctech seminar, Fall 2006]]: RFID Technology<br />
* [[Soctech seminar, Spring 2006]]: Social Ramifications of Search Technologies<br />
* [[Soctech seminar, Spring 2005]]: Electronic books and media<br />
* [[Soctech seminar, Winter 2005]]: Software security, law, and public policy<br />
<br />
===Mailing list===<br />
Visit<br />
:https://mailman.cs.washington.edu/mailman/listinfo/cse590t<br />
to sign up for the course mailing list. Contact the [[Society and technology#Coordinators|current soctech coordinator]] if you have any difficulty signing up.<br />
<br />
==Other activities==<br />
We have also, at various times in the past and with varying levels of success, tried [[Past society and technology activities|other things]].<br />
<br />
==People and organizations==<br />
===Coordinators===<br />
<!-- Note to editors: leave the "Coordinators" heading intact as you reorganize this page, as, it serves as a link target. ---><br />
<br />
Current UW-CSE coordinator: [http://www.cs.washington.edu/homes/travis/ Travis Kriplean], [http://www.cs.washington.edu/homes/yanokwa/ Yaw Anokwa]<br />
<br />
Current UW law coordinator: Jim Sfekas<br />
<br />
===Other people===<br />
*[http://www.cs.washington.edu/homes/ckd/ Colin Dixon]<br />
*[http://www.cs.washington.edu/homes/evan/ Evan Welbourne]<br />
*[http://www.cs.washington.edu/homes/supersat/ Karl Koscher]<br />
*[http://www.cs.washington.edu/homes/bdferris/ Brian Ferris]<br />
<br />
(feel free to add your name here)<br />
<br />
*'''[[Society and technology alumni|Past members and collaborators]]'''<br />
<br />
===UW departments===<br />
We're in informal contact with most of these, or have been in the past. The extent to which we actually work with them varies widely.<br />
*[http://www.cis.washington.edu/about/ Center for Internet Studies]<br />
*[http://www.law.washington.edu/ UW School of Law]<br />
**Intellectual Property Program (led by [http://www.law.washington.edu/Faculty/Gomulkiewicz/ Robert W. Gomulkiewicz])<br />
**[http://www.law.washington.edu/lct/ Shidler Center for Law, Commerce, and Technology] (led by [http://www.law.washington.edu/Faculty/Winn/ Jane Kaufman Winn])<br />
**Technology and Law club (may be defunct)<br />
*[http://www.ischool.washington.edu/ UW Information School]<br />
<br />
==Resources==<br />
*'''[[Society and technology courses|Courses]]:''' At the UW, and elsewhere. Some of the online lectures are especially useful.<br />
*'''[[Society and technology people|People]]:''' Scholars, activists, etc.<br />
*'''[[Society and technology organizations|Organizations]]:''' Research centers, nonprofits, government<br />
*'''[[Society and technology conferences|Conferences]]'''<br />
*'''[[Society and technology online|Other online resources]]:''' Mailing lists, blogs, etc.<br />
<br />
[[Category:Society and technology]]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6934Mac Users:Suggested Applications2007-08-20T21:24:21Z<p>Yanokwa: /* Browsing */</p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
*[http://notational.net/ Notational Velocity] is an ultra-lightweight note-taking application.<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns]. Useful extensions are [http://www.downthemall.net DownloadThemAll] (speed downloader) and [http://www.getfirebug.com FireBug] (web programming). You should also try these speed [http://forum.addonsmirror.net/index.php?showtopic=2875 optimizations].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source.<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is for the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs.<br />
*[http://skim-app.sourceforge.net/index.html Skim] lets you take (proprietary) notes on your PDFs.<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://bittyrant.cs.washington.edu/ BitTyrant] an in-house developed mod to Azureus that's more strategic.<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries..<br />
*[http://www.last.fm/group/iScrobbler iScrobbler] uploads what you listen to in iTunes to Last.fm. Annoying to download, it'll be one of the forum topics about a page down.<br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy.<br />
*[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
*[http://samba.anu.edu.au/rsync/ rsync] is the venerable command line tool. Useful options include -a -v -E and --delete.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://www.unrarx.com/ UnRarX] only does .rar files, but does them pretty well.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake.<br />
*[http://iterm.sourceforge.net/ iTerm] a full featured terminal emulation app written using Cocoa. Supports tabs.<br />
*[http://www.derlien.com/ Disk Inventory X] gives you an extremely useful graphical view of how space is used on your hard drive. Useful for cleaning up after yourself and your apps.<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]<br />
<br />
==AntiVirus==<br />
Hahaha! No seriously, any antivirus solution will slow down your machine with all the scanning. Seeing as there are no known Mac viruses, the only reason to install it is to prevent spread of Microsoft macro viruses. I strongly recommend not installing any antivirus software and just regularly updating your OS software.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=ORCA_Institutional_Partners&diff=6906ORCA Institutional Partners2007-06-06T20:15:52Z<p>Yanokwa: New page: Do not demand as much information as possible. - For each bit of data that you have there should be a clear policy (reasons known to the transit agencies). What you are collecting and why....</p>
<hr />
<div>Do not demand as much information as possible.<br />
- For each bit of data that you have there should be a clear policy (reasons known to the transit agencies). What you are collecting and why.<br />
<br />
Be aware of the powers of data mining. <br />
<br />
Data access should be known<br />
<br />
Everything you have should be in contract.<br />
<br />
Try not to violate users's privacy. <br />
<br />
If you can gather the information in aggregate, do so. It is a liability to have the data around.<br />
<br />
<br />
Commercial partner.<br />
- Be aware of things like the americans with disability act. if you collect bus stop information. you may get information about planned parenthood and the like. publicity and liability issues are huge.<br />
<br />
- As an institutional partner, you should be pushing for a flat and anonymous rate. Allow a contract where the transit agency control the pricing so the partner isn't.<br />
<br />
- Factor for the greater good, if you allow for max flexibility you build trust and better the environment, better the companies reputation. <br />
<br />
- If there are proprietary information on the card (including a user id that is used in ms), that might be accessed by other companies. There is no clear firewall between systems so you should assume that everything you know, your partners know as well.<br />
<br />
- Make sure to use a random salt on the card. Targeted hostility may be a problem if users know Microsoft employees are on the bus. <br />
<br />
- There is a good reason to keep the cards separate if at all possible. While the card can support applications. Leaked information could be a issue -- not cleartext but can still read information from encryption. <br />
<br />
- Allow users to opt -out in a meaning way and still get some of the rates that the linked card has. If possible to go fully anonymous, then please do so.<br />
<br />
- Each corporation has it's own different purposes. Understand that data could be supoeaned in court and so there are liability issues.<br />
<br />
- Before deploying a system, it might nice to ask the users what they think to prevent a mutiny. Don't make it a forced-condition of employment. Avoiding mutiny is a good idea.]<br />
<br />
- the transit agencies collect a ton of data. if the data you have cannot be supoenead, the transit agencies has a super set of the data which can be supoenaed.. by the press and by law enforcement. just because you control a subset doesnt mean you control all of it. location data can do all sorts of tricky things given the right algorithm.<br />
<br />
- the data is a double edged sword. it can be useful and a liability. <br />
<br />
- It's unlikely that the card the point of failure. if you collecting some transit, understand that employees shouldnt have access to this data. there are smart people at msft, but there are stalking scnearios.<br />
<br />
- determine what you term as abuse. that abuse is transit agency considers abuse and so the users should be clear about it.<br />
<br />
- bus drivers cannot be enforcers of your policies. they are just state employees.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=ORCA_One-Page_Summaries&diff=6905ORCA One-Page Summaries2007-06-06T20:15:34Z<p>Yanokwa: </p>
<hr />
<div>Stakeholders:<br />
* Joe Users<br />
* Institutional Users<br />
* Transit Agencies<br />
* [[ORCA Institutional Partners]]<br />
* Policy Makers<br />
* ERG Group/Implementers<br />
<br />
Categories:<br />
* What is ORCA?<br />
* How does it affect me?<br />
* What should I be worried about?<br />
* What shouldn't I be worried about?<br />
* What can I do?</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Optometrists_in_Seattle&diff=6836Optometrists in Seattle2007-05-24T20:31:28Z<p>Yanokwa: /* Optometrists recommendations/information */</p>
<hr />
<div>==Optometrists recommendations/information==<br />
<br />
====Yaw Anokwa, 24-May-2007====<br />
Another thumbs up for Bursett Optometry.<br />
<br />
====From: Jochen Jaeger <jj@cs.washington.edu>====<br />
<br />
As it is only a 5 min walk away from SIEG I went to the<br />
University Vision Clinic (4115 Univ. Way, N.E, Suite 101).<br />
The team there was very nice and I got a thorough eye<br />
examination (took roughly one hour). First his assistant<br />
did some basic examination/questions and then Dr. Hovander<br />
continued with glass fitting and some more examinations.<br />
He patiently and competently answered all questions I had<br />
and did not push me to buy anything.<br />
I would recommend him.<br />
Only drawback. Instead of the 10$ out of pocket money<br />
I had to pay 20$ as the examination costs apparently<br />
70$ and the insurance only covers 60$ (from which you<br />
have to pay already 10$).<br />
<br />
====04 Feb 2002 Vibha Sazawal <vibha@cs>====<br />
<br />
For an OPTHAMOLOGIST...<br />
<br />
Brian Carey<br />
Seattle Eye M.D.s<br />
6th & Pine (downtown)<br />
<br />
http://www.eyemds.net<br />
<br />
Glasses only is $130, but only $100 if it's your first visit<br />
and if you don't want to claim any insurance. Contacts are<br />
$180?<br />
<br />
They test for glaucoma, retinal detachment,<br />
cataracts...things you should only worry about if you have<br />
family history. <--- This is a mis-conception ... family history of ocular disease increases a person's risk factor for getting the disease, but it does not completely rule out the possiblity of the person getting the disease. People are still advised to get annual eye exams to catch any problems before it advances. <br />
<br />
Don't go to the hospital just 'cause it's cheaper. You<br />
might just get a clueless resident.<br />
<br />
====24 Sep 2004 yasuhara====<br />
<br />
FYI a ton of CSE folks (myself included) continue to see Dr. Bursett (as commented on below), but she did move her office to the east side---no longer in the U. District. The new address and phone are 13715 Bel Red Rd, Bellevue, WA 98005, (425) 401-2020.<br />
<br />
UPDATE: Actually Ken, she moved back to the west side (Eastlake to be precise)...yay! Jessica<br />
<br />
UPDATE: Dr. Bursett's Current Contact Info:<br />
2323 Eastlake Avenue East<br />
Seattle, WA 98102 <br />
206-632-2237 -- kate<br />
<br />
====26 October 2000 Rachel Pottinger (rap@cs)====<br />
<br />
I recommend Bursett Optometry, 206-632-2237, 4545 15th Avenue NE #207;<br />
they know all about the insurance and had contacts for me on the spot,<br />
which has never happened to me before. I got out of there with a new<br />
pair of contacts for $24. She's used by about half the people in my<br />
office (224).<br />
<br />
====Craig Kaplan, Sep 2001====<br />
<br />
Lisa Bursett at 45th and 15th. She has a sixth sense for<br />
immediately choosing the one set of frames that's perfect<br />
for you, even if you didn't realize how good they were.<br />
<br />
==Advice for those looking for an optician if you have already have a prescription:==<br />
<br />
====9 Oct 2000 Ashish Sabharwal====<br />
<br />
I got new glasses a week ago from Colaizzo Opticians (1623 Queen Ann Ave N.).<br />
I think they have a better collection than the few shops I tried in<br />
U-district, especially if you want something "different" :)<br />
<br />
<br />
====9 October 2000 Adam Macbeth====<br />
<br />
I went to the place on the Ave (across from the bookstore) and they did a<br />
pretty good job.<br />
<br />
====6 October 2000 Gerome Miklau====<br />
<br />
There's kind of an upscale place in U Village that sells stylish<br />
frames. It's in the inner courtyard-type part of the mall. <br />
<br />
====6 October 2000 Ka Yee Yeung====<br />
<br />
I'm personally a big Costco fan. They sell glasses. But if you prefer a<br />
clinic-type of places, you can go to an optometrist.<br />
Oh, Costco is a lot less expensive, and we can claim our insurance even if<br />
we go to Costco.<br />
<br />
I have been terribly ribbed by some (bad) optometrists before. They<br />
charged me $150 for a pair of contact lenses. But I managed to get<br />
identical contact lenses at Costco for $40. But Costco probably doesn't<br />
carry very many fancy frames for glasses. <-- You must understand that Costco is a large corporation that is able to purchase and stock large quantities of contact lenses. They usually will get the bulk order of lenses at a reduced rate compared to private offices. This reduction is then passed onto the consumers. Private practices are not always readily able to make purchases that large, thus the cost for them is higher ... hence higher prices for the lenses.<br />
<br />
====6 October 2000 Steve Swanson====<br />
<br />
It depends on whether you want plastic or glass. I think everywhere pretty<br />
much does plastic. I am picky and wanted glass, and finally found that<br />
Eyes Right on the corner of the Ave and 46th or so (right next to futon of<br />
north america and catty corner from Costas) would do it. They deal with<br />
UW insurance I guess. Insurance got messed up with me, but I had some<br />
wierdness with the two insurance polcies I had at the time.<br />
<br />
If nothing else the guy that seems to own the place is really nice. <br />
<br />
====9 October 2000 Dan Grossman====<br />
<br />
I haven't had any experience with shops in Seattle, but I would caution<br />
that they are decidedly *not* all the same. Also, frame styles should not<br />
be your main criterion. One thing to pay attention to is the number and<br />
quality of technicians working there. When I first got glasses, it took<br />
several months and several adjustments before they were physically<br />
comfortable and properly functioning vision-wise. (Of course, I have<br />
bifocals, so that presents special difficulties.) If the store does not<br />
have a very helpful staff, you might get stuck paying for all sorts of<br />
adjustments you might have to make, not to mention the fact that your<br />
lenses might have flaws such as slight disparities in lens power, improper<br />
angle of insertion into the frames, etc.<br />
<br />
In my experience, you can tell a skilled and helpful technician by his/her<br />
grim determination to get the glasses looking, feeling, and "seeing" <br />
exactly right. Of course, most of this is exhibited *after* you've<br />
ordered the glasses, but you can also tell a lot by their attitude during<br />
the trying-on phase.<br />
<br />
====Optometrist/eyeglass shop recommentations from early April, 1997:====<br />
<br />
Marc Friedman <friedman>:<br />
<br />
(July 2, 1998)<br />
The least I can do is urge people NOT to go to Roosevelt Vision<br />
Clinic. I missed an appointment there, and paid their missed <br />
appointment fee on the spot. Nevertheless, they TERMINATED me as a<br />
patient without explanation and with no opportunity for rehabilitation.<br />
<br />
This may seem cost-effective to them, but it seems unprofessional to<br />
me. I mean, my car was stolen. But did they care? No. Don't go<br />
there.<br />
<br />
Dan Fasulo <dfasulo>:<br />
<br />
I recently got a couple of pairs of glasses from LensCrafters up at the <br />
Northgate mall. I didn't have time to comparison shop because I was in a <br />
hurry to replace some glasses that got left behind on a trip, but the <br />
salespeople were friendly and helpful and the glasses got made in an hour <br />
without a hitch. Their facilities seemed very modern.<br />
<br />
I also went to the on-site, independent optometrists, and, despite<br />
having fancier equipment than my hometown optometrist, they botched the<br />
prescription slightly the first time, which was annoying. On the other<br />
hand, they re-did the exam promptly and LensCrafters replaced the lenses<br />
for free. <br />
<br />
I also had to pick out frames since the old frames, along with the<br />
lenses, had been left behind in Colorado. :) The salesman was patient and<br />
helpful, and being a CS grad student, I *always* need help in identifying<br />
things that are fashionable. :) It seemed like a well-run place.<br />
<br />
Jack Lo <jlo>:<br />
<br />
I've gone to the Roosevelt Vision Clinic. It's been a good place for me to<br />
go. It's also on approved the grad student vision plan list, if you have<br />
grad student/appointee health insurance.<br />
<br />
Emin Gun Sirer <egs>:<br />
<br />
I have been going to Scott Jamieson at the Roosevelt Vision Clinic. He<br />
is competent and knowledgeable, and patiently answers all of my questions.<br />
He is affiliated with the student vision plan, so insurance picks up most<br />
of the costs. <br />
<br />
Amir Michail <amir>:<br />
<br />
I have had good experiences with Eye Associates Northwest. Their<br />
number is 206-386-2700. (However, my glasses are not "high powered".)<br />
<br />
Pat Tressel <tressel><br />
<br />
I tried for *years* to find someplace that could make even marginally<br />
usable high-diopter glasses, until...one of the dispensing opticians at<br />
the Virgina Mason clinic's optical shop ("Visual Effects" ;-) realized<br />
what was wrong. The prescriptions had always been filled with plastic<br />
lenses. But plastic has about half the index of refraction of glass,<br />
and the curvature required was so extreme with plastic that there was<br />
usually only one small region that was in focus. The optician ordered<br />
glass lenses, and -- voila! -- everything was in focus right to the<br />
edges of the lenses. So, no matter who you go to, don't let them talk<br />
you into plastic lenses. Instead, to keep the weight down, get frames<br />
with a small aperture. (You don't have to be a patient at Virginia<br />
Mason to have prescriptions filled at Visual Effects. They are likely<br />
more expensive than the mass-production shops. I have the vaguest of<br />
memories that the optician who helped me was named John.)<br />
<br />
I don't, unfortunately, know of an optometrist willing to take the time<br />
to work with low-vision patients. The last time I had my prescription<br />
checked, I had to go back and get tested a second time. A suggestion:<br />
Schedule the exam late in the day, when your eyes are tired, else you'll<br />
end up with a prescription that's adequate for a while after you wake up,<br />
but isn't sufficient by the end of the day.<br />
<br />
Michael Ernst <mernst>:<br />
<br />
I eventually went to Roosevelt Vision Clinic and saw Dr. Jamieson. I<br />
don't plan to return. While the office staff is helpful, friendly, and<br />
largely (not uniformly) competent, my glasses were mis-made (the bifocal<br />
line was too high) and after months I still don't have a<br />
comfortably-fitting pair of glasses. Also, I found Dr. Jamieson<br />
condescending and unhelpful (though he did give me a free second<br />
consultation in which he recommended a pair of computer glasses -- not<br />
covered by insurance, but in my case well worth the cost). Incidentally,<br />
those lenses were scratched when I first received them, too. It seems<br />
like this might be a reasonable place to go for someone with a weaker<br />
prescription than mine.<br />
<br />
Kurt Partridge <kepart>:<br />
<br />
i really like unversity vision clinic (recommended by others).<br />
dr. hovander seems competent, and is willing to give technical<br />
explanations for questions. last time i was there i started asking him<br />
some really fine points and he was pretty patient about all of them, and<br />
even admitted that he didn't know the answer to something (wish i remember<br />
how basic of a question is was :). also, the optician, monty, is<br />
excellent; i've always had problems with frames hurting behind the ears,<br />
and he adjusted them perfectly. he also suggested the pair of glasses<br />
that i currently have, which i've been very happy with. he's been an<br />
optician for something like 7 years now, and really enjoys it (i.e. he's<br />
not just doing it as a job).</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Dentists_in_Seattle&diff=6835Dentists in Seattle2007-05-24T20:29:31Z<p>Yanokwa: /* Dentists */</p>
<hr />
<div>==Dentists==<br />
<br />
====Yaw Anokwa, 24-May-2007====<br />
Another thumbs up for 32 Good Reasons. A little sore from the cleaning, but they were friendly and thorough.<br />
<br />
====Kayur Patel, 18-Aug-2005====<br />
I recommend Dr. William Thompson and Laser Dentistry of Seattle. The staff is very friendly and he provides a drill/anesthetic free alternative for routine dental work (eg. fillings). Personally, I don't respond well to novocaine so finding his office has been a godsend. There's only one caveat, its about 10 miles away from the UW. If you are interested his number is (206) 242-5800.<br />
<br />
====Susumu Harada, 28-Feb-2005====<br />
Another thumbs up for 32 Good Reasons. Had a small filling without any anesthetics and didn't feel a thing. Pain free treatment as well as pain free insurance handling (they were very accurate on the quote they gave me).<br />
<br />
====Gary Yngve, 22-Dec-2004==== <br />
I had some work done at Stacy Gilmore's office (see Sarah's entry), and it was quite excellent. Very friendly staff.<br />
<br />
====Peter Mork, 13-Dec-2004====<br />
<br />
I agree with Neva and Rachel. My whole family uses 32 Good Reasons (Dr. Barrett's office). My wife is very leery of dentists (due to oral surgery without anasthesia as a child), but they've been very good to her. She just had a pain-free root canal!<br />
<br />
====Ethan Phelps-Goodman, 12/12/2004====<br />
I went to Lynn Rowland once, and I'd say she was only OK. She was very friendly, and it was easy to make an appointment, but I didn't think the cleaning was nearly as thurough as I got from my dentist back home. And it was done entirely by a dental assistant, not the dentist. Maybe that's normal though.<br />
<br />
<br />
====Sarah Schwarm, 12/10/2004====<br />
I see Dr. Stacy Gilmore, and am very pleased with her office for both regular cleanings (they know our insurance, I never touch any paperwork) and more extensive work. I recently had a crown put on one of my front teeth to permanently repair a broken tooth from a high school mishap involving a field hockey stick, and I'm very pleased with the results. (The process of getting the crown done was a lot less unpleasant than I feared, too.)<br />
<br />
Her office contact info is:<br />
3216 NE 45th Pl Ste 302<br />
Seattle, WA 98105<br />
(206) 522-0443<br />
<br />
<br />
====Andrew Whitaker, 11/07/2004====<br />
I can whole-heartedly recommend Wallingford Dental Arts (google://wallingford dental arts). The office is run by a set of dentists, all of whom (in my experience) are extremely competent and friendly. And, they have the University insurance system down pat.<br />
<br />
====Andy Schwerin, 03-27-2007====<br />
I have been using Dr. Charles Wallace, on Eastlake Ave E, since late 2001. I have received regular cleanings and a referral for wisdom tooth removal, and been highly satisfied.<br />
<br />
====Stefan Saroiu, 09-24-2004====<br />
I go to Dr. Daniel Thacker in Kingston (you have to take the ferry to get there).<br />
<br />
Apple Tree Cove Dental Ctr PO Box 149 Kingston, WA 98346-0149 Phone: (360) 297-3392<br />
<br />
It seems like an overkill to take the ferry to go see your dentist, so why do I recommend him? Three reasons:<br />
<br />
1. My wife is a dentist. She recommends that office (the truth is that I sometimes see my wife rather than Dr. Thacker). And no, she doesn't practice at that office, nor we derive any benefits from recommending people to go there.<br />
<br />
2. They use very good materials and the dentist is good. Personally, I don't care too much about the staff being friendly. I think it's more important if the dentist is good and whether they're not into saving a couple of bucks by using inferior dental products.<br />
<br />
3. That's the closest good dentist/good materials office we know of. We're not saying there aren't other good offices closer to UW.<br />
<br />
By the way, the ferry ride is spectular ($5 per person both ways, no car).<br />
<br />
--Stefan<br />
<br />
====Neva Cherniavsky, 09-24-2004====<br />
<br />
Since Rachel posted so long ago, I want to reiterate what she said. I went to Dr. Barrett this summer and he and his staff were great. They were very friendly and professional, and they knew all about the insurance. It didn't cost me a penny.<br />
<br />
Ernest Barrett<br />
1107 NE 45th St. Suite 220 <br />
(206)632-9400 <br />
<br />
====Dmitriy Portnov, 09-05-2001====<br />
<br />
Robert Stark<br />
4530 Union Pl NE, Suite 206<br />
phone 206-525-5000<br />
<br />
Another recommendation for Dr. Robert Stark (dentist).<br />
<br />
I agree with everything in Matthai's recommendation from 10-5-99. Very<br />
nice, modern office; friendly and professional staff.<br />
Staff knows about our insurance policy too.<br />
<br />
====Craig Kaplan, 09-04-2001====<br />
<br />
Lynn Rowland<br />
(see below)<br />
<br />
The first dentist I chose in Seattle was the right one. I'm<br />
very happy with Lynn Rowland. She's on the Ave. south of 42nd.<br />
<br />
====Denise Pinnel, 10-05-1999====<br />
<br />
Lynn Rowland<br />
4115 Univ Way Suite 110<br />
phone: 632-7575<br />
<br />
Very good, friendly, staff knows all about our insurance policy. Right<br />
on the Ave near school.<br />
<br />
====Matthai Philipose, 10-05-1999====<br />
<br />
Robert Stark<br />
4530 Union Pl NE, Suite 206<br />
206-525-5000<br />
<br />
His office is located just behind the university village. I've been <br />
going to him for about a year now, my wife has been going for a few <br />
years. We have found him (and his assistants) very professional and <br />
competent. The clinic is pleasant, bright and modern. I've gotten two <br />
wisdom teeth removed there, no problem. All in all, eons better than <br />
my previous Seattle dentist, a guy called Carey from the U District.<br />
<br />
====Rachel Pottinger, 10-04-1999====<br />
<br />
Ernest Barrett<br />
1107 NE 45th St. Suite 220 <br />
<br />
Very good; very nice, staff knows all about the insurance.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Open_ORCA_Questions&diff=6743Open ORCA Questions2007-05-10T09:02:52Z<p>Yanokwa: /* General questions */</p>
<hr />
<div>== email to be sent to Kevin ==<br />
<br />
I'll write up an email thursday based on responses I get from people. I have a blurb of an email outlined here, but more specific questions will be summarized from the list below. Please add to it, or send me an email at travis at cs.washington.edu.<br />
<br />
=== Email ===<br />
<br />
We are mainly computer science PhD students and law school students, along with other disciplines and faculty. We are all generally interested in the intersection of the law and technology. We have spent about 8 weeks discussing ORCA and what issues should be considered in order for a responsible and successful ORCA deployment. We've been basing our discussions mainly on bits and pieces of data about ORCA that we've collected from the web, as well as other transit systems like it. We're hoping that you'll be able to help us understand the specifics of ORCA, policy-wise, legally, and technically. We also hope that this will be a first opportunity for us to be able to share with you our thoughts as stakeholders.<br />
<br />
=== General questions ===<br />
<br />
* What is changing between the old transit system and ORCA? What do transit agencies and riders gain? What do they lose? <br />
* What is the overall vision of ORCA in the future?<br />
* What are the big hurdles you've encountered so far?<br />
* What obstacles you see in the near and distant future?<br />
* What legal issues have come to the fore in making ORCA possible? (Have the transit agencies been participating in developing the Washington electronic bill of rights?)<br />
* How does ORCA differ from other ERG-contracted transit systems like Oyster, in terms of policy and technology? <br />
<br />
==== Data management ====<br />
<br />
* What data is stored on the card? When the card communicates with the reader what information is exchanged? Is this information encrypted?<br />
<br />
* What data is stored in the database? What function does each piece of data serve? (Are the unique identifiers salted on the card?)<br />
<br />
* Let's say I take a trip on the bus. From the time I swipe my card until the time I get off, what gets read from the card, where does the data go, what is added to it, when does it get stored to a central database? <br />
<br />
* How long is the data kept in the database? We know it is held for a min of 90 days, but what's the max?<br />
<br />
* Will stored data be aggregated or does it remain connected to personal data?<br />
<br />
* Physically, where are the databases? Do the transit authorities control those facilities or does ERG?<br />
<br />
* What technology is used to transmit data from the RFID readers on the bus to the central database? Is it encrypted? Is it sent via WiFi or physically transmitted via disk?<br />
<br />
==== Transit agency policy ====<br />
<br />
* What are the key points of your privacy policy?<br />
<br />
* As a user of the ORCA card, what are the terms and conditions? What contract do I sign and when?<br />
<br />
* How does KC Metro currently handle requests for information by law-enforcement? Given that data (entrance/exit) data may be stored for a minimum of 90 days, are you worried about an increase in requests for this data (e.g. as the Oyster card has seen)? Is there a mechanism for preventing 'fishing expeditions'<br />
<br />
* Will there be options to opt-out of using an ORCA card while using public transit, or will these options be phased out over time? What do users loose when they opt-out?<br />
<br />
* How does KC Metro view ownership of the transit data?<br />
<br />
* Will transit users be able to view data that has been collected about them?<br />
<br />
* Is there an audit trail that individuals and institutional partners can use to trace whom the data has been given out to (e.g. D.C. deployment)?<br />
<br />
* Are there processes in place for fixing incorrect data?<br />
<br />
* Is there a citizens advisory board? How is compliance with the policies ensured?<br />
<br />
==== Institutional partners and third parties ====<br />
<br />
* Who has access to what data? Are there any limits to who has access?<br />
<br />
* Who will be the major initial institutional partners? We know about the UW-Husky card integration and Boeing, but are there others? How do you see these institutional partnerships growing in the future?<br />
<br />
* Are there other applications planned beyond transit, such as the use of ORCA cards as commercial debit cards? If so, how are the boundaries of applications defined? Who do you classify as a third party and what data flows between these new applications? <br />
<br />
* What might be sent to third parties? Is it aggregate or individual records? Can this data be sold? If so, in what form? <br />
<br />
* Who will be allowed to sell new cards? Who will be authorized to sell/distribute one-use cards? What data will these card issuers be entitled to?<br />
<br />
* Why is it necessary for customer-service agents, employees of ERG, transit agents, and institutional partners to have access to transit histories for specific transit-users?<br />
<br />
==== Miscellaneous ====<br />
<br />
* What is the timeline for bringing forward proposals for changes to the ORCA system and ORCA policies. What aspects of the ORCA system are set in stone?</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Open_ORCA_Questions&diff=6742Open ORCA Questions2007-05-10T08:56:06Z<p>Yanokwa: /* Email */</p>
<hr />
<div>== email to be sent to Kevin ==<br />
<br />
I'll write up an email thursday based on responses I get from people. I have a blurb of an email outlined here, but more specific questions will be summarized from the list below. Please add to it, or send me an email at travis at cs.washington.edu.<br />
<br />
=== Email ===<br />
<br />
We are mainly computer science PhD students and law school students, along with other disciplines and faculty. We are all generally interested in the intersection of the law and technology. We have spent about 8 weeks discussing ORCA and what issues should be considered in order for a responsible and successful ORCA deployment. We've been basing our discussions mainly on bits and pieces of data about ORCA that we've collected from the web, as well as other transit systems like it. We're hoping that you'll be able to help us understand the specifics of ORCA, policy-wise, legally, and technically. We also hope that this will be a first opportunity for us to be able to share with you our thoughts as stakeholders.<br />
<br />
=== General questions ===<br />
<br />
* What is changing between this system and the old system? What do transit agencies and riders gain? <br />
* What is the overall vision of ORCA in the future?<br />
* What are the big hurdles you've encountered so far?<br />
* What are the significant obstacles you see in the near and distant future?<br />
* What legal issues have come to the fore in making ORCA possible? (Have the transit agencies been participating in developing the Washington electronic bill of rights?)<br />
* How does ORCA differ from other ERG-contracted transit systems like Oyster, in terms of policy and technology? <br />
<br />
==== Data management ====<br />
<br />
* What data is stored on the card?<br />
<br />
* What data is stored in the database? What function does each piece of data serve? (Are the unique identifiers salted on the card?)<br />
<br />
* I take a trip on the bus. From the time I swipe my card until the time I get off, what gets read from the card, where does the data go, and when does it get stored to a central database? <br />
<br />
* How long is the data kept in the database? We know it is held for a min of 90 days, but what's the max?<br />
<br />
* Will stored data be aggregated or does it remain connected to personal data? <br />
<br />
* Physically, where are the databases? Do the transit authorities control those facilities or does ERG?<br />
<br />
* What technology is used to transmit data from the RFID readers on the bus to the central database? Is it encrypted? Is it sent via wifi or physically transmitted via disk?<br />
<br />
==== Transit agency policy ====<br />
<br />
* What are the key points of your privacy policy?<br />
<br />
* As a user of the ORCA card, what are the terms and conditions? What contract do I sign and when?<br />
<br />
* How does KC Metro currently handle requests for information by law-enforcement? Given that data (entrance/exit) data may be stored for a minimum of 90 days, are you worried about an increase in requests (e.g. as the Oyster card has seen)?<br />
<br />
* Will there be options to opt-out of using an ORCA card while using public transit, or will these options be phased out over time?<br />
<br />
* How does KC Metro view ownership of the transit data?<br />
<br />
* Will transit users be able to view data that has been collected about them?<br />
<br />
* Is there an audit trail that individuals and institutional partners can use to trace whom the data has been given out to (e.g. D.C. deployment)?<br />
<br />
* Are there processes in place for fixing incorrect data?<br />
<br />
* Is there a citizens advisory board? How is compliance with the policies ensured?<br />
<br />
==== Institutional partners and third parties ====<br />
<br />
* Who has access to what data? Are there any limits to who has access?<br />
<br />
* Who will be the major initial institutional partners? We know about the UW-Husky card integration and Boeing, but are there others? How do you see these institutional partnerships growing in the future?<br />
<br />
* Are there other applications planned beyond transit, such as the use of ORCA cards as commercial debit cards? If so, how are the boundaries of applications defined? Who do you classify as a third party and what data flows between these new applications? <br />
<br />
* What might be sent to third parties? Is it aggregate or individual records? Can this data be sold? If so, in what formats? <br />
<br />
* Who will be allowed to sell new cards? Who will be authorized to sell/distribute one-use cards? What data will these card issuers be entitled to?<br />
<br />
* (Why is it necessary for customer-service agents, employees of ERG, transit agents, and institutional partners to have access to transit histories for specific transit-users?)<br />
<br />
==== Miscellaneous ====<br />
<br />
* What is the timeline for bringing forward proposals for changes to the ORCA system and ORCA policies. What aspects of the ORCA system are set in stone?</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Open_ORCA_Questions&diff=6725Open ORCA Questions2007-05-10T00:50:59Z<p>Yanokwa: /* Organizational policy */</p>
<hr />
<div>== email to be sent to Kevin ==<br />
<br />
<br />
<br />
=== General questions ===<br />
<br />
* What is the overall vision of ORCA in the future?<br />
* What are the big hurdles you've encountered so far?<br />
* What are the significant obstacles you see in the near and distant future?<br />
* What legal issues have come to the fore in making ORCA possible?<br />
<br />
==== Organizational policy ====<br />
<br />
How does this deployment differ from other ERG transit systems (additions and subtractions)? How are they managed (organizationally, legally)<br />
<br />
Is there any participating in developing the electronic bill of rights? Is there any other legislation that is relevant that you are looking at?<br />
<br />
Is there a citizens advisory board? How is compliance with the policies ensured? Who is watching the watcher?<br />
<br />
<br />
<br />
What other applications are you planning on beyond transit? We know about the UW-Pass and Boeing, but who else? Who will you interoperate with?<br />
<br />
How does KC Metro currently handle law-enforcement information. Given that data (entrance/exit) data may be collected for min 90 days. you worried about an increase in requests (see uk)<br />
<br />
Who are the "partner participants"? What gets sent to third party? Is it aggregate or individual records? Can this data be sold? If so, in what formats?<br />
<br />
How are the boundaries of applications defined? Do you have plans to expand beyond transit. And if so, who do you classify as a third party and what data flows between these new applications? Who can issue new cards?<br />
<br />
what is your privacy policy? what are the five key points?<br />
<br />
What are my options to opt-out. Are these reasonable options?<br />
<br />
Who gets sued when something goes wrong?<br />
<br />
What are you changing between this system and the old system? What do you gain (variable rates, more throughput)? What do you see as the long term change.<br />
<br />
<br />
As a user of the system, what are the terms and conditions? What contract do I sign?<br />
<br />
Data <br />
I take a trip on the bus. From the time I swipe my card till the time I get off, where does the data go, what does it get added, and when does it it disappear?<br />
<br />
<br />
How long is the data kept and what form (aggregate) is it stored?<br />
<br />
Who has access to what data and how?<br />
Where is the data stored?<br />
How does KC Metro view ownership of data?<br />
How is it shared?<br />
Is there an audit trail? Transparency builds trust. <br />
Is there a way fix incorrect data?<br />
<br />
Can I look at data about me (as opposed to my data).<br />
<br />
What data is stored on the card and what is stored in the database? Are the unique identifiers salted on the card?<br />
<br />
How does data get back to the central database? Is it sent in the clear? Via wifi? smoke signals?<br />
<br />
Data retention. We know it is held for a min of 90 days, but what's the max? What data are you collecting and why?<br />
<br />
If there are one-use cards, what are the issuers entitled to (data wise<br />
<br />
Can we get access to an ORCA card/reader?<br />
<br />
To Do<br />
Who will be there? <br />
We are not n00bs...<br />
Perhaps bring a lawyer and a technician</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Open_ORCA_Questions&diff=6724Open ORCA Questions2007-05-10T00:46:17Z<p>Yanokwa: /* Organizational policy */</p>
<hr />
<div>== email to be sent to Kevin ==<br />
<br />
<br />
<br />
=== General questions ===<br />
<br />
* What is the overall vision of ORCA in the future?<br />
* What are the big hurdles you've encountered so far?<br />
* What are the significant obstacles you see in the near and distant future?<br />
* What legal issues have come to the fore in making ORCA possible?<br />
<br />
==== Organizational policy ====<br />
<br />
How does this deployment differ from other ERG transit systems (additions and subtractions)? How are they managed (organizationally, legally)<br />
<br />
Is there any participating in developing the electronic bill of rights? Is there any other legislation that is relevant that you are looking at?<br />
<br />
Is there a citizens advisory board? How is compliance with the policies ensured? Who is watching the watcher?<br />
<br />
<br />
<br />
What other applications are you planning on beyond transit? We know about the UW-Pass and Boeing, but who else? Who will you interoperate with?<br />
<br />
How does KC Metro currently handle law-enforcement information. Given that data (entrance/exit) data may be collected for min 90 days. you worried about an increase in requests (see uk)<br />
<br />
Who are the "partner participants"? What gets sent to third party? Is it aggregate or individual records? Can this data be sold? If so, in what formats?<br />
<br />
How are the boundaries of applications defined? Do you have plans to expand beyond transit. And if so, who do you classify as a third party and what data flows between these new applications? Who can issue new cards?<br />
<br />
what is your privacy policy? what are the five key points?<br />
<br />
What are my options to opt-out. Are these reasonable options?<br />
<br />
Who gets sued when something goes wrong?<br />
<br />
What are you changing between this system and the old system? What do you gain (variable rates, more throughput)? What do you see as the long term change.<br />
<br />
<br />
As a user of the system, what are the terms and conditions? What contract do I sign?<br />
<br />
Data <br />
I take a trip on the bus. From the time I swipe my card till the time I get off, where does the data go, what does it get added, and when does it it disappear?<br />
<br />
<br />
How long is the data kept and what form (aggregate) is it stored?<br />
<br />
Who has access to what data and how?<br />
Where is the data stored?<br />
How does KC Metro view ownership of data?<br />
How is it shared?<br />
Is there an audit trail? Transparency builds trust. <br />
Is there a way fix incorrect data?<br />
<br />
Can I look at data about me (as opposed to my data).<br />
<br />
What data is stored on the card and what is stored in the database? Are the unique identifiers salted on the card?<br />
<br />
How does data get back to the central database? Is it sent in the clear? Via wifi? smoke signals?<br />
<br />
Data retention. We know it is held for a min of 90 days, but what's the max? What data are you collecting and why?<br />
<br />
If there are one-use cards, what are the issuers entitled to (data wise)<br />
<br />
To Do<br />
Who will be there? <br />
We are not n00bs...<br />
Perhaps bring a lawyer and a technician</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Open_ORCA_Questions&diff=6720Open ORCA Questions2007-05-09T22:24:29Z<p>Yanokwa: New page: Policy What are the top issues you've come across? What are the big hurdles you've encountered and what do you foresee? What do you see are the pertinent legal issues? How does this dep...</p>
<hr />
<div>Policy<br />
<br />
What are the top issues you've come across? What are the big hurdles you've encountered and what do you foresee? What do you see are the pertinent legal issues? <br />
<br />
How does this deployment differ from other ERG transit systems (additions and subtractions)? How are they managed (organizationally, legally)<br />
<br />
Is there any participating in developing the electronic bill of rights? Is there any other legislation that is relevant that you are looking at?<br />
590<br />
Is there a citizens advisory board? How is compliance with the policies ensured? Who is watching the watcher?<br />
<br />
<br />
<br />
What other applications are you planning on beyond transit? We know about the UW-Pass and Boeing, but who else? Who will you interoperate with?<br />
<br />
How does KC Metro currently handle law-enforcement information. Given that data (entrance/exit) data may be collected for min 90 days. you worried about an increase in requests (see uk)<br />
<br />
Who are the "partner participants"? What gets sent to third party? Is it aggregate or individual records? Can this data be sold? If so, in what formats?<br />
<br />
How are the boundaries of applications defined? Do you have plans to expand beyond transit. And if so, who do you classify as a third party and what data flows between these new applications? Who can issue new cards?<br />
<br />
what is your privacy policy? what are the five key points?<br />
<br />
What are the five hardest things you have overcome so far and what are they five that you foresee?<br />
<br />
What are my options to opt-out. Are these reasonable options?<br />
<br />
Who gets sued when something goes wrong?<br />
<br />
What are you changing between this system and the old system? What do you gain (variable rates, more throughput)? What do you see as the long term change.<br />
<br />
<br />
As a user of the system, what are the terms and conditions? What contract do I sign?<br />
<br />
Data <br />
I take a trip on the bus. From the time I swipe my card till the time I get off, where does the data go, what does it get added, and when does it it disappear?<br />
<br />
<br />
How long is the data kept and what form (aggregate) is it stored?<br />
<br />
Who has access to what data and how?<br />
Where is the data stored?<br />
How does KC Metro view ownership of data?<br />
How is it shared?<br />
Is there an audit trail? Transparency builds trust. <br />
Is there a way fix incorrect data?<br />
<br />
Can I look at data about me (as opposed to my data).<br />
<br />
What data is stored on the card and what is stored in the database? Are the unique identifiers salted on the card?<br />
<br />
How does data get back to the central database? Is it sent in the clear? Via wifi? smoke signals?<br />
<br />
Data retention. We know it is held for a min of 90 days, but what's the max? What data are you collecting and why?<br />
<br />
If there are one-use cards, what are the issuers entitled to (data wise)<br />
<br />
To Do<br />
Who will be there? <br />
We are not n00bs...<br />
Perhaps bring a lawyer and a technician</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6719Soctech seminar, Spring 20072007-05-09T22:23:21Z<p>Yanokwa: /* Whitepaper */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
== Whitepaper ==<br />
<br />
We'd like to create a whitepaper that could be given to the ORCA, University, and/or legislators based on what we see as acceptable practices for the ORCA deployment. See [[ORCA whitepaper]] or [[Open ORCA Questions]]<br />
<br />
== Administrative info ==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Seminar cancelled<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID – [http://www.cs.washington.edu/homes/yanokwa/soctech/Dan_Kaminsky-RFID-Attack-Surface.ppt Slides (ppt)]<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFID_Privacy_for_UW_ORCA.ppt Slides (ppt)], [http://www.cs.washington.edu/homes/yanokwa/soctech/Informal_RFID_Privacy_Guidelines.doc Informal RFID Privacy Guidelines (doc)]<br />
<br />
'''8 May''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats – [http://www.cs.washington.edu/homes/yanokwa/soctech/Covington_ORCAPresentation.ppt Slides (ppt)]<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6694Soctech seminar, Spring 20072007-05-08T21:29:05Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
== Whitepaper ==<br />
<br />
We'd like to create a whitepaper that could be given to the ORCA, University, and/or legislators based on what we see as acceptable practices for the ORCA deployment. See [[ORCA whitepaper]].<br />
<br />
== Administrative info ==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Seminar cancelled<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID – [http://www.cs.washington.edu/homes/yanokwa/soctech/Dan_Kaminsky-RFID-Attack-Surface.ppt Slides (ppt)]<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFID_Privacy_for_UW_ORCA.ppt Slides (ppt)], [http://www.cs.washington.edu/homes/yanokwa/soctech/Informal_RFID_Privacy_Guidelines.doc Informal RFID Privacy Guidelines (doc)]<br />
<br />
'''8 May''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats – [http://www.cs.washington.edu/homes/yanokwa/soctech/Covington_ORCAPresentation.ppt Slides (ppt)]<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6693Soctech seminar, Spring 20072007-05-08T21:28:56Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
== Whitepaper ==<br />
<br />
We'd like to create a whitepaper that could be given to the ORCA, University, and/or legislators based on what we see as acceptable practices for the ORCA deployment. See [[ORCA whitepaper]].<br />
<br />
== Administrative info ==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Seminar cancelled<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID – [http://www.cs.washington.edu/homes/yanokwa/soctech/Dan_Kaminsky-RFID-Attack-Surface.ppt Slides (ppt)]<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFID_Privacy_for_UW_ORCA.ppt Slides (ppt)], [http://www.cs.washington.edu/homes/yanokwa/soctech/Informal_RFID_Privacy_Guidelines.doc Informal RFID Privacy Guidelines (doc)]<br />
<br />
'''8 May''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats – [[http://www.cs.washington.edu/homes/yanokwa/soctech/Covington_ORCAPresentation.ppt Slides (ppt)]<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6664Soctech seminar, Spring 20072007-05-05T23:59:51Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
== Whitepaper ==<br />
<br />
We'd like to create a whitepaper that could be given to the ORCA, University, and/or legislators based on what we see as acceptable practices for the ORCA deployment. See [[ORCA whitepaper]].<br />
<br />
== Administrative info ==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Seminar cancelled<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID – [http://www.cs.washington.edu/homes/yanokwa/soctech/Dan_Kaminsky-RFID-Attack-Surface.ppt Slides (ppt)]<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFID_Privacy_for_UW_ORCA.ppt Slides (ppt)], [http://www.cs.washington.edu/homes/yanokwa/soctech/Informal_RFID_Privacy_Guidelines.doc Informal RFID Privacy Guidelines (doc)]<br />
<br />
'''8 May''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6639Soctech seminar, Spring 20072007-05-03T00:29:02Z<p>Yanokwa: /* Course Topics */ Added Shafer's slides.</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
== Whitepaper ==<br />
<br />
We'd like to create a whitepaper that could be given to the ORCA, University, and/or legislators based on what we see as acceptable practices for the ORCA deployment. See [[ORCA whitepaper]].<br />
<br />
== Administrative info ==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Seminar cancelled<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFID_Privacy_for_UW_ORCA.ppt Slides (ppt)], [http://www.cs.washington.edu/homes/yanokwa/soctech/Informal_RFID_Privacy_Guidelines.doc Informal RFID Privacy Guidelines (doc)]<br />
<br />
'''8 May''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Society_and_technology_alumni&diff=6583Society and technology alumni2007-04-17T02:58:48Z<p>Yanokwa: </p>
<hr />
<div>(part of the '''[[society and technology]] wiki''')<br />
<br />
Past members of (and collaborators with) soctech@cs...<br />
*[http://www.cs.washington.edu/homes/deibel/ Kate Deibel]<br />
*[http://www.cs.washington.edu/homes/klee/ Keunwoo Lee]<br />
*[http://www.cs.washington.edu/homes/tapan/ Tapan Parikh]<br />
*[http://www.cs.washington.edu/homes/valentin/ Valentin Razmov]<br />
*[http://www.cs.washington.edu/homes/creis/ Charlie Reis]<br />
*[http://www.cis.washington.edu/about/people/benner/default.asp Caroline Benner] (Center for Internet Studies)<br />
*[http://www.cs.washington.edu/ UW Computer Science and Engineering] students:<br />
**[http://www.cs.washington.edu/homes/djp3/homepage Donald J Patterson] aka Don<br />
**[http://www.cs.washington.edu/homes/jlnd/ Janet Davis]<br />
*[http://www.law.washington.edu/ UW Law] students:<br />
**[http://www.seedlaw.com/attorneys/dugan.html Ben Dugan]<br />
**David Orange<br />
<br />
[[Category:Society and technology]]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Society_and_technology&diff=6582Society and technology2007-04-17T02:58:37Z<p>Yanokwa: /* People and organizations */</p>
<hr />
<div>The society and technology interest group ('''soctech''') is an informal interest group that we are starting up among UW-CSE students to promote awareness of various social computing issues, in both CSE and the UW. We collaborate with other departments, with possible aims including the production of cross-departmental courses, lecture series, or white papers.<br />
<br />
We have a mailing list, '''soctech@cs'''. Here's [http://mailman.cs.washington.edu/mailman/listinfo/soctech the public list info page].<br />
<br />
==Goals of the SocTech group==<br />
*'''Connecting the social concerns, legal landscape, and technical aspects of transformative technologies''': In the university, it is often easy to get lost daydreaming about abstract theories or caught up in the inner workers of some protocol or mechanical gadget. We want to step back and understand the larger context within which much of our research is taking place. How does technology get incorporated into people's everyday lives? What concerns are being raised about the technologies in question? Are there actions that can be taken to address these concerns?<br />
*'''Dialogue between disciplines''': We want to establish common vocabulary between groups with different expertise. Disciplines bring different frames of reference on the problems that we all confront--whether its technical perspectives from CS or EE or legal expertise from students of the law or a rich understanding of social forces from sociologists and communications folks. Addressing the many possiblities and problems that face our information-intensive society require dialogue across these boundaries.<br />
*'''Dialogue with the public''': It is easy for us to debate sociotechnical issues to our heart's content, but it won't have much impact unless we try to make connections with the public at large. A better informed public can make better decisions about its (and our) future. Our position as university elite does not mean that we need to be elitist.<br />
<br />
==Seminar==<br />
The '''society and technology seminar''' (CSE 590 T, formerly CSE 590 SO) is a weekly seminar that brings together students and scholars from a variety of fields to discuss the impacts of computing (and other technologies) on the larger world. If you have ideas for a future soctech seminar, or would be willing to organize one, please contact the [[Society and technology#Coordinators|current soctech coordinator]]!<br />
<br />
The course is organized by [[Society and technology|soctech@cs]] and listed under the UW Dept. of Computer Science and Engineering, but undergraduate and graduate students in all departments are encouraged to sign up. Enrollment is open; see the pages for individual quarter offerings for details.<br />
<br />
===Current and past quarters===<br />
* [[Soctech seminar, Spring 2007]]: RFID Case study: ORCA cards<br />
* [[Soctech seminar, Fall 2006]]: RFID Technology<br />
* [[Soctech seminar, Spring 2006]]: Social Ramifications of Search Technologies<br />
* [[Soctech seminar, Spring 2005]]: Electronic books and media<br />
* [[Soctech seminar, Winter 2005]]: Software security, law, and public policy<br />
<br />
===Mailing list===<br />
Visit<br />
:https://mailman.cs.washington.edu/mailman/listinfo/cse590t<br />
to sign up for the course mailing list. Contact the [[Society and technology#Coordinators|current soctech coordinator]] if you have any difficulty signing up.<br />
<br />
==Other activities==<br />
We have also, at various times in the past and with varying levels of success, tried [[Past society and technology activities|other things]].<br />
<br />
==People and organizations==<br />
===Coordinators===<br />
<!-- Note to editors: leave the "Coordinators" heading intact as you reorganize this page, as, it serves as a link target. ---><br />
<br />
Current UW-CSE coordinator: [http://www.cs.washington.edu/homes/travis/ Travis Kriplean], [http://www.cs.washington.edu/homes/yanokwa/ Yaw Anokwa]<br />
<br />
Current UW law coordinator: Jim Sfekas<br />
<br />
===Other people===<br />
*[http://www.cs.washington.edu/homes/ckd/ Colin Dixon]<br />
*[http://www.cs.washington.edu/homes/evan/ Evan Welbourne]<br />
*[http://www.cs.washington.edu/homes/supersat/ Karl Koscher]<br />
<br />
(feel free to add your name here)<br />
<br />
*'''[[Society and technology alumni|Past members and collaborators]]'''<br />
<br />
===UW departments===<br />
We're in informal contact with most of these, or have been in the past. The extent to which we actually work with them varies widely.<br />
*[http://www.cis.washington.edu/about/ Center for Internet Studies]<br />
*[http://www.law.washington.edu/ UW School of Law]<br />
**Intellectual Property Program (led by [http://www.law.washington.edu/Faculty/Gomulkiewicz/ Robert W. Gomulkiewicz])<br />
**[http://www.law.washington.edu/lct/ Shidler Center for Law, Commerce, and Technology] (led by [http://www.law.washington.edu/Faculty/Winn/ Jane Kaufman Winn])<br />
**Technology and Law club (may be defunct)<br />
*[http://www.ischool.washington.edu/ UW Information School]<br />
<br />
==Resources==<br />
*'''[[Society and technology courses|Courses]]:''' At the UW, and elsewhere. Some of the online lectures are especially useful.<br />
*'''[[Society and technology people|People]]:''' Scholars, activists, etc.<br />
*'''[[Society and technology organizations|Organizations]]:''' Research centers, nonprofits, government<br />
*'''[[Society and technology conferences|Conferences]]'''<br />
*'''[[Society and technology online|Other online resources]]:''' Mailing lists, blogs, etc.<br />
<br />
[[Category:Society and technology]]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=ORCA_whitepaper&diff=6581ORCA whitepaper2007-04-17T00:43:09Z<p>Yanokwa: /* Questions */</p>
<hr />
<div>== Outline ==<br />
*Section 1 – Background/History of the ORCA <br />
** Where are we now, how did we get to be here?<br />
** Motivations<br />
<br />
*Section 2 – Background of RFID<br />
** Very high level, focus more on transit implications<br />
<br />
*Section 3 - RFID in Transit Systems<br />
** Potential Benefits<br />
** Oyster, Octopus, Charlie, etc.<br />
** ERG Group<br />
** Personnel Cost Savings<br />
** Maintenance Advantages<br />
** Financial Benefits<br />
** Other Benefits (law enforcement, university, city, state, etc)<br />
<br />
* Section 4 - ORCA Details<br />
** ERG Group<br />
** MiFare DESFire<br />
** Trip History<br />
** Data retention<br />
<br />
* Section 5 – Cautionary Anecdotes<br />
** A story says 1,000 images<br />
** Trust Your Data to People Who Manage Data [Not Trains]<br />
** Insider Abuse Has Major Risks<br />
** Holey Matrimony<br />
** Tracking Customers is Bad Business<br />
<br />
* Section 6 - Stakeholder Analysis<br />
** Why do we care?<br />
** Who else should care?<br />
<br />
* Section 7 – Deployment Considerations<br />
** Legal/Regulatory<br />
*** Audit trails (DC)<br />
*** Anonymity in warehousing?<br />
*** Data retention<br />
*** Rights to access? Across orgs?<br />
*** Is information that is passed between parties anonymized/aggregated?<br />
** Technical<br />
*** What's encrypted? When? How? Where?<br />
*** Who owns the keys?<br />
*** Who's writing the encryption code?<br />
*** Access control?<br />
*** Who makes cards?<br />
** Informing the public/media<br />
* Section 8 - Our Recommendations<br />
<br />
== Questions ==<br />
* Has ERG group had any kind of compromises?<br />
* How is data shared? Is it aggregated or unique records?<br />
* How do the privacy policies extend across organizations? Who owns and who can sell the data (UW? KC Metro?)<br />
<br />
== Action Items ==<br />
* contact MIT people (Yaw)<br />
* repurpose best practices from RFID clinic</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=ORCA_whitepaper&diff=6580ORCA whitepaper2007-04-17T00:41:10Z<p>Yanokwa: /* Questions */</p>
<hr />
<div>== Outline ==<br />
*Section 1 – Background/History of the ORCA <br />
** Where are we now, how did we get to be here?<br />
** Motivations<br />
<br />
*Section 2 – Background of RFID<br />
** Very high level, focus more on transit implications<br />
<br />
*Section 3 - RFID in Transit Systems<br />
** Potential Benefits<br />
** Oyster, Octopus, Charlie, etc.<br />
** ERG Group<br />
** Personnel Cost Savings<br />
** Maintenance Advantages<br />
** Financial Benefits<br />
** Other Benefits (law enforcement, university, city, state, etc)<br />
<br />
* Section 4 - ORCA Details<br />
** ERG Group<br />
** MiFare DESFire<br />
** Trip History<br />
** Data retention<br />
<br />
* Section 5 – Cautionary Anecdotes<br />
** A story says 1,000 images<br />
** Trust Your Data to People Who Manage Data [Not Trains]<br />
** Insider Abuse Has Major Risks<br />
** Holey Matrimony<br />
** Tracking Customers is Bad Business<br />
<br />
* Section 6 - Stakeholder Analysis<br />
** Why do we care?<br />
** Who else should care?<br />
<br />
* Section 7 – Deployment Considerations<br />
** Legal/Regulatory<br />
*** Audit trails (DC)<br />
*** Anonymity in warehousing?<br />
*** Data retention<br />
*** Rights to access? Across orgs?<br />
*** Is information that is passed between parties anonymized/aggregated?<br />
** Technical<br />
*** What's encrypted? When? How? Where?<br />
*** Who owns the keys?<br />
*** Who's writing the encryption code?<br />
*** Access control?<br />
*** Who makes cards?<br />
** Informing the public/media<br />
* Section 8 - Our Recommendations<br />
<br />
== Questions ==<br />
* Has ERG group had any kind of compromises?<br />
* How is data shared? Is it aggregated or unique records?<br />
<br />
== Action Items ==<br />
* contact MIT people (Yaw)<br />
* repurpose best practices from RFID clinic</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=ORCA_whitepaper&diff=6579ORCA whitepaper2007-04-17T00:35:39Z<p>Yanokwa: </p>
<hr />
<div>== Outline ==<br />
*Section 1 – Background/History of the ORCA <br />
** Where are we now, how did we get to be here?<br />
** Motivations<br />
<br />
*Section 2 – Background of RFID<br />
** Very high level, focus more on transit implications<br />
<br />
*Section 3 - RFID in Transit Systems<br />
** Potential Benefits<br />
** Oyster, Octopus, Charlie, etc.<br />
** ERG Group<br />
** Personnel Cost Savings<br />
** Maintenance Advantages<br />
** Financial Benefits<br />
** Other Benefits (law enforcement, university, city, state, etc)<br />
<br />
* Section 4 - ORCA Details<br />
** ERG Group<br />
** MiFare DESFire<br />
** Trip History<br />
** Data retention<br />
<br />
* Section 5 – Cautionary Anecdotes<br />
** A story says 1,000 images<br />
** Trust Your Data to People Who Manage Data [Not Trains]<br />
** Insider Abuse Has Major Risks<br />
** Holey Matrimony<br />
** Tracking Customers is Bad Business<br />
<br />
* Section 6 - Stakeholder Analysis<br />
** Why do we care?<br />
** Who else should care?<br />
<br />
* Section 7 – Deployment Considerations<br />
** Legal/Regulatory<br />
*** Audit trails (DC)<br />
*** Anonymity in warehousing?<br />
*** Data retention<br />
*** Rights to access? Across orgs?<br />
*** Is information that is passed between parties anonymized/aggregated?<br />
** Technical<br />
*** What's encrypted? When? How? Where?<br />
*** Who owns the keys?<br />
*** Who's writing the encryption code?<br />
*** Access control?<br />
*** Who makes cards?<br />
** Informing the public/media<br />
* Section 8 - Our Recommendations<br />
<br />
== Questions ==<br />
* Has ERG group had any kind of compromises?<br />
<br />
== Action Items ==<br />
* contact MIT people (Yaw)<br />
* repurpose best practices from RFID clinic</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=ORCA_whitepaper&diff=6578ORCA whitepaper2007-04-17T00:34:48Z<p>Yanokwa: /* Whitepaper */</p>
<hr />
<div>== Outline ==<br />
*Section 1 – Background/History of the ORCA <br />
** Where are we now, how did we get to be here?<br />
** Motivations<br />
<br />
*Section 2 – Background of RFID<br />
** Very high level, focus more on transit implications<br />
<br />
*Section 3 - RFID in Transit Systems<br />
** Potential Benefits<br />
** Oyster, Octopus, Charlie, etc.<br />
** ERG Group<br />
** Personnel Cost Savings<br />
** Maintenance Advantages<br />
** Financial Benefits<br />
** Other Benefits (law enforcement, university, city, state, etc)<br />
<br />
* Section 4 - ORCA Details<br />
** ERG Group<br />
** MiFare DESFire<br />
** Trip History<br />
** Data retention<br />
<br />
* Section 5 – Cautionary Anecdotes<br />
** A story says 1,000 images<br />
** Trust Your Data to People Who Manage Data [Not Trains]<br />
** Insider Abuse Has Major Risks<br />
** Holey Matrimony<br />
** Tracking Customers is Bad Business<br />
<br />
* Section 6 - Stakeholder Analysis<br />
** Why do we care?<br />
** Who else should care?<br />
<br />
* Section 7 – Deployment Considerations<br />
** Legal/Regulatory<br />
*** Audit trails (DC)<br />
*** Anonymity in warehousing?<br />
*** Data retention<br />
*** Rights to access? Across orgs?<br />
*** Is information that is passed between parties anonymized/aggregated?<br />
** Technical<br />
*** What's encrypted? When? How? Where?<br />
*** Who owns the keys?<br />
*** Who's writing the encryption code?<br />
*** Access control?<br />
*** Who makes cards?<br />
** Informing the public/media<br />
* Section 8 - Our Recommendations<br />
<br />
== Legal considerations ==<br />
<br />
== Technical ==<br />
* What's encrypted? When? How? Where? <br />
* Who owns the keys? <br />
* Who's writing the encryption code?<br />
* Access control?<br />
* Who makes cards?<br />
<br />
== Regulatory ==<br />
* Audit trails (DC)<br />
* Anonymity in warehousing?<br />
* Data retention<br />
* Rights to access? Across orgs?<br />
* Is information that is passed between parties anonymized/aggregated?<br />
<br />
== Questions ==<br />
* Has ERG group had any kind of compromises?<br />
<br />
== Action Items ==<br />
* contact MIT people (Yaw)<br />
* repurpose best practices from RFID clinic</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6570Soctech seminar, Spring 20072007-04-11T17:04:07Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA – [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6569Soctech seminar, Spring 20072007-04-11T17:03:43Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Slides (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf Slides (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6568Soctech seminar, Spring 20072007-04-11T17:02:48Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt (ppt)]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Intro to ORCA (ppt)]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA [http://www.cs.washington.edu/homes/yanokwa/soctech/RFCS_UWSocTech.pdf ACLU (pdf)]<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6566Soctech seminar, Spring 20072007-04-10T21:21:47Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Intro to ORCA Slides]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA<br />
<br />
'''17 April''' ORCA, Discussion<br />
<br />
'''24 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''26 April''' Dan Kaminsky, Hacker perspective on RFID<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6564Soctech seminar, Spring 20072007-04-10T20:00:24Z<p>Yanokwa: /* Resources */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Intro to ORCA Slides]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://cs.washington.edu/homes/yanokwa/soctech/MBTA_Privacy_Proposal_and_Paper.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6563Soctech seminar, Spring 20072007-04-10T19:55:24Z<p>Yanokwa: /* Resources */</p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11998 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11998 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
Sign up for the mailing list at https://mailman.cs.washington.edu/mailman/listinfo/cse590t if you are not yet on it!<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas (sfekas at u.washington.edu), Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications -- [http://www.cs.washington.edu/homes/travis/2007_spring_soctech_intro.ppt Slides]<br />
<br />
'''03 April''' ORCA and Husky Card overview — [http://www.cs.washington.edu/homes/ckd/pres/soctech-orca-intro-sp2007.ppt Intro to ORCA Slides]<br />
<br />
'''10 April''' Christina Drummond, ACLU on ORCA<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
'''Dan Kaminsky''', IOActive<br />
:The Hacker View on RFID<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]<br />
<br />
CDT Consumer Privacy Guidelines. [http://www.cdt.org/privacy/20060501rfid-best-practices.php]<br />
<br />
Octopus card implemented in Hong Kong. [http://en.wikipedia.org/wiki/Octopus_Card wikipedia article]<br />
<br />
Privacy considerations for a Massachusetts RFID transit system [http://www-swiss.ai.mit.edu/6.805/student-papers/fall04-papers/6.805_MBTA_-_FINAL_Privacy_Proposal_and_Paper.doc]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6541Soctech seminar, Spring 20072007-03-23T23:08:49Z<p>Yanokwa: </p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards'''<br />
<br />
Course: <br />
:CSE Students: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T<br />
:Non-CSE Students: SLN 11981 or CSE 590X (graded)<br />
<br />
Time: Tuesday 12:30-13:20<br />
<br />
Place: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
Notes: Courses SLN 11994 and SLN 11981 are identical. If you are a CSE student, sign up for the CSE course. If you are a non-CSE student, sign up for the non-CSE course. Email travis (at cs.washington.edu) if you need an add code.<br />
<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas, Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications<br />
<br />
'''03 April''' ORCA and Husky Card overview<br />
<br />
'''10 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' ACLU on ORCA, Guest speaker(s) from the ACLU<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6540Soctech seminar, Spring 20072007-03-23T22:54:29Z<p>Yanokwa: </p>
<hr />
<div>'''Spring 2007: Case study of ORCA/Husky cards''': <br />
<br />
Course Information: [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] or CSE 590T @ Tuesday 12:30-13:20. Non-CSE students (including law) should register for the graded CSE 590 X - SLN 11981. Email travis (at cs.washington.edu) for an add code if you need one. <br />
<br />
Room Information: [http://www.washington.edu/students/maps/map.cgi?CSE Paul Allen Center] [http://norfolk.cs.washington.edu/htbin-php/bldgmaps/floormap.php?room=CSE303 Room 303]<br />
<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas, Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications<br />
<br />
'''03 April''' ORCA and Husky Card overview<br />
<br />
'''10 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' ACLU on ORCA, Guest speaker(s) from the ACLU<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6539Mac Users:Suggested Applications2007-03-20T17:28:40Z<p>Yanokwa: /* Creation */</p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source.<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake.<br />
*[http://iterm.sourceforge.net/ iTerm] a full featured terminal emulation app written using Cocoa. Supports tabs.<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]<br />
<br />
==AntiVirus==<br />
Hahaha! No seriously, any antivirus solution will slow down your machine with all the scanning. Seeing as there are no known Mac viruses, the only reason to install it is to prevent spread of Microsoft macro viruses. I strongly recommend not installing any antivirus software and just regularly updating your OS software.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6538Mac Users:Suggested Applications2007-03-20T17:28:17Z<p>Yanokwa: /* Utilities */</p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source/<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake.<br />
*[http://iterm.sourceforge.net/ iTerm] a full featured terminal emulation app written using Cocoa. Supports tabs.<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]<br />
<br />
==AntiVirus==<br />
Hahaha! No seriously, any antivirus solution will slow down your machine with all the scanning. Seeing as there are no known Mac viruses, the only reason to install it is to prevent spread of Microsoft macro viruses. I strongly recommend not installing any antivirus software and just regularly updating your OS software.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6537Soctech seminar, Spring 20072007-03-15T21:28:36Z<p>Yanokwa: /* Course Topics */</p>
<hr />
<div>'''Spring 2007: Case study: ORCA/Husky cards''': [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] CSE 590 T, Tuesday 12:30-1:20, [http://www.washington.edu/students/maps/map.cgi?CSE CSE] 303'''<br><br />
Non-CSE students (including law) should register for the graded CSE 590 X - SLN 11981. Everything else is identical. Email travis (at cs.washington.edu) for an add code if you need one.<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We have an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas, Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications<br />
<br />
'''03 April''' ORCA and Husky Card overview<br />
<br />
'''10 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' ACLU on ORCA, Guest speaker(s) from the ACLU<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Kevin Desmond (KC Metro)<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6533Soctech seminar, Spring 20072007-03-12T23:27:49Z<p>Yanokwa: /* Potential Speakers/Organizations */</p>
<hr />
<div>'''Spring 2007: Case study: ORCA/Husky cards''': [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] CSE 590 T, Tuesday 12:30-1:20, [http://www.washington.edu/students/maps/map.cgi?CSE CSE] 303'''<br><br />
Non-CSE students (including law) should register for the graded CSE 590 X - SLN 11981. Everything else is identical. Email travis (at cs.washington.edu) for an add code.<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We started an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter and that can be extended in the future. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas, Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications<br />
<br />
'''03 April''' ORCA and Husky Card overview<br />
<br />
'''10 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' ACLU on ORCA, Guest speaker(s) from the ACLU<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Guest speaker from transit authority<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond''', King County Metro Transit<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Soctech_seminar,_Spring_2007&diff=6532Soctech seminar, Spring 20072007-03-12T23:27:29Z<p>Yanokwa: /* Potential Speakers/Organizations */</p>
<hr />
<div>'''Spring 2007: Case study: ORCA/Husky cards''': [http://www.washington.edu/students/timeschd/SPR2007/cse.html SLN 11994] CSE 590 T, Tuesday 12:30-1:20, [http://www.washington.edu/students/maps/map.cgi?CSE CSE] 303'''<br><br />
Non-CSE students (including law) should register for the graded CSE 590 X - SLN 11981. Everything else is identical. Email travis (at cs.washington.edu) for an add code.<br />
<br />
==Overview==<br />
<br />
This quarter, we will explore a specific local issue ([http://www.orcatest.com ORCA]/[http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 Husky cards]) as a concrete aspect of the more general issue of RFID technology so that we might inform the design, implementation, and regulation of a technology which will likely directly affect all of us in the near future. By the end of the quarter, we would like to produce a set of specific and reasonably implementable recommendations for the University of Washington and Seattle transportation agencies that would improve the privacy, efficacy and public confidence in ORCA/Husky cards.<br />
<br />
==Description==<br />
<br />
In the past few years there has been excitement, fear, and controversy about the transformative potential of radio frequency identification (RFID) technology as it gets more and more feasible to deploy widely. In a [[Soctech seminar, Fall 2006|previous seminar]], we explored the broader legal and sociopolitical implications of RFID, discussing privacy, security, and surveillance through conversations with invited RFID experts and enthusiasts each week. We started an ongoing [[UW Society and Technology Group RFID Position Paper|whitepaper]] based on our discussions during that quarter and that can be extended in the future. <br />
<br />
During the Spring quarter we are going to try something different: focus on a single,<br />
about-to-be-deployed technology in the Seattle region, specifically the<br />
[http://www.orcatest.com ORCA card] and its [http://uwnews.washington.edu/ni/uweek/uweekarticle.asp?articleID=26783 integration with the UW Husky card]. The ORCA card (One Regional Card for All) is a collaboration between Seattle transportation agencies that will establish a single, RFID-enabled transportation option for public transportation. The test run of the card finished in late 2006 and the ORCA card is now set to be deployed in early 2008. The University is working with the ORCA team to embed ORCA capability into the new Husky card, as well as establishing a quick pay option for the card with local businesses. <br />
<br />
By focusing on an issue close to home we will have the opportunity to discuss identity management, security, and surveillance<br />
issues with administrators from the UW and the local government. While these stakeholders have a great influence over the impact of technology on society, we, as academics, do not typically get the opportunity to interact with them. Moreover, because the ORCA/Husky card is still in its formative stages, our conversations with stakeholders may positively impact the conditions under which the card will be deployed. <br />
<br />
Participation in the Fall 2006 soctech seminar is not a prerequisite for this seminar. We will begin the seminar with a technical overview of the capabilities of RFID, the regulatory landscape on which laws will be crafted, and a number of existing RFID deployments. During the following weeks, we will invite a guest from a variety of organizations, including the university administration, Seattle public transportation agencies, law experts, and legislators.<br />
<br />
== Seminar Organization ==<br />
The seminar will be discussion-driven, each period led by a small group of seminar participants and/or invited guests. Seminar participants will be expected to generate questions for our guest before seminar, but there won't be pressure to organize a class period.<br />
<br />
Contact information: This course is being organized by Evan Welbourne (evan at cs), Colin Dixon (ckd at cs), Karl Koscher (supersat at cs), Jim Sfekas, Yaw Anokwa (yanokwa at cs), and Travis Kriplean (travis at cs).<br />
<br />
==Administrative info==<br />
<br />
Course grading and credit-load policies: Subject to change, but variable credits are available to meet differing levels of participation:<br />
*Sign up for 1 credit if you plan to attend, do the readings, and participate in discussions.<br />
*Sign up for 2 credits if you wish to organize a discussion by contacting a guest, coordinate their visit, and explaining why you chose them.<br />
*Sign up for 3 credits if you wish to be heavily involved in the planning process for the seminar. Contact the course organizers in advance if you plan to take this course for 3 credits.<br />
<br />
== Course Topics ==<br />
<br />
Note: subject to change as we find guest speakers<br />
<br />
'''27 March''' RFID History, Basic Technical Description and Overview of Applications<br />
<br />
'''03 April''' ORCA and Husky Card overview<br />
<br />
'''10 April''' Bill Covington, ORCA and liability, Technical and policy overview, potential privacy threats<br />
<br />
'''17 April''' ORCA, Stakeholder analysis<br />
<br />
'''24 April''' ACLU on ORCA, Guest speaker(s) from the ACLU<br />
<br />
'''1 May''' Steven Shafer, RFID privacy and personal information<br />
<br />
'''8 May''' Gov't representative from sponsors of Washington's new Electronic Bill of Rights<br />
<br />
'''15 May''' ORCA, Guest speaker from transit authority<br />
<br />
'''22 May''' ORCA and the Husky Card, Guest speaker from UW administration on Husky Card<br />
<br />
'''29 May''' ORCA, Discussion<br />
<br />
== Potential Speakers/Organizations ==<br />
<br />
'''Steven Shafer''', Microsoft Research<br />
:A policy for RFID Privacy, addressing personal information in RFID systems.<br />
<br />
'''Christina Drummond''', Director of Technology and Liberty Project, ACLU of Washington<br />
<br />
'''Doug Klunder''', Privacy Project Director, ACLU of Washington<br />
<br />
'''Bill Covington''', UW Law<br />
<br />
'''Kevin Desmond'''King County Metro Transit<br />
<br />
Sound Transit<br />
<br />
Community Transit<br />
<br />
Project Manager for Husky Card, Husky Card Account & ID Center Manager<br />
<br />
Gov't representative of sponsors of Washington's new [http://www.leg.wa.gov/pub/billinfo/2007-08/Pdf/Bills/House%20Bills/1031-S.pdf Electronic Bill of Rights]<br />
<br />
== Resources ==<br />
<br />
Privacy and Security in Library RFID : Issues, Practices, and Architectures. [http://www.cs.berkeley.edu/~dmolnar/library.pdf PDF]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6459Mac Users:Suggested Applications2007-03-06T19:23:54Z<p>Yanokwa: </p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source/<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]<br />
<br />
==AntiVirus==<br />
Hahaha! No seriously, any antivirus solution will slow down your machine with all the scanning. Seeing as there are no known Mac viruses, the only reason to install it is to prevent spread of Microsoft macro viruses. I strongly recommend not installing any antivirus software and just regularly updating your OS software.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Society_and_technology&diff=6456Society and technology2007-02-22T23:44:52Z<p>Yanokwa: /* Coordinators */</p>
<hr />
<div>The society and technology interest group ('''soctech''') is an informal interest group that we are starting up among UW-CSE students to promote awareness of various social computing issues, in both CSE and the UW. We collaborate with other departments, with possible aims including the production of cross-departmental courses, lecture series, or white papers.<br />
<br />
We have a mailing list, '''soctech@cs'''. Here's [http://mailman.cs.washington.edu/mailman/listinfo/soctech the public list info page].<br />
<br />
==Goals of the SocTech group==<br />
*'''Connecting the social concerns, legal landscape, and technical aspects of transformative technologies''': In the university, it is often easy to get lost daydreaming about abstract theories or caught up in the inner workers of some protocol or mechanical gadget. We want to step back and understand the larger context within which much of our research is taking place. How does technology get incorporated into people's everyday lives? What concerns are being raised about the technologies in question? Are there actions that can be taken to address these concerns?<br />
*'''Dialogue between disciplines''': We want to establish common vocabulary between groups with different expertise. Disciplines bring different frames of reference on the problems that we all confront--whether its technical perspectives from CS or EE or legal expertise from students of the law or a rich understanding of social forces from sociologists and communications folks. Addressing the many possiblities and problems that face our information-intensive society require dialogue across these boundaries.<br />
*'''Dialogue with the public''': It is easy for us to debate sociotechnical issues to our heart's content, but it won't have much impact unless we try to make connections with the public at large. A better informed public can make better decisions about its (and our) future. Our position as university elite does not mean that we need to be elitist.<br />
<br />
==Activities==<br />
*'''[[soctech seminar]]''': Weekly seminar/reading group held in CSE; open to all students<br />
:The seminar is our primary current activity; see the [[soctech seminar|individual quarter pages]] for more details.<br />
<br />
We have also, at various times in the past and with varying levels of success, tried [[Past society and technology activities|other things]].<br />
<br />
==People and organizations==<br />
===Coordinators===<br />
<!-- Note to editors: leave the "Coordinators" heading intact as you reorganize this page, as, it serves as a link target. ---><br />
<br />
Current UW-CSE coordinator: [http://www.cs.washington.edu/homes/travis/ Travis Kriplean], [http://www.cs.washington.edu/homes/yanokwa/ Yaw Anokwa]<br />
<br />
Current UW law coordinator: Jim Sfekas<br />
<br />
===Other people===<br />
*[http://www.cs.washington.edu/homes/jlnd/ Janet Davis]<br />
*[http://www.cs.washington.edu/homes/deibel/ Kate Deibel]<br />
*[http://www.cs.washington.edu/homes/klee/ Keunwoo Lee]<br />
*[http://www.cs.washington.edu/homes/tapan/ Tapan Parikh]<br />
*[http://www.cs.washington.edu/homes/valentin/ Valentin Razmov]<br />
*[http://www.cs.washington.edu/homes/creis/ Charlie Reis]<br />
(feel free to add your name here)<br />
<br />
*'''[[Society and technology alumni|Past members and collaborators]]'''<br />
<br />
===UW departments===<br />
We're in informal contact with most of these, or have been in the past. The extent to which we actually work with them varies widely.<br />
*[http://www.cis.washington.edu/about/ Center for Internet Studies]<br />
*[http://www.law.washington.edu/ UW School of Law]<br />
**Intellectual Property Program (led by [http://www.law.washington.edu/Faculty/Gomulkiewicz/ Robert W. Gomulkiewicz])<br />
**[http://www.law.washington.edu/lct/ Shidler Center for Law, Commerce, and Technology] (led by [http://www.law.washington.edu/Faculty/Winn/ Jane Kaufman Winn])<br />
**Technology and Law club (may be defunct)<br />
*[http://www.ischool.washington.edu/ UW Information School]<br />
*[http://www.soc.washington.edu/ UW Sociology]<br />
<br />
==Resources==<br />
*'''[[Society and technology courses|Courses]]:''' At the UW, and elsewhere. Some of the online lectures are especially useful.<br />
*'''[[Society and technology people|People]]:''' Scholars, activists, etc.<br />
*'''[[Society and technology organizations|Organizations]]:''' Research centers, nonprofits, government<br />
*'''[[Society and technology conferences|Conferences]]'''<br />
*'''[[Society and technology online|Other online resources]]:''' Mailing lists, blogs, etc.<br />
<br />
[[Category:Society and technology]]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Ski_Day_2007&diff=6435Ski Day 20072007-01-19T01:50:49Z<p>Yanokwa: /* People Needing Rides */</p>
<hr />
<div>= General Information = <br />
<br />
Ski Day is set for Friday January 19th at Stevens Pass. Hank is providing a pizza lunch at 12:30. <br />
We have the Trophy Room in the Pacific Crest Lodge reserved for lunch (and hopefully from 9am until 5:30pm). When you are facing up the mountain, it is in the leftmost lodge, on the 2nd floor. You can probably leave belongings in the room during the day if you like, and people can hang here during the day, but it will not be secured in any way, and we need to get our stuff out of there by 5:30. Lockers are available for a fee. If you are renting skis, please use the complimentary ski check at the mountain when you go inside.<br />
<br />
Apres Ski -- at the end of the day (4:00 or a little later) we will meet at the Bull's Tooth Pub for a hot chocolate or (for non-drivers) something stronger. The pub is on the 2nd floor of the Granite Peaks Lodge, the middle of the 3 buildings at the base of the mountain. You can find more details on this map [[http://www.stevenspass.com/mountain/map/]].<br />
<br />
We have a very large group and need to carpool to minimize the number of cars and to make sure everyone gets there. Please edit the wiki below to fill in information about the ride you need [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#People_Needing_Rides]] or the rides you can provide [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#People_Offering_Rides]] . Anyone taking a lesson needs to get there at 9 to rent equipment and be on the snow when lessons start at 10. See below for directions and other driving information [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#Getting_There]].<br />
<br />
It has been very cold lately, though it is predicted to warm up by Friday. Regardless, we will be in the mountains in the winter, so please dress warmly, bring extra layers, and bring a change of clothes (or at least socks). If you lack appropriate clothing or don't know what appropriate clothing is, please post your needs or questions below under [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#Ski_Clothing]]. If you have extra gear, please check below and help out your fellow CSE snow bunnies. Remember sunblock and hydrate well in preparation.<br />
<br />
Should be a great day!<br />
<br />
= Skier's Code =<br />
<br />
1. Always stay in control and be able to stop or avoid other people or objects. <br />
2. People ahead of you have the right of way. It is your responsibility to avoid them. <br />
3. You must not stop where you obstruct a trail or are not visible from above. <br />
4. Whenever starting downhill or merging into a trail, look uphill and yield to others.<br />
5. Always use devices to help prevent runaway equipment. <br />
6. Observe all posted signs and warnings. Keep off closed trails and out of closed areas. <br />
7. Prior to using any lift, you must have the knowledge and ability to load, ride and unload safely.<br />
<br />
= Getting Lift Tickets and Rentals =<br />
<br />
If you are not taking a lesson, go to Guest Relations in the Granite Peaks Lodge to purchase your lift ticket at the group rate-- tell them that you are from the UW CSE group. Nathan Escalona from Group Sales coordinated our trip, so if anything comes up you can mention him-- he should be helping our group in the rental shop. If you are getting a rental but not a lesson, you will have to pay Hank back ($26) for the rental after ski day, as he is fronting the money for these to preserve our group discount and make things easier for Stevens.<br />
<br />
If you are getting a lift/ rental/ lesson package, you will pay for everything and get your lift ticket at the rental shop. The rental shop is in the Tye Creek Lodge, and ours probably will be too, but they are setting up our gear in advance, so it might be in a slightly different spot.<br />
<br />
For ski rentals, make sure your boots fit well, this is necessary for control and comfort. You want them snugger than you'd wear a sneaker (ideally, you shouldn't really be able to lift your heel or twist your foot), but you want to be able to wiggle your toes.<br />
<br />
= Getting There =<br />
<br />
You can find directions here: [http://www.stevenspass.com/mountain/gettinghere/] <br />
They claim it will take 2-2.5 hrs from Seattle. <br />
<br />
(Slightly different route than their directions to avoid I5 and I405: Take Lake City Way heading towards Bothell. In Bothell you'll see signs to 522, follow them by turning right at the traffic light at Woodinville Drive. Stay on 522 until it ends at Route 2. Turn left onto Route 2 and follow to Stevens Pass. Be careful with speed limits -- on Route 2 you'll go through a bunch of little towns (Startup, Sultan, etc.) -- the speed limits drop as you're going through those "towns" and the cops there will pull you over if you're speeding. The drive should take less than 2 hours.)<br />
<br />
The road up to Stevens is rough in bad weather. It currently looks like the weather will be ok, but be careful. If you don't have 4-wheel drive you should carry chains just in case.<br />
<BR>You can check the weather here: [http://www.nwac.noaa.gov/products/SABNW]<br />
<BR>You can see current road conditions here (please check on Friday if there is a chance of a weather restriction): [http://www.wsdot.wa.gov/traffic/passes/stevens/]<br />
<BR>One option I recommend is parking in Sultan and paying $5 to take a shuttle the last 40 miles:[http://www.stevenspass.com/mountain/parking/shuttle_sultan.aspx]<br />
On Fridays, though, it only runs up at 8:30am and only runs down at 4:30pm.<br />
<br />
If you are taking a lesson, PLEASE arrive at the mountain by 9am to get your rental gear and make your lesson on time.<br />
<br />
Please sign up below if you need a ride or can offer rides-- we should try to fill all the cars!<br />
<br />
= People Needing Rides =<br />
Please edit the wiki and add yourself here if you need a ride to and from Stevens. Please indicate where you want to be picked up from (it probably helps if you can get to the PAC or can meet your ride at his/her place), your desired departure time from Seattle, your desired departure time from the mountain (if any), whether or not you will be bringing skis/snowboard in the car, and whether you need to get there at 9 for a lesson. <br />
<br />
You are responsible for finding your own ride, so check the ride listings on this page and contact drivers. Please remove yourself from here when you find a ride.<br />
<br />
EXAMPLE: Neva Cherniavsky - Eastlake, 8am-5pm (or whenever the bar closes), bringing snowboard, no lesson<br />
<br />
{| border=1<br />
!Name!!Location to be picked up at!!Leave Seattle?!!Leave Mountain?!!Bringing equipment?!!9 am lesson?<br />
|-<br />
|Roee Engelberg (roee@cs) || U-District/Allen Center || early || late || none || yes <br />
|-<br />
|Ethan (ethan) || U-Dist|| 7:30-8|| 5? || skis || no<br />
|-<br />
|CJ (cj) || Loyal Heights/Allen Center|| 6.30-7:30 || 5? || yes || no<br />
|-<br />
|...||...||...||...||...||...<br />
|}<br />
<br />
= People Offering Rides = <br />
Please edit the wiki and add yourself here if you can offer rides to and from Stevens. Please indicate where you will be leaving from, what time you will leave Seattle, what time you will leave Stevens, how many more people you can fit (please update this as your car fills), and whether you can fit skis/snowboard (basically, if you have a rack, or if the skis will take up a seat). If you like, you can also indicate who your passengers are. Please try to fill up your car by contacting people who need rides above.<br />
<br />
If you want a ride with someone, please verify with the driver through email before editing yourself into the car.<br />
<br />
EXAMPLE: Ethan Katz-Bassett, U District, 8am-5pm, 2 people with equipment or 3 without.<br />
<br />
* Richard Ladner, Ballard, 6:30 - 5:00, Sandra Fan. Roee. GYngve. I can pick folks up at the CSE building on the way. 4 people with equipment, 5 without.<br />
* <del>Jonathan Hsieh, Fremont, 6:30 - 5:00. Dan Halperin. Neva Cherniavsky. Aaron Kimball.</del> [car full]<br />
* <del>YongChul Kwon, U District/Northgate, 6:30 - 5:00. Fei Wu, Suporn Pongnumkul, Piatek Michael, Jjohn</del> [car full].<br />
* Anna Cavender, Lake City, 6:30 - 5:00. Craig Prince + Cherie Cheung.<br />
* <del>Tobias Oberlies, Ravenna/Campus, 7:00 - 5:30. Armin Hornung, Stefan Eckerfelt, Nguyen, Thach.</del> [car full]<br />
* James Lee, Capitol Hill, 6:45-coming back on Sat night. So this is probably not useful, but if you'd like to stay for another day we can give you a ride there and back. Big SUV- 3 people with equipment, 5 without.<br />
* Carl Ebeling, Wedgewood, will stop by CSE, 6:30 - 5:00. Krzysztof, Tyler, maybe + 1.<br />
* Dan Suciu, View Ridge, 7:00 - 4:30. I will have my two 7-years old kids in the car, and can take one extra person.<br />
* Stephen Friedman, U District/CSE, 7:00AM - 5ish. Have to get there in time for the lesson. Brian Ferris, Amy Wheeless. One more? <del>Have 3 free seats in the back of a Ford Taurus. Can squish 3 people without equipment, may be able to get 1 or 2 with equipment(via a fold down seat)</del>.<br />
* Allan Carroll, Kenmore, 7:00 - 5:00. Room for 1 or 2 depending on equipment.<br />
<br />
= Ski Clothing = <br />
<br />
Rentals include ski boots (or snowboard boots, if you go that way). I usually just wear sneakers to the mountain and change into dry socks as I put on my boots. You need a warm hat, gloves/mittens, pants, jacket, maybe a scarf/neckwarmer, ski goggles/sunglasses, and warm long socks (just wear one pair, even if they are thin). Underneath, wear layers for warmth and versatility if it warms up. Wool, silk, polyester, and polypro are better than cotton (which is not warm when wet). Ideally, the gloves, pants, and jacket should be waterproof or at least water resistant. Track pants/warmup pants work in a pinch. For more information on recommended clothing, go here: [http://www.abc-of-snowboarding.com/snowboardinggear.asp].<br />
<br />
If you don't have clothing appropriate for winter sports, post your needs here. If you have extra gear, please email people to help fill their needs.<br />
<br />
EXAMPLE: Ethan Katz-Bassett - I am unhappy with my color options. Looking for a blue coat and pink pants.<br />
<br />
Roee: short (and maybe stupid) question from an unexperienced: is a helmet part of the rentals?<br />
<br />
Ethan: I always wear a helmet and recommend it to everyone-- you never know when Hank might get out of control and run into you. I know one person who had her life saved by her helmet, and I've been knocked out twice even wearing mine. You can rent one for $8+tax at the rental shop, no reservation necessary. You can also rent lightweight ski pants and jacket for $33+tax-- bring layers to wear underneath.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Ski_Day_2007&diff=6406Ski Day 20072007-01-18T05:46:23Z<p>Yanokwa: /* People Needing Rides */</p>
<hr />
<div>= General Information = <br />
<br />
Ski Day is set for Friday January 19th at Stevens Pass. Hank is providing a pizza lunch at 12:30. <br />
We have the Trophy Room in the Pacific Crest Lodge reserved for lunch (and hopefully from 9am until 5:30pm). When you are facing up the mountain, it is in the leftmost lodge, on the 2nd floor. You can probably leave belongings in the room during the day if you like, and people can hang here during the day, but it will not be secured in any way, and we need to get our stuff out of there by 5:30. Lockers are available for a fee. If you are renting skis, please use the complimentary ski check at the mountain when you go inside.<br />
<br />
Apres Ski -- at the end of the day (4:00 or a little later) we will meet at the Bull's Tooth Pub for a hot chocolate or (for non-drivers) something stronger. The pub is on the 2nd floor of the Granite Peaks Lodge, the middle of the 3 buildings at the base of the mountain. You can find more details on this map [[http://www.stevenspass.com/mountain/map/]].<br />
<br />
We have a very large group and need to carpool to minimize the number of cars and to make sure everyone gets there. Please edit the wiki below to fill in information about the ride you need [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#People_Needing_Rides]] or the rides you can provide [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#People_Offering_Rides]] . Anyone taking a lesson needs to get there at 9 to rent equipment and be on the snow when lessons start at 10. See below for directions and other driving information [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#Getting_There]].<br />
<br />
It has been very cold lately, though it is predicted to warm up by Friday. Regardless, we will be in the mountains in the winter, so please dress warmly, bring extra layers, and bring a change of clothes (or at least socks). If you lack appropriate clothing or don't know what appropriate clothing is, please post your needs or questions below under [[http://abstract.cs.washington.edu/wiki/index.php/Ski_Day_2007#Ski_Clothing]]. If you have extra gear, please check below and help out your fellow CSE snow bunnies. Remember sunblock and hydrate well in preparation.<br />
<br />
Should be a great day!<br />
<br />
= Getting Lift Tickets and Rentals =<br />
<br />
Go to Guest Relations in the Granite Peaks Lodge to purchase your lift ticket at the group rate-- tell them that you are from the UW CSE group. Nathan Escalona from Group Sales coordinated our trip, so if anything comes up you can mention him. If you are getting a lift/ rental/ lesson package, pay for that at Guest Relations. If you are getting a rental but not a lesson, you will have to pay Hank back ($26) for the rental after ski day, as he is fronting the money for these to preserve our group discount and make things easier for Stevens.<br />
<br />
Ask at Guest Relations where you need to go for rentals and lessons. Rentals are normally in the Tye Creek Lodge, and ours probably will be too, but they are setting up our gear in advance, so it might be in a slightly different spot.<br />
<br />
For ski rentals, make sure your boots fit well, this is necessary for control and comfort. You want them snugger than you'd wear a sneaker (ideally, you shouldn't really be able to lift your heel or twist your foot), but you want to be able to wiggle your toes.<br />
<br />
= Getting There =<br />
<br />
You can find directions here: [http://www.stevenspass.com/mountain/gettinghere/] <br />
They claim it will take 2-2.5 hrs from Seattle. <br />
<br />
(Slightly different route than their directions to avoid I5 and I405: Take Lake City Way heading towards Bothell. In Bothell you'll see signs to 522, follow them by turning right at the traffic light at Woodinville Drive. Stay on 522 until it ends at Route 2. Turn left onto Route 2 and follow to Stevens Pass. Be careful with speed limits -- on Route 2 you'll go through a bunch of little towns (Startup, Sultan, etc.) -- the speed limits drop as you're going through those "towns" and the cops there will pull you over if you're speeding. The drive should take less than 2 hours.)<br />
<br />
The road up to Stevens is rough in bad weather. It currently looks like the weather will be ok, but be careful. If you don't have 4-wheel drive you should carry chains just in case.<br />
<BR>You can check the weather here: [http://www.nwac.noaa.gov/products/SABNW]<br />
<BR>You can see current road conditions here (please check on Friday if there is a chance of a weather restriction): [http://www.wsdot.wa.gov/traffic/passes/stevens/]<br />
<BR>One option I recommend is parking in Sultan and paying $5 to take a shuttle the last 40 miles:[http://www.stevenspass.com/mountain/parking/shuttle_sultan.aspx]<br />
On Fridays, though, it only runs up at 8:30am and only runs down at 4:30pm.<br />
<br />
If you are taking a lesson, PLEASE arrive at the mountain by 9am to get your rental gear and make your lesson on time.<br />
<br />
Please sign up below if you need a ride or can offer rides-- we should try to fill all the cars!<br />
<br />
= People Needing Rides =<br />
Please edit the wiki and add yourself here if you need a ride to and from Stevens. Please indicate where you want to be picked up from (it probably helps if you can get to the PAC or can meet your ride at his/her place), your desired departure time from Seattle, your desired departure time from the mountain (if any), whether or not you will be bringing skis/snowboard in the car, and whether you need to get there at 9 for a lesson. <br />
<br />
You are responsible for finding your own ride, so check the ride listings on this page and contact drivers. Please remove yourself from here when you find a ride.<br />
<br />
EXAMPLE: Neva Cherniavsky - Eastlake, 8am-5pm (or whenever the bar closes), bringing snowboard, no lesson<br />
<br />
{| border=1<br />
!Name!!Location to be picked up at!!Leave Seattle?!!Leave Mountain?!!Bringing equipment?!!9 am lesson?<br />
|-<br />
|Sandra B. Fan (sbfan@cs)||U-District/Allen Center||6:30 am|| no later than 5 pm || none || yes<br />
|-<br />
|Craig Prince (cmprince)||U-District/Allen Center||||||none||no<br />
|-<br />
|Cherie Cheung (cherie@cs)|| U-Village || 6 am || 5-6 pm || none || yes<br />
|-<br />
|Brian Ferris (bdferris@cs) + Amy Wheeless || U-District/Allen Center |||||| snowboard || yes<br />
|-<br />
|Roee Engelberg (roee@cs) || U-District/Allen Center || early || late || none || yes <br />
|-<br />
|Colin (ckd@cs) || U-District/Allen Center || early || late || no || yes <br />
|-<br />
|Ethan (ethan) || U-Dist|| 7:30-8|| 5? || skis || no<br />
|-<br />
|Yaw (yanokwa) || Cap Hill/Allen Center|| 6.30 am|| 5 pm || no || yes<br />
|-<br />
|...||...||...||...||...||...<br />
|}<br />
<br />
= People Offering Rides = <br />
Please edit the wiki and add yourself here if you can offer rides to and from Stevens. Please indicate where you will be leaving from, what time you will leave Seattle, what time you will leave Stevens, how many more people you can fit (please update this as your car fills), and whether you can fit skis/snowboard (basically, if you have a rack, or if the skis will take up a seat). If you like, you can also indicate who your passengers are. Please try to fill up your car by contacting people who need rides above.<br />
<br />
If you want a ride with someone, please verify with the driver through email before editing yourself into the car.<br />
<br />
EXAMPLE: Ethan Katz-Bassett, U District, 8am-5pm, 2 people with equipment or 3 without.<br />
<br />
* Richard Ladner, Ballard, 6:30 - 5:00, I can pick folks up at the CSE building on the way. 4 people with equipment, 5 without.<br />
* Jonathan Hsieh, Fremont, 6:30 - 5:00. Dan Halperin. Neva Cherniavsky. Aaron Kimball. [car full]<br />
* YongChul Kwon, U District/Northgate, 6:30 - 5:00. Fei Wu, Suporn Pongnumkul, Piatek Michael, Jjohn [car full].<br />
* Anna Cavender, Lake City, 6:30 - 5:00. 1 person with equipment or 2 without.<br />
* Tobias Oberlies, Ravenna/Campus, 7:00 - 5:30. Armin Hornung, Stefan Eckerfelt, Nguyen, Thach. Can fit a short person's equipment in the trunk.<br />
* James Lee, Capitol Hill, 6:45-coming back on Sat night. So this is probably not useful, but if you'd like to stay for another day we can give you a ride there and back. Big SUV- 3 people with equipment, 5 without.<br />
* Carl Ebeling, Wedgewood, will stop by CSE, 7:00 - 5:00. Krzysztof, Tyler, + 1 or 2.<br />
<br />
= Ski Clothing = <br />
<br />
Rentals include ski boots (or snowboard boots, if you go that way). I usually just wear sneakers to the mountain and change into dry socks as I put on my boots. You need a warm hat, gloves/mittens, pants, jacket, maybe a scarf/neckwarmer, ski goggles/sunglasses, and warm long socks (just wear one pair, even if they are thin). Underneath, wear layers for warmth and versatility if it warms up. Wool, silk, polyester, and polypro are better than cotton (which is not warm when wet). Ideally, the gloves, pants, and jacket should be waterproof or at least water resistant. Track pants/warmup pants work in a pinch. For more information on recommended clothing, go here: [http://www.abc-of-snowboarding.com/snowboardinggear.asp].<br />
<br />
If you don't have clothing appropriate for winter sports, post your needs here. If you have extra gear, please email people to help fill their needs.<br />
<br />
EXAMPLE: Ethan Katz-Bassett - I am unhappy with my color options. Looking for a blue coat and pink pants.<br />
<br />
Roee: short (and maybe stupid) question from an unexperienced: is a helmet part of the rentals?<br />
<br />
Ethan: I always wear a helmet and recommend it to everyone-- you never know when Hank might get out of control and run into you. I know one person who had her life saved by her helmet, and I've been knocked out twice even wearing mine. You can rent one for $8+tax at the rental shop, no reservation necessary. You can also rent lightweight ski pants and jacket for $33+tax-- bring layers to wear underneath.</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Getting_Started&diff=6320Mac Users:Getting Started2006-12-27T17:59:27Z<p>Yanokwa: /* Immediately annoying problems */</p>
<hr />
<div>== Getting started ==<br />
<br />
There are a set of things you'll want to your Mac right away. You should also sign up for the CSE Mac users mailing list [https://mailman.cs.washington.edu/mailman/listinfo/mac-users here]. <br />
<br />
=== Initial config ===<br />
<br />
Apple's initial configuration when you first start your Mac is pretty straightforward but there are a few catches.<br />
<br />
First, in order to print on campus, your short username has to match your CSE username. Second, do <b>not</b> configure your Internet connection. During setup, you should select 'no internet connection', as otherwise the registration software will attempt to contact Apple, which won't work because you haven't yet registered your MAC address, and take a long time to time out. <br />
<br />
Also note that you don't have to send any registration information to Apple, even though you need to fill it out in the initial setup form. If you claim that you don't have an internet connection, you never need to send it. You can also use the keystroke Apple-Q to quit the registration application -- your account creation will go through fine.<br />
<br />
=== Register MAC address ===<br />
<br />
You can do this [http://www.cs.washington.edu/lab/services/network/CSEnetAccess.html here].<br />
<br />
=== Immediately annoying problems ===<br />
<br />
Apple populates its new machines with some bloated applications and annoying initial settings. Chief among these is the i* applications, which take up a bunch of unnecessary disk space. You can remove the following:<br />
<br />
* GarageBand - A music creation program, takes up 2+ gigs. Remove /Applications/GarageBand and /Library/Application Support/Garage Band<br />
* iWeb - website creation targeted at home users, takes 630+ megs. Remove /Applications/iWeb<br />
* iMovie - movie editing software, takes 200+ megs. Remove /Applications/iMove HD and /Library/Application Support/iMovie<br />
<br />
Feel free to add more cruft here. All of these can be easily reinstalled from the install DVDs that come with your machine. Also, these and other applications clutter your initial dock, which you can easily remove by simply dragging them out of the dock.<br />
<br />
You can configure most global preference (mouse speed, key repeat rate, network config, etc.) in the System Preferences application, accessible by select 'System Preferences' from the Apple menu (it's at the top left, looks like a blue apple).<br />
<br />
=== Installing X11 and the developer tools ===<br />
<br />
By default, Apple does not include X11 or the GNU development toolchain. You need to install these yourself from the installation DVD that came with your computer, you'll find these by double clicking on the DVD (which appears on the desktop after you insert it).<br />
<br />
For X11, scroll down until you see the 'Optional Installs' package. Double click that, go through the initial few steps, and then expand Applications and select X11 when you need to specify what to install. <br />
<br />
To install the developer tools, open the Xcode Tools folder on the root level of the installation DVD and install the XcodeTools package similarly. Keep in mind that Apple updates its developer tools often, and the latest version is always available free at their [http://connect.apple.com/ ADC website]. You will need to setup a free Apple Developer account.<br />
<br />
== Services you probably want ==<br />
<br />
=== Mail ===<br />
<br />
Apple's Mail program is the default email reader for OS X, and supports IMAP reasonably well. Check [[Mac Users:Suggested Applications]] for other options.<br />
<br />
Configuring Apple's Mail program is fairly easy, with the small caveat that you need to accept that your account won't work after you go through the initial config when you first start the program. Instead, once you've gotten past the initial setup, you can get to more advanced settings via the Mail->Preferences... menu wherein you can change things for your account like SSL settings and IMAP prefix path (in the Advanced tab). <br />
<br />
Also, you may want to right click (hold control while clicking if you've got a single button mouse) on your folder list in Mail and select 'Use small mailbox icons' to make the icons a reasonable size.<br />
<br />
=== Web ===<br />
<br />
The default web browser in OS X is Safari in /Applications/Safari. Common problems generally involve tabbed browsing and popup blocking, both of which are off by default, but can be enabled from Safari->Block popup windows and Safari->Preferences->Tabs, respectively. Check [[Mac Users:Suggested Applications]] for other options. for other options.<br />
<br />
=== LaTeX, Gnuplot, and other UNIX stuff ===<br />
<br />
Check out [[Mac_Users:DarwinPorts_vs_Fink]]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6319Mac Users:Suggested Applications2006-12-21T02:13:03Z<p>Yanokwa: /* Creation */</p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source/<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6318Mac Users:Suggested Applications2006-12-21T02:12:45Z<p>Yanokwa: </p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Web==<br />
===Browsing===<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
===Creation===<br />
*[http://macrabbit.com/cssedit/ CSSEdit] is a modestly priced program that can really help out with CSS <br />
editing, which is one of the more tricky aspects of current web design.<br />
<br />
*[http://www.nvu.com NVU] seems reasonable and is open source/<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users&diff=6315Mac Users2006-12-17T07:37:19Z<p>Yanokwa: </p>
<hr />
<div>Using a Mac in UW CSE<br />
<br />
Please start moving [http://www.cs.washington.edu/homes/bershad/Mac/ Brian's work] into wiki format. For archival purposes, you can get a [http://www.cs.washington.edu/homes/yanokwa/macusers/bershad_mactutorial.zip zipped copy].<br />
<br />
<br />
[[Mac Users:FAQ]] Frequently Asked Questions<br />
<br />
[[Mac Users:Getting Started]] So you just got a new Mac<br />
<br />
[[Mac Users:Suggested Applications]] What do people use to do X?<br />
<br />
[[Mac Users:Printing 101]] How come I can't print?<br />
<br />
[[Mac Users:Backup 101]] Loosing data sucks. How do I prevent this?<br />
<br />
[[Mac Users:Remembering Windows]] How do you still use Windows on a Mac?<br />
<br />
[[Mac Users:DarwinPorts vs Fink]] Using UNIX ports on a Mac<br />
<br />
[[Mac Users:Getting Things Fixed]] Where to find Mac service<br />
<br />
[[Mac Users:Useful Mac Links]] Where to go on the web</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6314Mac Users:Suggested Applications2006-12-17T07:35:00Z<p>Yanokwa: /* Productivity */</p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
===Office===<br />
*[http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Browsing==<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]</div>Yanokwahttp://abstract.cs.washington.edu/wiki/index.php?title=Mac_Users:Suggested_Applications&diff=6313Mac Users:Suggested Applications2006-12-17T07:32:57Z<p>Yanokwa: /* General Downloading */</p>
<hr />
<div>This list are the applications that most use in CSE. We try to focus on applications that are free, inexpensive and open source. If such applications don't exist, we list the best piece of software in that category. If you want a specific piece of software, try [http://www.macupdate.com MacUpdate] and [http://www.versiontracker.com VersionTracker]. You can also send your question to the [https://mailman.cs.washington.edu/mailman/listinfo/mac-users mailing list].<br />
<br />
==Text==<br />
===Coding===<br />
*[http://macromates.com/ TextMate] is a brilliant general purpose text editor. It's good for coding, taking notes, managing repositories, latexing, etc. It's the hot new standard in OS X.<br />
*[http://www.barebones.com/ BBEdit] the old standard from the OS 9 days. Still very popular.<br />
*[http://www.barebones.com/products/textwrangler/ TextWrangler] is a free mini-BBEdit.<br />
*[http://www.codingmonkeys.de/subethaedit/ SubEthaEdit] is a novel collaborative text editor that some use.<br />
*[http://macvim.org/OSX/index.php Vim] in OS X.<br />
*[http://www.porkrind.org/emacs/ Carbon Emacs] is good for those who want an OS X native Emacs.<br />
<br />
===IDE===<br />
*[http://www.apple.com/macosx/features/xcode/ Xcode] is the Obj-C standard, but is good for all flavors of C (and some Java). If you are building OS X native software, you should use this.<br />
*[http://www.eclipse.org/ Eclipse] is the Java standard.<br />
<br />
===Tex===<br />
*[http://darkwing.uoregon.edu/~koch/texshop/texshop.html TeXShop] is TeX specific any editor is good.<br />
*[http://ktd.club.fr/programmation/latexit_en.php LaTeXiT] is for embedding quotations in any document.<br />
*[http://bibdesk.sourceforge.net/ BibDesk] is a good bibliography manager.<br />
<br />
==Graphics==<br />
*[http://www.omnigroup.com/applications/omnigraffle/ OmniGraffle] is great for creating posters, graphs and other vector based images.<br />
*[http://www.inkscape.org/ Inkscape] is an Illustrator clone and is good for free form work.<br />
<br />
==Productivity==<br />
* [http://www.neooffice.org/ NeoOffice] is a Mac friendly version of the free [http://www.openoffice.org/ OpenOffice].<br />
*[http://www.microsoft.com/mac/products/office2004/office2004.aspx?pid=office2004 Office 2004] is availabe from the department.<br />
*[http://www.apple.com/iwork/keynote/ Keynote] is Apple's presentation software.<br />
*[http://www.apple.com/iwork/pages/ Pages] is Apple's wordprocessing software..<br />
<br />
===Note Taking===<br />
*[http://www.hogbaysoftware.com/product/mori Mori]<br />
*[http://www.barebones.com/products/yojimbo/ Yojimbo]<br />
*[http://www.omnigroup.com/applications/omnioutliner/ OmniOutliner]<br />
*[http://homepage.mac.com/stewart.hector/home/software/software.html Notepad Widget] is good for quick notes<br />
<br />
==Browsing==<br />
*[http://www.caminobrowser.org Camino] is based on the Mozilla rendering engine, but unlike Firefox it is "Mac-y" in nature. It uses Keychain, OS X elements, etc. You can find optimized versions on [http://forums.mozillazine.org/viewforum.php?f=12 MozillaZine] and extensions at [http://pimpmycamino.com PimpMyCamino].<br />
<br />
*[http://www.apple.com/macosx/features/safari/ Safari] is the standard OS X browser. [http://webkit.org/ WebKit] is Apple's open source (and often faster) browser engine. Find extensions at [http://pimpmycamino.com PimpMySafari].<br />
<br />
*[http://www.firefox.com/ Firefox], is a cross-platform browser, but there are [http://www.beatnikpad.com/firefox processor optimized] versions available. Find extensions at [https://addons.mozilla.org/firefox/extensions/ Mozilla AddOns].<br />
<br />
If you are using, Camino or Firefox, you'll note that you don't by default have the ability to render PDFs in the browser. If you're running on an Intel mac, you're up a creek without a paddle, switch to Safari if you really need it. If you're using a PowerPC mac then you can download [http://www.schubert-it.com/pluginpdf/ PDF Browser], which basically puts Preview.app into the browsers<br />
<br />
==Chat==<br />
===AIM/MSN/YIM/Gtalk===<br />
*[http://www.adiumx.com Adium] (based on Gaim but pretty) because it's [http://www.ksuther.com/chax/ customizable] and allows for all the chat protocols in one client. It has medicore file transfer support.<br />
<br />
*Apple [http://www.apple.com/macosx/features/ichat/ iChat] paired with [http://www.ksuther.com/chax/ Chax]. <br />
<br />
===VoIP===<br />
*[http://www.skype.com/ Skype] is the VoIP standard.<br />
*[http://www.gizmoproject.com/ GizmoProject] is an OSS version of Skype.<br />
<br />
===IRC===<br />
*[http://colloquy.info/ Colloquy] is a popular Client<br />
*[http://www.irssi.org/ irssi] is fro the CLI IRC crowd.<br />
<br />
==Mail==<br />
*[http://www.apple.com/macosx/features/mail/ Mail]. Try [http://c-command.com/spamsieve/ SpamSieve] or it's free counterpart [http://junkmatcher.sourceforge.net/Home/index.html JunkMatcher] for better filtering. Use [http://harnly.net/software/letterbox/ LetterBox] to get three column layouts.<br />
*[http://www.mozilla.com/en-US/thunderbird/ Thunderbird]<br />
*[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]<br />
* [http://www.gyazsquare.com/gyazmail/ GyazMail] <br />
* [http://www.eudora.com/download/ Eudora]<br />
<br />
Mail tends to be more popular because it's easy and simple. Entourage tends to be the reverse of Mail, and Thunderbird sits in the middle.<br />
<br />
==Calendar==<br />
[http://www.apple.com/macosx/features/ical/ iCal]<br />
[http://www.microsoft.com/mac/products/entourage2004/entourage2004.aspx?pid=entourage2004 Entourage]. <br />
<br />
iCal tends to be more popular because it's easy and simple. Entourage tends to be the reverse of iCal but has better Exchange server support.<br />
<br />
==RSS==<br />
*[http://vienna-rss.sourceforge.net/vienna21.php Vienna] is an open-source client that works well.<br />
*[http://www.newsgator.com/NGOLProduct.aspx?ProdID=NetNewsWire NetNewsWire] (both pro and lite) are pretty good too.<br />
<br />
==PDF==<br />
*[http://pdfview.sourceforge.net/ PDFView] is vastly superior PDF Reader.<br />
*[http://www.adobe.com/products/reader/ Reader 8] is Adobe's offering.<br />
*[http://www.apple.com/macosx/features/pdf/ Preview]. <br />
*[http://www.yepthat.com/ yep] is like iPhoto for your PDFs<br />
<br />
==File Transfer==<br />
===FTP===<br />
*[http://cyberduck.ch/ Cyberduck] offers good FTP/SFTP support.<br />
*[http://rsug.itd.umich.edu/software/fugu/ Fugu] are nice but getting old.<br />
*[http://www.fetchsoftworks.com/ Fetch] works and is free for students.<br />
*[http://www.panic.com/transmit/ Transmit] is nicest of all but not free. <br />
<br />
===Torrents===<br />
*[http://www.azureuswiki.com/index.php/Intel_Macs Azureus] if you need lots of functionality and plugs-ins. <br />
*[http://sarwat.net/bittorrent/ Tomato Torrent]<br />
*[http://transmission.m0k.org/ Transmission]<br />
*[http://www.xtorrentp2p.com/ XTorrent].<br />
<br />
===General===<br />
*[http://www.yazsoft.com/ Speed Download] is the most popular.<br />
*[http://www.igetter.net/ iGetter] is free.<br />
<br />
==Music==<br />
===Listening===<br />
*[http://www.apple.com/itunes/ iTunes] is the standard and you can get some useful [http://www.dougscripts.com/ scripts].<br />
*[http://panic.com/audion/ Audion] old but good.<br />
<br />
===Managing===<br />
*[http://www.chaoticsoftware.com/ProductPages/MediaRage.html Media Rage] for doing managing artwork, tags, etc.<br />
*[http://jay.tuley.name/pages/software#ieatbrainz IEatBrainz] for automatic tag management, *[http://nclasssoftware.com/index.php/nClassSoftware/corripio/ Corripio] *[http://www.widget-foundry.com/widgets/amazonart.htm Amazon Album Art widget] is widget for getting art.<br />
*[http://homepage.mac.com/sroy/libra/ Libra] helps manage multiple libraries.. <br />
<br />
===Making===<br />
*[http://www.apple.com/ilife/garageband/ Garageband] is pretty good if you don't want any "pro" apps. *[http://www.hairersoft.com/Amadeus.html Amadeus] is a great sound editor. <br />
*[http://www.freeverse.com/soundstudio/ SoundStudio] is good too. <br />
*[http://audacity.sourceforge.net/ Audacity] is an OSS editor.<br />
<br />
==Video==<br />
===Watching===<br />
*[http://www.apple.com/quicktime/mac.html QuickTime] is great. Add [http://perian.org/ Perian] and [http://www.microsoft.com/windows/windowsmedia/player/wmcomponents.mspx Flip4Mac] to make it better.<br />
*[http://www.videolan.org/vlc/ VLC] plays almost all formats.<br />
*[http://mplayerosx.sourceforge.net/ MPlayer] is less popular but works as well.<br />
===Making===<br />
*[http://www.apple.com/finalcut/ iMovie HD, Final Cut Express HD, and Final Cut Studio]. Which one you pick depends on what you want to do (and spend).<br />
<br />
==Burning Software==<br />
*[http://www.apple.com/support/tiger/burn/ Finder] has built-in burning.<br />
*[http://www.roxio.com/enu/products/toast/titanium/overview.html Toast] is the burning standard.<br />
*[http://burn-osx.sourceforge.net/ Burn] is a free alternative.<br />
<br />
==Photos==<br />
*[http://www.apple.com/ilife/iphoto/iPhoto iPhoto] Simple and easy. *[http://www.adobe.com/products/photoshop/family.html Photoshop] The legendary phototool.<br />
*[http://www.lemkesoft.com/en/graphcon.htm GraphicConverter] Good for quick edits and batch processing.<br />
*[http://gimp-app.sourceforge.net/ Gimp.app] Not quite Photoshop, but close and free.<br />
<br />
==Navigation==<br />
*[http://www.obdev.at/products/launchbar/index.html LaunchBar] gets you instant access to apps, documents, search engines, etc. It's extremely quick, stable and has limited features.<br />
*[http://blacktree.com/apps/quicksilver/ Quicksilver] is a similar to LaunchBar. It's open source, has a ton more features, but is less stable.<br />
*[http://www.cocoatech.com/ Path Finder] A replacement for the Finder<br />
<br />
==Notification==<br />
*[http://growl.info/ Growl] allows applications that support Growl to send you notifications. It's generally a useful thing to have installed. <br />
<br />
==Backup==<br />
*[http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html SuperDuper] makes a bootable image of your hard drive.<br />
*[http://www.econtechnologies.com/site/Pages/ChronoSync/chrono_overview.html Chronosync] makes versioned incremental backups of any folder you specify.<br />
<br />
==Utilities==<br />
*[http://www.titanium.free.fr/pgs/english.html OnyX] helps you run system maintenance tasks and configure hidden parameters.<br />
*[http://sourceforge.net/projects/applejack AppleJack] is a similar utility to OnyX but runs in single user mode.<br />
*[http://www.ragingmenace.com/software/menumeters/ MenuMeters] is a system monitoring, cpu, network throughput, disk, memory, etc.<br />
*[http://www.charlessoft.com/ Pacifist] Look into pkg, dmg, .tar, etc files and pull individual files out.<br />
*[http://wakaba.c3.cx/s/apps/unarchiver.html UnArchiver] A much more capable replacement the built-in archive unpacker program in Mac OS X.<br />
*[http://docs.blacktree.com/visor/visor Visor] a systemwide terminal window accessible via a hotkey, much like the consoles found in games such as Quake<br />
<br />
==Remote Desktop==<br />
*[http://cord.sourceforge.net CoRD] Cocoa OSS client for Intel.<br />
*[http://www.microsoft.com/mac/downloads.aspx?pid=download&location=/mac/download/misc/rdc_update_103.xml&secid=80&ssid=10&flgnosysreq=True Microsoft RDC] MS client for PPC. <br />
*[http://rdesktop.darwinports.com/ rdesktop] in DarwinPorts<br />
*[http://pdb.finkproject.org/pdb/package.php/rdesktop rdesktop] in Fink<br />
<br />
*[http://sourceforge.net/projects/cotvnc/ Chicken of the VNC] Cocoa VNC client<br />
*[http://www.nomachine.com/download-client-macosx.php NX] FreeNX client<br />
*[http://www.apple.com/remotedesktop/ Remote Desktop] from Apple<br />
<br />
==Windows==<br />
*[http://www.parallels.com/ Parallels] Popular virtualization solution<br />
*[http://www.apple.com/macosx/bootcamp/ BootCamp] Boot a native copy of Windows<br />
*[http://www.vmware.com/mac VMWare] Currently in beta.<br />
*[http://www.codeweavers.com/products/cxmac/ CrossOver] Provides a Win32 API for some apps<br />
<br />
If you do a lot of hardware or graphics intensive work, use Bootcamp. If you need a full fledged Windows install try Parallels. If you only have one app and it's supported by Crossover, then use that. If you want know the differences, try this [http://www.notebookreview.com/printArticle.asp?newsid=2990 Guide for Choosing Boot Camp or Parallels to Run Windows on an Apple MacBook]</div>Yanokwa