designing for community

“we want to be the myspace of financial traders” !!!

mikeindustries.com/myspace ? — his articles on the topic.

one-way web vs. two-way web. best way to describe what web 2.0 really is.

(why yes, I am still getting going.) where people interacting with each other improve the site. most examples will be from the news industry, because that’s where his interests are now.

one-way web example: NYT. great site, but the expert POV.

WaPo, with holovaty, is going more two-way.

the inverted pyramid: all the important stuff at the top. (goes back to the Civil War era?!)

how did it get started? in a panel he was on recently, 4 different people had 4 different people. now, in syndication, don’t know how much room will be available, so make it cut-able.

newsvine approach is the hourglass, as it tapers off, the comments take off and go into other directions. “hey, I shot a guy in the face there too.”

increasing loyalty by allowing comments.

“much more leveragable”? CNN (200 people) vs newsvine (6 people).

goals of sites. review sites want good reviews across genres. social bookmarking wants people who know what tags are. corked…started because owner wanted to know more about why. finding people who share similar interests.

more than just being social. friendster didn’t do anything but be social networking. in comparison to flickr: social network on top of a great photo service.

never lose site of what your product is separate from the social networking aspect.

active vs. passive users. pay attention to your passive user: everybody starts that way. (who are the passive users on OlyBlog? what do they want/need?) the 1%, 10% of users who create/mixup content need the audience of the 90%.

newsvine: a story that has a lot of votes and no comments is interesting, but non-controversial (or uncomfortable to comment on), or a story with a ton of comments but view votes. “bush acknowledges racism still exists…getting smarter [sotto voce]” best thing is a story with a lot of votes AND a lot of comments.

hmmmm…C might dig newsvine. he loves Google News, and it looks like a souped-version.

delicious hasn’t paid attention to the passive user, which may be creating a barrier to entry. (he asked if anybody had to explain it, and I popped up with my experience with C. took freaking FOREVER, but now he loves it.)

worst example: mark canter’s people aggregator. (hm, that’s baffling looking.) entertaining usability bashing. 🙂 video: “control all the people in your network”?! mmmm, buzzword-tastic. plus, randomly, his kids.

marc canter has his own category on valleywag.

dipping toes in the water, with customizing w/out registering. example: findory. (like the personal list feature on our directory. oh, hey, that gives me an idea.) and moderating.

make registration as light as possible. newsvine is reducing their already light registration form. ajax for checking what names are available. (oooh, try that for book exchange!)

give people something to do immediately after registration.

reputation building. three versions of identity: real identity, anonymity, pseudo-anonymity. real is mostly for stuff like banking. most of what you see in social sites is pseudo-anonymity. (MeFi, OlyBlog, etc., etc.)

how to create a system that rewards good long-time users w/out punishing new/untested users. (look at ebay rating system?) vineacity? get one rung for free. and a 2nd one is easy if you just hang around and don’t do anything.

adjust early & often.

quote from veen: on post “intellectual bargain shopping” — quote from nietzsche. in essence: users aren’t stupid, they’re mentally efficient.

questions….

noticed you added chat rooms, and nobody ever seems to use them? what’s up with that? like walking into a bar, don’t see anybody there, and leave. hasn’t done well, esp. in re: how good they thought it was going to be.

how is community interaction working out? newsvine “code of honor” — not anarchy! (cute graphic.)

business model? we are an advertising-based business. but with only 6 employees, they don’t need a lot of ads. also talking to some other news assets about licensing the technology.

technology? mostly open source. PHP, standards-compliant HTML/CSS. MS-SQL?

the new community

damn it’s cold in here. and I know it’s crazy hot outside. sounds like it could be record-breaking over the weekend, up into the 90s. it always is when I go to Webvisions.

dude, Nick Finck is following me! huh, Derek designed the blogger logo.

he’s a darn lively speaker.

virtual community. his book in 2000, in the last part of the last chapter, 4 pages about blogging. now you can’t talk about virtual community w/out talking about blogging.

“feels like something slightly new going on”

grrr…he’s reading his slides.

