Showing posts with label Andrew Long. Show all posts
Showing posts with label Andrew Long. Show all posts

16.2.10

TOS and Privacy (Class 11) - Andrew Long

Happy User Strategies
1) Simplicity. Empower users who may not be very technically savvy.
2) You need to set guidelines on how to behave also privacy policy on how information shall be used.
3) Posting/asking questions stimulates community.
4) Explaining status of your service - let users know what is happening pref. with personality.
5) Transparency. Ensure communication is open so users know what hapens.
6) Flame Wars. Watch and manage. Also: angry people can cause problems - how do comm mods deal with this to save losing members.
7) Rewarding users for contribution. Reward systems increase community participation.
8) Mixing. Taste the community. Devs provide ingredients and users make the recipe. Consistency in all aspects of community.
9) Super Loyalty! In users and Devs.
10) Provide ways for users to give feedback.
11) Speed, performance, reliability - also references to Geek movies.
12) Provide good support.
13) Diversity of membership.
14) Common-sense design.
15) Trolls.
16) Value for money. Capital.
17) Who is in charge? No bullying and harassment.
18) Justice. Exercising good judgment.
19) Engagement. Find out what audience is engaged by. Potential age-issues.

TOS and Privacy Policy
Govern all aspects of data-life-cycle.
Outlines expectations of behaviour and responsibilities for both parties -  or rights and obligations.
Signing up is tantamount to agreement to policy.

Types of Info Collected
Mandatory personal: collected on registration - vital for having an account.
Optional personal: Identity driven, useful but not essential. These can improve Social Media services but those services are not predicated on providing said info.
Log information: Automatic - IP, browser, page visits. Third party services e.g. Google Analytics. Cookies.

Privacy
Must satisfy legal requirements but this is a terribly fraught area. Particularly around jurisdictional issues. And it is an area I can't really go with so little time...

18.1.10

Keeping the Peeps (Class 10) - Andrew Long

How do we keep people in our community?

What is the lifeblood of community? "He tangata, he tangata, he tangata."

Typical Community Members
Newbies, guests, visitors: rejuvinate the community over time.
Regulars: do all work and make up bulk of community members. Regularly contribute and therefore shape the community by modeling/reprimanding certain behaviour.
Leaders: energy and skill to take community in particular direction. Help convert newbies to regulars.
Elders: Became weary of day-to-day stuff. Active as repositories of knowledge. Peripheral watchers lurking in the shadows.
Lurkers - not connected, don't contribute: we want to convert these to our lurkers to regulars.

How do we Retain Active Community Membership?
Work Slides
a) Aspect of community. b) Strategy to improve community leading from this aspect.
1)a) Simplicity is Key. b) Keep everything simple-don't over-complicate things.
2)a) Policies to make expected behaviours explicit. b) Keep policies in a public directory and current.
3)a) Think outside the box. b) Being creative will provide new opportunities for members.
4)a) Provide (free) compensation for unexpected down-time. b) Giving people something interesting means they will be more amenable to lack of service.
5)a) In/visibility. b) Provide a way for people to be graphically identified - provide people with a voice.
6)a) Flame War. b) Prevent flame wars before they start - through policies and monitoring.
7)a) Incentives. b) Nerds love being rewarded - provide rewards for involvement in community.
8)a) Stick to the recipe. b) Ensure new fang-dangled-things don't remove previous usability.
9)a)Animals are cute. b) Have animals somewhere on your site; the cuter the better.
10)a) Feedback. b) Have adequate conduits for feedback and ensure you listen to the users-tell them so.
11)a) Speed. b)Ensure your community is not slow to use/load
12)a) Tech Support b) Ensure there is fast, friendly, active response to technical issues.
13)a) Fostering diversity - incl. linguistic. b) Ensure that there are adequate rules to make newbies feel comfortable; if newbies have a bad experience early on then they are likely to not become regulars.
14)a) Accessible via symbols - removing need for language. b) Menu items designated by symbols (particularly "universal" symbols) means people with different linguistic abilities/frames of reference can feel comfortable navigating your site.
15)a) Trolls. b) Trolling should be explicitly prohibited and people who troll should be removed/sanctioned. This action should be carried out reasonably publicly so that people know what sort of behaviour is expected; utilise the Panopticon.
16)a) Money (broadly capital/value). b) If there is no capital flowing (social or fiscal) then there is little chance of sustainability - ensure your community has this flowing.
17)a) Intimidating behaviour from regulars. b) If regulars intimidate newbies then they will not become regulars themselves. Ensure that everyone provides an open, supportive environment. This is best dealt with by private messaging; don't make a mountain out of a molehill.
18)a) Justice. b) Ensure that people are treated fairly and that there are explicit ways of handling disputes.
19)a) Kiddisafe. b) Ensure that there is a way for "adult" material to be posted so that it is not accessible by minors. Similarly, if a person contributes material that may be of an adult nature, this should be readily identified as "NSFW" so that the person viewing the material can decide when or if they wish to proceed.
20)a) People will put their own interpretations on the community - they will make of it what they will. b) Although there should be rules describing acceptable or unacceptable behaviour (and to satisfy legal requirements) these should not be overly prescriptive; too many rules can strangle a community and also reduces the autonomy of self-governance/group governance.