Skip to main content

Twitter is a 'starfish' enabler

Twitter is a 'starfish' enabler. It's what makes Twitter powerful and empowers those who use Twitter. It puts individuals at the center of the star.

Twitter friends (followers) are more like information flows you choose, organizing the flow of information for yourself and others, curating, editing, creating than other social network friends, which are more passive, something you collect or at most create a space to explore. This is because friends/followers bring content to you automatically. It is the flows of information resulting from following that make Twitter different from other social networks.

I didn't know much about Twitter when we started designing Farmfoody.org and thought it was something to do with short text messages on cell phones. I am currently integrating Twitter into farmfoody.org, after having considered a Facebook social feed model and finding it overly complex and confusing. We need as low a barrier to participation as possible. Farmers don't have time for complex systems, blogging, social feeds with posts and comments and threads and six dfferent types of publishing and bold and italic.

Neither do people standing at a farm stand with a bag of white corn tucked in their arm have time for complexity. It turns out that the social bulletin system we were envisioning two years ago exactly describes the information flows in Twitter. The way your friends (followers) tweets (messages) aggregate on the Twitter homepage is identical to how we envisioned messages from our users collecting on the user's profile page. In our bulletin system, all the friends of a user receive a bulletin, similar to the "homepage" on Twitter, creating an information flow. The only difference is bulletins are like craigslist ads and expire. That original requirement for bulletings to operate as classified ads with an expiration date, similar to craigslist, held us back. I should have looked into Twitter integration then, since we would not have needed to develop one of our own.

Comments

Popular posts from this blog

Minolta Lenses on a Four Thirds Camera

During the summer, I bought an Olympus E-510 digital single lens reflex camera. The 510 is a FourThirds camera and because of the of shallow flange of the 4/3 lens mount it is one of the most flexible cameras on the market when it comes to mounting legacy optics (lenses from traditional film SLRs). A 4/3 camera can mount "legacy optics" or lenses from several other manufacturers made before the DSLR era. Although unintended, this makes FourThirds a revolutionary mount. For the first time not only can a photographer mount lenses from different manufacturers who produce lenses to the "open" FourThirds standard, with inexpensive Chinese-made adapters lenses from nearly any manufacturer from the golden age of SLRs can be mounted as well. Third party adapters can be found for Olympus OM, Nikon, Pentax, Zeiss and Contax. The only one missing from the party was Minolta. I purchased an inexpensive OM to 4/3 adapter from ebay and mounted several OM lenses, a 50mm f/1.8, 50m...

Reading Tweets

I see a new kind of writing being created on Twitter, including hashtags, mixed into the text, in a variety of creative ways. In future, we should see a system that allows users to make these kind of connections, but without needing to include obscure computer-like commands in their text. I sometimes feel I'm reading a Linux command line or script when reading some tweets. Sometimes, it takes a moment to figure out what the tweet means.

Facilitating the Conversation

I was prompted by something Andrew Shafer of Reductive Labs said (on the FooCampers list, so I won't reproduce it here, since it was forwarded to me) about the quality of communication among software developers. He was talking about how communicating the overall design and intentions of the project is vital, so the developers are not left guessing about how the application will be used and what its architects think it should do. What is important is the existence of a conversation between the leaders of a project and the developers writing the code. This hits very close to home, because our farmfoody.or g project is essentially there to improve the flow of information between producers and consumers of food, to enable a conversation . It occurred to me the solution is to throw away the flash cards and bulleted design specifications and just facilitate the conversation. Why not use social networking tools for developers to communicate? (You can get a sense of another approach from ...