definition of community “you know it when you see/feel it” ability to use voice in public/immediate way forming relationships over time. (that works for me.)

george pullman: the company town. what happens when one guy controls the whole community. cut everybody’s salary, but left up prices/rents. “they burnt that sh!t down”

bulletin boards, usenet (blah blah blah), the well: as the company town.

blogs: you are your own company town. shows of hands to prove idea of decentralized conversations, commenting on other people’s ideas. (pace Ralph’s commentary on that topic.)

connective tissue, sidewalks of the intarwebs. “trackbacks, which are more or less dead” and all the usual stuff, technorati, blogrolls, and so on and so forth. “nobody’s talking about that one.”

boingboing used to have comments, but everybody picked on everybody else. “nobody graffiti’s their own house”

aggregators, by interest or location. pb on the spot!

as the age of company town diminishes, how will we find each other?

memes as proof of life. (four things. hey, did any/all of the people I tagged actually do it?)

what’s different? is this good for us? he thinks so. no boss-man can turn you out. human-scale …the vastness is part of why I dropped off of mefi.

“no one to cry to when someone is mean to you” (am reminded of joeclark: he just cries out to the whole world. ;))

flickr is a company town; manager: “she’s my wife, she’s very nice.” but they understand that they live in a different world; more ways to get pics out than in. (tho they aren’t EASY now.)

when amazon started, you could post your review, lots of reviews, but no way to show “joe’s awesome reviews” until the common POV changed.

livejournal, also a company town, but allows public/private boundaries.

when you think about real-life communication, we don’t talk to the whole world at once. we wear different hats. he thinks this thing we’re doing — same to everybody — will be seen as a historic anomaly. (vs. joeclark & the death of privacy)

if you run a company town “turns out we’re really the man!” (OlyBlog?) — treat them well: you need them more than they need you. “anybody who says ‘we’re creating community’ is lying to you.” example of JPG Magazine: instead of starting their own tool, they created a flickr group. go to where they are. look for the communities that pre-exist: there’s already a community for almost everything.

life cycle ideas of online community….

“nowhere to go but up” yay! optimism!

comment from audience: threadless, on profile pages, has places to pull in flickr photos, delicious links, last.fm, own blog, etc. acknowledgement of diversity of selves?

“maybe that’s where the e from flickr went” superglue

“less of a social benefit to being a dickhead” in a decentralized system.

“the gentleman mentions fray” — a company town: he picked/edited/created questions, etc. wanted people to tell stories, but now that’s happening all the time, all over. if it comes back, it’ll have to be different.

what piece of the puzzle is still missing? if he could invent a fantasy tool, talk directly to our communities w/out being a company town. making it/blogosphere smarter about human relationships w/out anybody being in charge.

what about 9rules, etc.? (I’m checking my email, etc., instead of paying attention.)

how does bringing money in change the community? (mefi has a “cover charge” now) in the decentralized model, money doesn’t come into it, except to create the site. “ask matt” of course, people in the audience already know the answers. example of craigslist charging people who “should pay”.

mobile phones & mobile web

Nick doing the intro again! Original presenter couldn’t make it, so his (Nick’s) business partner Brian Fling is speaking instead. Brian runs Idea Day (?)…one of the few mobile experts [in the US, as the Norwegians (or Asians!) will tell you]. runs mobiledesign.org (did I get that right?) blue favor director of strategy.

Brian used to work for, and is inspired by, the planned presenter. Will be mashing up both presentations. One person has some experience, the rest of us are blank stares.

Mobile is not the Web. Can’t just go buy a book and figure it out. 200+ devices in north america. (1000+ devices worldwide) device fragmentation is a huge part of the problem. and then…30+ browsers. hail mary mother of jeebus. some hope: a lot of them are various flavors of a previous version. most phones are locked down. carrier controlled ecosystem. no sh!t. napster would never happen with mobile. “to make it a better experience” but also a frustration. I/O limitations. not a lot of resources available: if David hadn’t been a close personal friend, he wouldn’t be where he is today. (!!!!) “Mobile Mondays” mobilemonday.com “no standards” — but that’s not true; more standardized in some ways because of the controlled ecosystem. and consumers (in US) don’t “get it”. (And in US it’s painfully expensive, IMHO.)

