Filtering is not Web 2.0 thinking 

Web 2.0 implies filtering through people 

• Identify roles 
• Roles contradict democratization 

Alternatives 

• Generate less information 
• Generate summaries 
• Voting, "most thumbs up" 
• How to avoid the "tyranny of the majority"? 
• E.g., Digg has become "not the place to go" -- full of teens adding irrelevant content 
• "The tipping point" of social media 
• Context-sensitive labelling 
• Let's use software engineering knowledge to relate information and reduce the burden of information overflow 
• Automated categorization 
• Interaction mining Curation vs. popularity Interruption management 
• "Don't do email all day" -- don't read tweets all day 

Is there an evolutionary drive to consume as much information as possible? 

• Should governments regulate social media? 

The importance of process of using Web 2.0 

• E.g. not responding immediately to tweets (like email: doing it only one hour in the morning) 
• Is reading tweets required? How many tweets do you read? 
• Assumptions have to be formalized -- it's about the relationships -- implicit 

If there are many channels (wiki, twitter, email, IM) people will not know which channel to use 

As Web 2.0 gets more important, "switching off" Twitter, Facebook (e.g., for maintenance) becomes problematic 

Web 2.0 services need to be cloneable Digital privacy -- new laws 

Should we study how web 2.0 mechanisms are used? Risk of not knowing what's going on

Privacy and Ethics

Example: Use of Twitter at conferences 

• Can we quote people on twitter? 
• What about mis-quotes on Twitter? Does self-correction work? 
• The importance of etiquette / ethics of using Twitter 

Few companies have Twitter etiquette rules, more have rules about blogging 

Lawyers understand social media (at least some of them) 

• Social media law is an emerging topic 
• International differences -- software development across borders 

Ethical obligations to OSS developers before reading their communication? 

• Depends on license 
• Moral vs. legal 
• Try to communicate with the people who created the artifacts 
• Anonymize at beginning or end? 

What are good metaphors for employer privacy? 

• Your boss goes into your office without your knowledge and reads all your notes and looks in your filing cabinet and then uses that information against you in a performance review 

Open source is like a "public art project" 

• They are performing in public ("although they may not be aware of it") 
• Does a company "own" interactions a developer had with, e.g., an IDE or TFS? 

IDE to Browser

(How much) of the IDE should be in the browser? 

Tool builders are interested 

Add web 2.0 plugins in existing IDEs 

• Getting a fast editor is hard enough 
• Browsers aren't quite there yet 

Challenges: organization on the server, naming scheme 

Social conventions to deal with concurrency 

Reasons to move to the browser 

• Accessibility (apply fix in the airport) 
• Collaboration 
• Data integration 
• Same configurations for everybody
• "The future" 
• Superficial reasons 

Data in the cloud does not imply browser 

Examples: 

• WebVelocity Smalltalk http://www.cincomsmalltalk.com/main/products/webvelocity/ 
• Palm WebOS http://developer.palm.com/ 
• Heroku http://heroku.com/ 
• Bespin https://bespin.mozillalabs.com/ 
• EyeOS http://eyeos.org/ 
• Atlas http://280atlas.com/ 
• Uses Web technologies and was supposed to be a web-based IDE 
• Community voted against it because of code ownership fears 

Vote: IDE to browser? 

• Yes 10, No 4.5, Maybe 1