asdf

adsadfa

Test

AJDFAFKJ

TEST

//||

TEST

//||

TEST

Bessaadaadsdddddddfafaafdft

TEST

Bessaadft

TEST

Best

TEST

TEST

Wk 5 Notes

Mobile Social Software

- Thinking about social interactions.
- Desktop -> Mobile Technology
- Mobile phones -> ubiquitous handheld computing
- LCD = SMS
- Massive uptake of mobile phones (98% in AUS)
- Need to decide early on to use SMS or not

-Mobile phones thought to be intrusive
-Norms established for technology, etiquet, and rules.
-Private world invading public
-When rolling out the technology think of context and social implications.

Social + mobile
- When?
- fist thing in the morning, work, home, uni, doing something else.

What do we do with it?
- Chat, keep up with contacts, media sharing, sharing
- blurring boundaries, workplace/private

How does mobile technology change this?
-More accessible, any place, any time. Some restrictions.
-Different expectations.
-more intrusive.
-transportable friends.
-augmenting conversation.

MOSOS Application
-More than mobile browsing.
-Location sensitive
- guides, games, matchmaking

Design considerations
-push vs pull, asking or pushed out
-authority to author
-available to all vs specific technology required
-wi-fi chalking.

Wk4: Social Software

Wk4: Social Software

- Software that supports group interaction
- deals with groups not individuals.

8 Challenges (Grudin 1994):
1. Disparity in work & benefit
2. Critical mass & prisoners dilemma
3. Disruption of social processes
4. Exception handling
5. Unobtrusive accessibility
6. Difficulty of evaluation
7. Failure of intuition
8. The adoption process

Shirky 3 things to accept
1. You can't completely separate the technical and social issues.
2. Members are different than users
3. The core group has rights that trump individual rights in some situations

Shirky: 4 things to design for
1. Handles the user can invest in, penalties for switching, reputation management
2. Design a way for there to be members in good standing
3. Barriers to participation, has to be hard for some users
4. Spare the group from scale.

Understanding groups
- differs by size, composition of group
- conformity, norms, consensus

Wk3 Notes

CSCW Architecture:
- systems need to support multiple parties asynchronously and geographically distributed.

Centralised Architecture
- consistency easily achieved but slow doesn't scale well. Simple to understand-

Replicated Architecture
- Quicker, more responsive. Scales well, More complex. Difficult to keep consistent

Hybrid Architecture
- Responsive, Consistency but complex.

-WYSIWIS
-undo
-transparency, awareness
-synchronisation

-Methods for showing who your collaborating with and how.

Week2 Lecture Notes: CSCW

-Groupware can be categorized into one of 4 distinct types.

• Synchronous Distributed Interaction (chat)
  
• Ashynchronous Distributed Interaction (email)
  
• Face-to-face Interaction
• Asynchronous Interaction (bbs)
  

Conversation:
- There are implicit rules that are followed when people interact

- These will depend on cultural context and particular occasions e.g. job interview, chat w/ friends

-eg. Turn taking rules: don't interrupt

- Breakdowns: deliberate, unconsiously, methods exist to remidy breakdown.

- These breakdowns and methods to repair them will vary according to the medium or method used in the interaction. Eg. conversation on phone.


Coordination:
- Schedules, timetables, shared calendars, hand signals

-Designing to support coordination

- Privacy, social engineering.

- allow for compromise and negotiation, 'social protocols'


Awareness:
- Knowing who is around, who is talking to who

- Supporting awareness: notifications, 'google docs', show proximity...


Key Point:
Software must take into account the context in which the software will be used
for it to be effective. Having an elaborate means of communication via software when
collabrative members will be next to each other will not work.

First Post

Sigined up with blogger. Need a post to test the rss feeds.