goddamn telcos.

jargon alert: “G” – 1G to 3G, with some decimal points in between. 1G …omg, I used to babysit some kids of a guy who had one of those, “car phone”! 2G, not so clunky, but just phones. “2.5G” is about where we are now…cheaper airtime. data capacity, but not much use. or we are at 3G?

LBS: location-based services. GPS chips, location-aware. locality to information.

skipping thru a bunch of stuff. ARPU — average revenue per user. or, how the carrier fsck over the consumer by charging for one thing 72 different ways. also, see Walled Garden. (Ala ye olde AOL.)

chart of carriers w/networks, platforms, etc.

some questions about walled garden issues, streaming, etc. storage space? (I jumped over to email briefly.)

awesome graphic! the device bomb. and then a big grid of pictures of phones.

mvno: mobile virtual network operator. Virgin, ESPN, etc. run on top of an operator/carrier platform. models by carrier, only double it to go back a year or two.

motorola is huge because of popular because of the razr: every carrier has them.

1 1/2% of phones are windows mobile….

pick 5 popular phone to support. how to know what’s popular? see what they’re giving away for free. 🙂 check periodically. people always go for the cheepest phone.

184 available devices available. 38 have audio playback, 64 have video streaming or playback. (it was kind of a PITA to find a tmo phone that plays music.)

Java/BREW support. Verizon is BREW, all else is Java.

more devices in US that support Flash Lite? No. hasn’t been released yet. Samsung has adopted for phone UI.

US is only country he knows of that subsidizes phones, and that drives the slowness of uptake.

Overwhelming majority of phones are “feature phones” — 120 px wide! presentation is on the website.

how many people are taking advantage of the features? and he goes on to talk about all the crazy nifty things that CAN be done. but it’s not happening. early failures. “mobile’s been hyped up.” spent more time talking with lawyers to do licensing for music/ringtones….

people still see their phones as phones.

getting cheaper to get better connection.

prediction: “mobile will revolutionize the way we gather & interact with information in the next three years.”

GOGL SMS queries.

zeldman’s head popping up randomly on the web 3.0 slide.

what do you serve by being mobile? find a need & fill it. nice chart/grid that he almost flashed past. (lots of little iterations, between hardware issues and connections to carriers.) wurfl(.sourceforge.net?) — open source database of phones.

how do you understand the limitations of each carrier? way he’s seen it solved in the past: have one contact at each carrier. (yeah, as if.) wikipedia (!) has info about carriers in North America. huh.

W3C believes in one web, with CSS to control the presentation. “.mobi” domain breaks the web in a fundamental way, according to TBL.

one web vs. mobile web debate.

options… the do-nothing approach. php script that strips stuff (other sorts of progammatical reformatting). alternate stylesheets. “handheld” to automagically reformat visuals.

stylesheet methodology doesn’t address context issues.

“mobile publishing is easy.” throw WML out unless you have extra resources. use XHTML.

I wonder what would be useful for students? (send me my schedule by SMS?)

questions about us vs. the rest of the industrialized world. japanese don’t have computers, so they use the phone. average US house has 1 1/2 computers, plus we are a ginormous country. (no mention of the endless bullsh!t that the telcos put us through.)

reminder service as a great example. if I paid for the bigger SMS plan, I’d probably use something like that. 🙂 again, I think that might be a nice spot for us.

publishing tools “like Movable Type” make perfect mobile web platforms. would wordpress do the same?

slides will be on blue flavor’s site.

rapid dom/ajax development

It took me a while to decide which panel to go to — I was very tempted by the social sharing session — but I decided I needed something really nerdy to kick it off.

I was going to try to do some work on a couple of side projects this afternoon, but I’m not working in my familiar computing environment, so I don’t think it’ll happen. 🙁 I suppose that’s more polite to the speakers, tho. 😉

Whoa, it’s crowded! As in, asking people to make room. I hope that bodes well.

