Lessons learned from

SETI@home Operations

Radio SETI projects

History and statistics

Public-resource computing

Characterizing SETI@home

Be prepared for crowds

Network bandwidth costs money

How to get and retain users

Reward users

Let users express themselves

Users are competitive

Anything can be reverse engineered

Users will help if you let them

Client: mechanism, not policy

Cross-platform is manageable

Server reliability/performance

What’s next for public computing?