Too much noise out in the hall…Nick Finck is doing a kinda dull intro.

Kewl, now the mic is on. I can hear him. Going to cover: his experience. Slides to be available afterwards.

What is DOM Scripting/AJAX? Quick definitions. I like that he uses Jeremy Keith’s term. they’re both just javascript. shouldn’t it be rapid javascript? has to keep up buzzword quotient.

people underestimate what’s possible. functional programming language: can pass functions to functions, and get functions as result of function. [okay, why?]

anonymous functions. function() { } vs function loadImages() { } — I missed why they’re good.

useful for callbacks, etc.

closures. means that we have access to internal scope variables. (I thought that was a bad thing?) example.

keys to rapid development: maintainability. finding bugs, managing the work of others. extensibility. flexibility. tieing to specific JS libraries, page class names.

using a coding style. no such thing as a real constant in JS, but by using syntax, tell self or others in the future that it shouldn’t be changed.

namespace. a variable that contains all of your particular scripts. weird.

underscores for internal methods. which methods to use or not.

he talks too fast…or maybe just fast AND vague.

singleton, design pattern which means there is only one of that item. use either object notation or the New keyword. can no longer create more versions of that object. event management is a good use of singletons. I feel like I’m missing something. also good for animations, use of timing. (C found a singleton beetle during an insect survey at Evergreen, years ago!)

object notation syntax. (what all this means, in short, is that between JS & PHP, I finally need to learn OOP)

use debug tools. excellent tool is firebug for firefox.

trace http calls — live http headers firefox extension — for AJAX more particularly. to see what’s happening.

on extensibility….

callback: Call this function when I’ve done something.

override. uses s5 as an example; this is the first thing that I can start to see concretely. the problem I have is that I think concretely, in examples, and these examples, for the most part, are very symbolic.

on flexibility….

don’t use predefined class names or element names. okay, here’s another good example, not tying to a library.

separation of behavior from presentation from content. don’t change styles directly, change the class name instead. element.className = ‘error’ vs. element.style.color = ‘red’

attach to elements. scope issue. I sorta get that.

libraries to avoid reinventing the wheel. (have we actually invented the wheel yet?)

reduce the mundane (document.getElementById() vs. $()) and/or create effects (primarily to reduce the gruntwork of cross-browserness)

more examples, mostly from Prototype. add/remove class names, particularly in situations where an element may already have a class. (I remember that example from the DOM Scripting book.) also example from JQuery. (have I seen jquery?)

click-to-expand FAQ. hey, neato!

chainable methods — receive object, perform action and so on, all in one line.

“sizzle” — fading sliding etc etc.

good libraries help, and fulfill his 3 requirements for good rapid development. “play well with others”

“which library should I use?” default answer: it depends; what are you trying to accomplish? avoid overkill. ooooh, comparison chart! name, size & compressed vs. uncompressed. Yahoo library is ginormous, but alacart: only pull in what you need. Dojo is similar.

and then there’s AJAX. nowadays anything with JS seems to get called AJAX. ways to improve connections to server. JSON. parsers exist for many serverside langs, incl. PHP. JSON Transformations? XSLT syntax. (yipes! run for the hills!)

two ways to call a json value — dot syntax vs. square bracket. (so, for java people vs. php people?) a way to do dynamic select lists.

use innerHTML. (isn’t this one of those religious debates.)

premade html shells — populate with data as ready, faster than innerHTML.

again: use a library.

where to from here: usability (dexterity example re: drag-drop shopping cart), accessibility. test, test, test!

what kind of compression? removed carriage returns, comments. could make smaller using gzip on server.

common pitfall for new developers: not testing enough. assuming that stuff will just work.

plugged back in

I’m back to being continuously connected, at least for the next day and a half. 🙂 In true geek convention fashion, I’m sitting on the floor juicing up a laptop, checking my email, looking at my aggregator (755 items!), and yes, writing this post.

The trip down to Portland was the journey of near-disasters. We went the long country way instead of taking I5, going around the back of Mt St Helens. We almost hit a deer, then we got stuck in a ditch, but two very nice women in a very large truck helped pull the car out with a chain. The drive around the mountain was gorgeous but uneventful. (Reminder to self: Iron (???) campground would be a really nice place to stay. The associated picnic area was quite lovely.)

We camped on Monday night at Battle Ground Lake State Park. It was something of a shock after driving all day in the middle of nowhere, to come out into the town of Battle Ground, and to have the first thing we saw be a brand shiny new Fred Meyer, in a strip mall with two Starbucks (one was inside FM)…with the same sale, even, as the one we were shopping on Sunday night in Lacey.

The campground was very well maintained, and the staff cheerful. The drive-in spots were pretty much full, but we’d booked ahead…and had a spot 3 minutes walk from the bathroom! There are also walk-in spots, and during our walkaround later in the evening, those spots looked to be mostly empty. Something good to note for later.

The lake itself is gorgeous. Alas, all I had was my cameraphone, so no pics. It’s an old volcanic cone, like a flatter Crater Lake, and there’s a trail all the way around.

Of course, in a final near-disaster, I took a good hard tumble on the rocks on our 2nd walk around the lake. I lost my footing and went down in a crazy upside-down pose. But…no cuts, only a couple of minor scrapes, a bit of soreness in my left shoulder, and a huge blue-purple bruise on my calf. And we made it the rest of the way around in the twilight, no more missteps.

The last time I went camping, I hardly slept a wink, because I could feel every little bump, and there was absolutely no cushioning underneath my hips. This time, I bought an air pad ahead of time, and slept like a rock.

I had an early morning walk around the lake, while C was still dozing, and as the sun was cresting over the edge of the crater. (Oh how I love summer at this latitude!) Mist was rising off of the water, and the air was cool & soft. Just about perfect.

After a little breakfast, we drove down to Portland and hooked up with my old friend Tom. I’ve known Tom since ’97, when we worked at United Way together, when I was an administrative assistant, and he was working on the Web site (among other things), and that’s one of the things that got me into this biz. Also, Tom was one of the witnesses to my wedding. He’s only just recently come back to Portland from the UK, and is being gracious enough to let us crash on a futon in his living room. (It’s a great place: a house from the 20s that’s been converted into two apartments, in a lively neighborhood.)

So far we’ve had great Mexican food, pizza, and homemade Thai. Yum…one of my favorite things about Portland (which is one of my favorite places) is the great food. Plus we had breakfast at Roxy’s yesterday; we go there every time we’re in Portland. (The Soylent Green omlette? Highly recommended.)

I am on C’s new laptop, which we bought yesterday (educational discount + no sales tax!), and trying to figure out how this OSX thing works.

The last two days, we’ve spent the afternoon on the beach at Sauvie Island, just kinda dozing in the sun/dappled shade, swimming in the mighty Columbia. Also, I’ve been working my way through the last book of the Baroque Cycle. (Which fscking RAWKS.)

This morning I skipped the morning panels and instead we went to the Chinese Garden downtown. A little dowdy, with some stagnant spots of water, but generally quite lovely and inspirational.

It was good (where good = refreshing, meditative, and theraputic for my hands) to be mostly disconnected for a few days. It is equally good (where good = invigorating, engaging, and creative) to be back online.

going away for a bit

We are going camping for a few days, and then to Portland, partially to visit Tom, partially to go to WebVisions.So I will be out of all electronic range for a bit, and then liveblogging like mad. I’m really, really, really looking forward to a little getaway.

Of course, my camera is scheduled to come back from Sony repair on Wednesday. 🙁 But I finally replaced ye olde cellphone with something with a camera in it, so I can take some (albeit crappy) photos.

My only worry about being gone is the state of my garden…we’re supposed to get some warmer weather this next week, and I won’t be around to fuss. (This has happened every time I go to WebVisions; two? three? years ago, most of my garden DIED during that week.) But a good friend, who is also an attentive gardener himself, has promised to look in on both plants and kitties while we are gone.

So…see you (online) in a few days!

links for 2006-07-15

links for 2006-07-13