Epeus' epigone

Edifying exquisite equine entrapments

Showing posts sorted by relevance for query flow. Sort by date Show all posts
Showing posts sorted by relevance for query flow. Sort by date Show all posts

Friday, 7 August 2009

The Flow Past Web: even better than the RealTime thing

The 'RealTime Web' may be a name we are stuck with, but it is still a misleading one. Real-time software is a well-defined field where computing has to complete or fail cleanly by a deadline, because latency is paramount. A two-way phone conversation is an example - if the delay between parties exceeds a few hundred milliseconds, normal conversation becomes impossible, and people have to formally take turns. This is because a true verbal conversation is a flow state, where you are both engaged and responding.

With text, the latency requirement can be relaxed - historically conversations have been conducted by exchanges of letters with latencies in weeks. What's happening is that all kinds of media are having their latency domains expanded.

Technological constraints used to make buffering audio or video prohibitively expensive, so they only domain they could work in was real time, hence Telephony's interruptive call model, and Radio and Television's 'one way to many people at once' model. As storage has got cheap and ubiquitous, these give way to answerphones, TiVo's, iPods and YouTube.

At the same time, the latency of text has been moving the other way, from newspapers' and mail's daily cycles, to hours for webpages, minutes for blogs down to seconds for SMS, Twitter, Facebook and other activity streams. However, as audio and video have added persistence, text hasn't lost it - we do have the ability to review and catch up with the past of our flows, or to re-point people to older points in time, as well as marking out times in the future.

Text's natural parallelism means we are seeing new kinds of public flow states that we have become used to as private ones - hence the "Twitter is public IM" explanation; but the other addition needed to make this stable and not a cacophony is the semi-overlapping publics that mean we don't all see the same flow, but that it is mediated by the people we choose to pay attention to.

Much of the supposed 'Real-Time' web is enabled by the relaxation of realtime constraints in favour of the 'eventually consistent' model of data propagation. Google Wave, for example, enables simultaneous editing by relaxing the 'one person can edit at a time' rule in favour of reconciling simultaneous edits smoothly.

As Robert Hof says:

"Real-time" is actually a bit of a misnomer. Most of this activity doesn't truly occur in real time, the way talking on the phone does, and social gestures such as sharing links with friends are just as important a part of the appeal as immediacy

Instead, we should think about a web that flows past, a web where the flow is important, as well as its past. The Flow Past web.

Posted by Kevin Marks at 11:54 20 comments:
Labels: Flow Past Web, RealTime

Wednesday, 27 September 2023

Plus Theory

I wrote a post last year about Buzz theory, and the year before about Twitter theory, so I thought I'd compare how Google+ (hereafter Plus) fits in with them too.

Flow

Plus is a flow but it is re-ordered by responses to posts. It has a second flow of Notifications, that not only has an unread count (though it caps out at 9+), but that lurks atop every Google page, drawing you back in as you search or read gmail. What it chooses to notify you about are people who follow you (now mercifully collated into clumps, comments on your posts, and people plussing you (the equivalent of twitter @replies). Like Buzz, these Notifications end up privileged over the core flow, and also email you by default.

Faces

There are faces of people next to each post, tapping into the subtle nuances of trust we all carry in our heads. The replies and notifications have smaller faces, which makes it harder to work out who they are, as this is where strangers show up more. The faces shown for the circle you're watching, or the list of people also in a limited post are very tiny indeed.

Phatic

The phatic feel of Twitter is partially there, but at the launch there was much talk of Google 'hiding the irrelevant' so the social gestures where we groom each other may be tidied away by an uncomprehending machine.

The replies from faceless strangers flooding your inbox if you respond to anyone with a large following will put people off interacting socially. The feeling of talking intimately to those you know is replaced by something closer to the 'naked in the school lunchroom' nightmare.

Following

Buzz does pick up Twitters asymmetric following model, and indeed adds a way to create private Buzzes for small groups, both key features. However, these are undermined by the confusing editing process. The Follower/Following editing is only in pop-up javascript dialogs on your Buzz in gmail and Google Profile pages, and because of the auto-follow onboarding, rather opaque. The groups editing is in Google Contacts, but that doesn't show the Followers, Following, Chat Friends, Latitude or other subgroups. There is also no way to see just conversations with those groups.

The overall effect makes it feel more like a Mornington Crescent server than Twitter. I made a Mornington Crescent Buzz account; it seems to fit.

Publics

Twitter's natural view is different for each of us, and is of those we have chosen. We each have our own public that we see and we address.

The subtlety is that the publics are semi-overlapping - not everyone we can see will hear us, as they don't necessarily follow us, and they may not dip into the stream in time to catch the evanescent ripples in the flow that our remark started. To see responses to us from those we don't follow, we have to click the Mentions tab. However, as our view is of those we choose to follow, our emotional response is set by that, and we behave more civilly in return.

Buzz reverses this. The general comments from friends are in the Buzz tab, but anyone can use '@' to mention you, forcing the whole conversational thread into your inbox. Similarly, if you comment on someone else's Buzz, any further updates to the web show up in your main email inbox. The tragedy of the comments ensues, where annoying people can take over the discussion, and their replies are privileged twice over those you choose to follow.

This is the YouTube comments problem yet magnified; when all hear the words of one, the conversation often decays.

Mutual media

By bringing in Twitter,blogs, Google Reader shared items, photos and other Activity Streams feeds, Buzz has the potential to be a way to connect the loosely coupled flows those of us who live in the listening Web to the email dwellers who may left behind. By each reading whom we choose to and passing on some of it to others, we are each others media, we are the synapses in the global brain of the web of thought and conversation. Although we each only touch a local part of it, ideas can travel a long way.

If the prioritisation of secondary commentary and poking over collated ideas can be reversed in Buzz, this could be made to work.

Small world networks

Social connections are a small-world network locally strongly-connected, but spreading globally in a small number of jumps. The email graph that Buzz taps into may be a worse model of real world social networks that articulated SNS's like Facebook, but it could be improved if the following and editing models are fixed.

Buzz's promise is that it builds on Activity Streams and other open standards, so it could help encourage others to do this better.

Posted by Kevin Marks at 08:35 No comments:

Saturday, 13 February 2010

Twitter Theory applied to Google Buzz

I wrote a post last year about Twitter theory, and presented on it too so I thought I'd compare how Google Buzz fits in with them or not.

Flow

Buzz is a flow but it does show an unread count, and it's in your email inbox so the implicit pressure to read is there. You're not cued to dip in and out. Also, all replies come to your main inbox, privileging them over the flow from those you chose to follow.

Faces

There are faces of people next to the root Buzzes, tapping into the subtle nuances of trust we all carry in our heads, but not by the replies, making those 'comments from strangers' even more alien.

Phatic

The phatic feel of Twitter is partially there, but at the launch there was much talk of Google 'hiding the irrelevant' so the social gestures where we groom each other may be tidied away by an uncomprehending machine.

The replies from faceless strangers flooding your inbox if you respond to anyone with a large following will put people off interacting socially. The feeling of talking intimately to those you know is replaced by something closer to the 'naked in the school lunchroom' nightmare.

Following

Buzz does pick up Twitters asymmetric following model, and indeed adds a way to create private Buzzes for small groups, both key features. However, these are undermined by the confusing editing process. The Follower/Following editing is only in pop-up javascript dialogs on your Buzz in gmail and Google Profile pages, and because of the auto-follow onboarding, rather opaque. The groups editing is in Google Contacts, but that doesn't show the Followers, Following, Chat Friends, Latitude or other subgroups. There is also no way to see just conversations with those groups.

The overall effect makes it feel more like a Mornington Crescent server than Twitter. I made a Mornington Crescent Buzz account; it seems to fit.

Publics

Twitter's natural view is different for each of us, and is of those we have chosen. We each have our own public that we see and we address.

The subtlety is that the publics are semi-overlapping - not everyone we can see will hear us, as they don't necessarily follow us, and they may not dip into the stream in time to catch the evanescent ripples in the flow that our remark started. To see responses to us from those we don't follow, we have to click the Mentions tab. However, as our view is of those we choose to follow, our emotional response is set by that, and we behave more civilly in return.

Buzz reverses this. The general comments from friends are in the Buzz tab, but anyone can use '@' to mention you, forcing the whole conversational thread into your inbox. Similarly, if you comment on someone else's Buzz, any further updates to the web show up in your main email inbox. The tragedy of the comments ensues, where annoying people can take over the discussion, and their replies are privileged twice over those you choose to follow.

This is the YouTube comments problem yet magnified; when all hear the words of one, the conversation often decays.

Mutual media

By bringing in Twitter,blogs, Google Reader shared items, photos and other Activity Streams feeds, Buzz has the potential to be a way to connect the loosely coupled flows those of us who live in the listening Web to the email dwellers who may left behind. By each reading whom we choose to and passing on some of it to others, we are each others media, we are the synapses in the global brain of the web of thought and conversation. Although we each only touch a local part of it, ideas can travel a long way.

If the prioritisation of secondary commentary and poking over collated ideas can be reversed in Buzz, this could be made to work.

Small world networks

Social connections are a small-world network locally strongly-connected, but spreading globally in a small number of jumps. The email graph that Buzz taps into may be a worse model of real world social networks that articulated SNS's like Facebook, but it could be improved if the following and editing models are fixed.

Buzz's promise is that it builds on Activity Streams and other open standards, so it could help encourage others to do this better.

Posted by Kevin Marks at 03:29 8 comments:
Labels: buzz, Faces, sxd, Twitter

Monday, 24 April 2017

Mastodon, Twitter and publics

Long ago, I wrote about the theory of social sites, with the then-young Twitter as the exemplar. As Mastodon, GnuSocial and other federated sites have caught some attention recently, I thought I'd revisit these theories.

Flow

A temporal flow with no unread count that you could dip into was freeing compared to the email-like experience of feed readers back then. Now this is commonplace and accepted. Twitter has backtracked from the pure flow by emphasising the unread count for @'s. GnuSocial replicates this, but Mastodon eschews it, and presents parallel flows to dip into.

Faces

Having a face next to each message is also commonplace - even LinkedIn has faces now. Some groups within the fediverse resist this and prefer stylised avatars. On twitter, logos are the faces of brands, and subverting the facial default is part of the appeal to older online forms that is latent in the fediverse.

Phatic

Twitter has lost a lot of its phatic feeling, but for now Mastodon and the others have that pleasant tone to a lot of posts that comes with sharing and reacting without looking over your shoulder. Partly this is the small group homophily, but as Lexi says:

For many people in the SJ community, Mastodon became more than a social network — it was an introduction to the tools of the trade of the open source world. People who were used to writing interminable hotheaded rants about the appropriation of “daddy” were suddenly opening GitHub issues and participating in the development cycle of a site used by thousands. It was surreal, and from a distance, slightly endearing.

Eugen has done a good job of tummling this community, listening to their concerns and tweaking Mastodon to reflect them. The way the Content Warning is used there is a good example of this - people are thinking about what others might find annoying (political rants, perhaps?) and tucking them away behind the little CW toggle.

The existential dread caused by Twitter’s reply all by default and culture of sealioning is not yet here.

Following

Part of the relative calm is due to a return of the following model - you choose whom to follow and it’s not expected to be mutual. However there are follow (and boost and like) notifications there if you want them, which contains the seeds of the twitter engagement spiral. This is mitigated to some extent by the nuances of the default publics that are constructed for you.

Publics

As with Twitter, and indeed the web in general, we all see a different subset of  the conversation. We each have our own public that we see and address. These publics are semi-overlapping - they are connected, but adjacent. This is not Habermas’s public sphere, but de Certeau's distinction of place and space. The place is the structure provided, the space the life given it by the paths we take through it and our interactions.

Since I first wrote Twitter Theory, Twitter itself has become much more like a single public sphere, through its chasing of ‘engagement’ above all else. The federated nature of Mastodon, GnuSocial,  the blogosphere and indeed the multiply-linked web is now seen as confusing by those used to Twitter's silo.

The structure of Mastodon and GnuSocial instances provides multiple visible publics by default, and Mastodon's columnar layout (on wider screens) emphasises this. You have your own public of those you follow, and the notifications sent back in response, as with Twitter. But you also have two more timeline choices - the Local and the Federated. These make the substructure manifest. Local is everyone else posting on your instance. The people who share a server with you are now a default peer group. The Federated public is even more confusing to those with a silo viewpoint. It shows all the posts that this instance has seen - GnuSocial calls it “the whole known network” - all those followed by you and others on your instance. This is not the whole fediverse, it’s still a window on part of it. 

In a classic silo, who you share a server shard with is an implementation detail, but choosing an instance does define a neighbourhood for you. Choosing to join witches.town or awoo.space or botsin.space will give you a different experience from mastodon.social

Mutual Media

By showing some of these subsets explicitly, the fediverse can help us understand the nature of mutual media a bit more. As I said:

What shows up in Twitter, in blogs and in the other ways we are connecting the loosely coupled web into flows is that by each reading whom we choose to and passing on some of it to others, we are each others media, we are the synapses in the global brain of the web of thought and conversation. Although we each only touch a local part of it, ideas can travel a long way. 

The engagement feedback loops of silos such as Twitter and Facebook have amplified this flow. The furore over Fake News is really about the seizures caused by overactivity in these synapses - confabulation and hallucination in the global brain of mutual media. With popularity always following a power law, runaway memetic outbreaks can become endemic, especially when the platform is doing what it can to accelerate them without any sense of their context or meaning.

Small World Networks

It may be that the more concrete boundaries that having multiple instances provide can dampen down the cascades caused by the small world network effect. It is an interesting model to coexist between the silos with global scope and the personal domains beloved by the indieweb. In indieweb we have been saying ‘build things that you want for yourself’, but building things that you want for your friends or organisation is a useful step between generations.

Standards

The other thing reinforced for me by this resurgence of OStatus-based conversation is my conviction that standards are documentation, not legislation. We have been working in the w3c Social Web Working Group to clarify and document newer, simpler protocols, but rough consensus and running code does define the worlds we see.

Originally published at kevinmarks.com
Posted by Kevin Marks at 06:36 No comments:

Friday, 14 August 2009

How Twitter works in theory

It is said that an economist is someone who sees something that works in practice and wonders whether it works in theory. Twitter clearly works in practice - and if you want practical advice, watch Laura Fitton's Tech talk at Google, or read her Twitter for Dummies. I've learned a lot from talking to her and others about this phenomenon, and I wanted to write about some theories that help me understand it.

Flow

At it heart Twitter is a flow - it doesn't present an unread count of messages, just a list of recent ones, so you don't have email's inbox problem - the implicit pressure to turn bold things plain and get that unread number down. Instead, you can dip in and out of it, when you have time, and what you see is notes from people you care about.

Faces

Indeed, what you see are the faces of people you know with the notes they wrote next to them. This taps into deep mental structures that we all have to look for faces and associate the information we receive with people we decide to trust, through what we feel about them. This is also why automated tweets not by them are so obtrusive, as they break the trust. Using friends' faces in ads is even more pernicious, as ads are by definition recommendations from people we don't trust.

Phatic

The key to Twitter is that it is phatic - full of social gestures that are like apes grooming each other. Both Google and Twitter have little boxes for you to type into, but on Google you're looking for information, and expecting a machine response, whereas on Twitter you're declaring an emotion and expecting a human response. This is what leads to unintentionally ironic newspaper columns bemoaning public banality, because they miss that while you don't care what random strangers feel about their lunch, you do if its your friend on holiday in Pompeii. This is something it shares with Facebook and other social networks, but this brings me to another key difference, which is asymmetric connections.

Following

Historically, web fora were open to anyone, leading to the tragedy of the comments, where annoying people showed up and spoiled things.

Social network sites changed this by requiring mutual agreement on friendship, thereby making a natural in-group area where you only saw your friends' comments. This also created a venue for the phatic behaviour, but it was rather self-limiting, as you ended up with piles of friend requests from vaguely unfamiliar people that it feels rude to ignore, creating another inbox problem.

This is analogous to the pre-web hypertext systems that insisted every link would be bidirectional, thereby preventing the power-law distributed link structure that builds a small-world network to connect the web and provides the basis for Pagerank. Being able to link to something without it having to give you permission by linking back is what enabled the web to grow.

Making following asymmetric is similarly freeing for social relationships - it means you can follow authors or film stars without drowning them in friend requests, and get the same phatic sense of connection with them that you get from friends.

Publics

The idea of Following means that the natural view we see on Twitter is different for each of us, and is of those we have chosen to hear from. In effect we each have our own view of the web, our own public that we see and we address.

The subtlety is that the publics are semi-overlapping - not everyone we can see will hear us, as they don't necessarily follow us, and they may not dip into the stream in time to catch the evanescent ripples in the flow that our remark started. However, as our view is fo those we choose to follow, our emotional response is set by that, and we behave more civilly in return.

For those with Habermas's assumption of a single common public sphere this makes no sense - surely everyone should see everything that anyone says as part of the discussion? In fact this has never made sense, and in the past elaborate systems have been set up to ensure that only a few can speak, and only one person can speak at a time, because a speech-like, real-time discourse has been the foundational assumption.

Too often this worldview has been built into the default assumptions of communications online; we see it now with privileged speakers decrying the use of anonymity in the same tones as 19th century politicians defended hustings in rotten boroughs instead of secret ballots. Thus the tactics of shouting down debate in town halls show up as the baiting and trollery that make YouTube comments a byword for idiocy; when all hear the words of one, the conversation often decays.

Mutual media

The alternative model is one that is less familiar, yet is all around us - the spontaneous order that emerges from people communicating in parallel. We know this from market pricing, from scientific consensuses, and from human language, and are starting to see it harnessed in projects like Wikipedia that present a dynamic cultural consensus. What shows up in Twitter, in blogs and in the other ways we are connecting the loosely coupled web into flows is that by each reading whom we choose to and passing on some of it to others, we are each others media, we are the synapses in the global brain of the web of thought and conversation. Although we each only touch a local part of it, ideas can travel a long way.

Small world networks

This seems counter-intuitive too—we're used to the idea of having an institution tell us what is news—but that is really a left-over anomaly from 20th Century mass media. In fact, social connections are a small-world network, that has the Six Degrees property that it is both locally connected, but can be traversed globally in a small number of jumps. Although online social networks are often not good models of real world ones, they share this feature, and Twitter amplifies it with both a low propogation delay and the enforced brevity that makes both writing and reading rapid.

As we are working to generalise the ideas seen in Twitter and similar sites through the Activity Streams work, I find it helps me to think about these underlying theories.

Posted by Kevin Marks at 17:00 111 comments:
Labels: Flow Past Web, theory, Twitter

Saturday, 21 November 2009

Publics, Flow, Phatic, Tummeling and Out-groups - New Words You Need to Know to Understand the Web


Kevin Marks
Originally uploaded by O'Reilly Conferences
Last week at Web2expo I gave a 10-minute keynote on the new vocabulary needed to understand where the web is going - most of this comes from sociology and anthropology. If you've been following my blog, you'll recognise this inculdes ideas from my Twitter in Theory post, from the Flow Past Web, from one on Digital Publics and of course from the Tummler post. Here's the video:


And here's the presentation, which uses Prezi's mindmap-as-presentation software:
Posted by Kevin Marks at 18:09 1 comment:
Labels: Faces, Flow, Out-groups, Phatic, publics, Tummeling, Web2Expo

Thursday, 1 June 2006

Building openness in - Pingerati and Microformat search

Now we've announced Pingerati and Microformat search, I get a chance to reflect on what has been keeping me busy for the last month, and behind the hiatus in my writing here. I have been building a parallel infrastructure to our Blog indexing, focused on Microformats instead.

Microformats are a way of expressing common kinds of things we refer to online in HTML, such as people, places events and reviews. They are built on layers of open standards, and meant to re-use and converge existing ideas, not make up new ones out of thin air.

When Dave and I were building up Technorati, we were able to do so because of the underlying openness of the web environment - the infrastructure of the net itself, and the open source servers, databases and parsers we connect together to make the data flow.

We also built on a culture of openness that owes a lot to Dave Winer - the openly accessible list of updated blogs gave a place to start in finding blogs to index, and by feeding back links to bloggers we encouraged cross-blog conversations.

When we added tags to blogs we used the rel-tag microformat in conjunction with existing category conventions, and made sure the links were not proprietary, but under authors' control. Again, helping people make connections through open standards.
By being open, we let everyone's world grow.

Although we are seeing more Microformats in blogs every day, we know that they make sense in other places too, and we need a way to encourage people to experiment with them, and find how they can add value to the world. Indexing them and reflecting them back to writers, but building an open data flow that others can tap in enables much more.

So, for the last couple of weeks, I've been working on Pingerati, which is a way to route Microformats around. If you have pages with data to share, you can ping it. If you want to find who has Microformats, it will ping you. The protocol is as simple as it could be, and it should enable the kind of positive sum gains I was talking about yesterday.


Technorati Tags: blogs, emergence, HTML, meme, microformat, microformats, search, tags, technorati, Web 2.0℠

Posted by Kevin Marks at 07:43 No comments:

Sunday, 27 September 2009

Tummling, SideWiki, Twitter and the Tragedy of the Comments revisited

Says Marshall Kirkpatrick in Twitter is More Likely to Be Meaningful Than TV

In one of those conversations, Kevin Marks (formerly of Technorati and Google, now at British Telecom) told me the following: he believes that Twitter is more likely to be interesting than television because we opt-in to particular streams of other peoples’ updates that we find interesting. That creates a positive feedback loop that encourages us to contribute something interesting in return and thus the ecosystem trends towards higher quality content. Do you agree with that?

Marks also said this was an advantage that Twitter and other opt-in subscription-stream formats have over things like YouTube comments. What of the “I don’t care what you ate for breakfast” critique of Twitter? Marks says that’s just people who have an antiquated view of what belongs “in public,” based on a time when content had to go through expensive publishing processes before being broadcast to the public and thus had to be unusually important to be worth it.

I had a great conversation about RealTime and attention with Marshall, but I think he has coalesced two separate thoughts of mine into one here, in an interesting way. I do find Twitter more interesting than TV, but I realise that may not be a common view.

The first point I was making was that 'realtime' is a mistaken emphasis - what is really interesting is the interplay between the formerly required-realtime technologies like radio/TV and telephony that are now able to be buffered, and the formerly delayed response media like writing, blogging, emailing that are now moving to lower-latency modes. I discussed this in The Flow Past Web

My second one was that the other thing that Twitter makes obvious is the value of semi-overlapping publics - that we all see a different web, and that the default assumption that everyone should read every comment on a forum is an idea that fails at scale too, as one troll or disruptive person can spoil everyone's reading - the Tragedy of the Comments.

Twitter's 'Following' model is powerful here for both its first-order and second-order effects.

The first order effect is that by default we see interesting and friendly comments from people we have chosen to follow, which makes us more likely to want to read on. That people favour and retweet and repeat what they find interesting helps us expand our circles of trust outward to new people.

The second-order effect is that as what we see is mostly interesting, funny, polite and so on, we respond in that vein too (assuming that is what we are reading; certainly there can be self-reinforcing intolerance too, but it is more contained).

Conversely, it is possible to have intelligent and thoughtful conversations in a public, read-everything space too, but for this to work there needs to be someone there setting the tone and establishing the norm - being a Tummler. This week Heather Gold, Deb Schultz and I piloted a show on Leo Laporte's podcast network called Tummel Talk about this important skill and phenomenon, with Jerry Michalski as our first guest. We'll be talking about the idea some more on Social Media Hour with Cathy Brooks on Tuesday 29th September

The skill of Tummling is important, and we need to hold it in mind as we build social tools on the web. Which brings me back to Google SideWiki.

At it's heart, SideWiki is yet another blogging tool, where the blogposts happen to be hosted on your Google profile page. However, as it is deployed inside Google Toolbar, you can see the posts attached to the pages that they are written about as you browse to them.

Google attempts to show the 'most important' comments first, using a combination of voting and other ranking algorithms, but it is still attempting to show everyone the same comment ordering, not taking personal 'following' into account. For SideWiki to succeed, I think this will need to change.

Sidewiki does another interesting thing - it matches comments to the same words elsewhere on the web. For example, my comment on Douglas Adams excellent 1999 piece also shows up in SideWiki on JP Rangiswami's blog where he quotes Douglas Adams too.

This hints at a greater possibility for SideWiki - to weave the web together by better by showing commentary across the web from all places that quote and cite each other, correlating by textual quotation and adding annotated links to the commentary from people we trust most.

This is a way Google could use it's scale of indexing to weave a better web for us to read, through our own chosen trusted sources, rather than funneling commentary into being hosted on its own pages.
(original Google Sidewiki comment)

Posted by Kevin Marks at 17:27 59 comments:

Saturday, 13 November 2010

Firesheep, enterprise software and other broken models

There has been a lot of fuss about FireSheep, a browser plugin that show how easy it is to intercept packets on the internet, and masquerade as someone else. The idea is nothing new: EtherPeg—which intercepts wifi traffic and shows the JPEGs and other images passing by—is over 10 years old. Annalee Newitz wrote a Wired story on people packet sniffing in coffee shops back in 2004.

The underlying design of the internet means that you don't know who will be able to see any packets you send. If you care about not being snooped on, you need an encrypted connection from your computer to the one serving you at the other end. The best way to do this on the web is to use HTTPS, which all browsers support, and most servers support with configuration changes. It's not perfect, but it's good enough.

However, much of the advice following on from FireSheep was misleading or outright wrong. I saw several articles saying:

  • Avoid Open WiFi
  • Turn on WPA encryption
  • Use a VPN to tunnel the traffic into a server elsewhere

These techniques may protect for a while against those nearby you in the Café, but by not securing the whole connection, they just change who is able to intercept your communications.

The security model here is the firewall one - the notion that there are trusted networks and untrusted networks, and as long as you're inside a trusted one, you'll be OK. This is an obsolete worldview. When computers were large fixed physical entities with software controlled by a specialist, and networks were wires under their control too, this had some correspondence with reality, but it was always tenuous - others within the firewall could be running compromised machines; outbound connections could still leak data.

If you VPN into a company or service to mask your outbound connections, that endpoint is an attractive point of attack, as it has collected a set of people who think their data needs securing. There's a clear example of this in this NYT article about a hacker who lured his friends to use an FBI VPN to track them down and arrest them.

This worldview connects with two other themes. The US Government is trying to pass a law requiring ISPs to enable your communications to be intercepted. The UK government is also working on legislation on retaining all email and web traffic. Similarly, many companies monitor internet traffic within and leaving their secure networks for legal compliance and employee monitoring. Such mandated backdoors, like the VPN tunnel, become attractive targets for other bad actors - remember the Greek government being spied on through a legally mandated interception backdoor in the phones they used?

This week, I spent a couple of days at the Enterprise 2.0 conference, hearing how open standards like Activity Streams and OpenSocial are being used to bridge separate business information systems both within and between companies, with OAuth used to enforce corporate policy.

This seems anathema to old-line IT managers who assume that they dictate who gets to see what, but the pragmatic realisation that many business people have more powerful and connected computing devices in their pockets as phones than on their desks from corporate IT was in evidence at E2.0 at least.

This brought to mind the great conversation we had with Josh Klein on TummelVision last week, discussing his book Hacking Work - breaking stupid rules for smart results:

one of the most common hacks we found: jumping IT’s firewall and working around their restrictions and tools in open computing environments, then bringing the work back over the firewall and presenting it to bosses as if the corporate tools had actually been used.

Ben Horowitz's article on enterprise sales in TechCrunch today tries to justify corporate practices, even as he recognizes the inversion of the innovation flow.

What this misses is the underlying economic justification for the existence of a corporation in the first place - the economic theories that build on Coase's work saying that firms exist because transaction costs are lower within them than external transactions mediated by the marketplaces. Pettifogging internal purchasing rules should be subject to this test: does the internal transaction cost of approving and purchasing something exceed the value of the thing being purchased?

Reading Ben's explanation of how corporate salespeople help institutions negotiate their own labyrinthine processes, I couldn't help but be reminded of John Hagel's Big Shift model, (also discussed on TummelVision), which continues to show a declining return on assets for corporations.

The challenge we have on the web is to maintain the kinds of open-to-all interoperable standards that empower us to work round these creaking bureaucracies. If we delegate our online identities to a few firms operating proprietary APIs, that they can revoke access to, or decide who can call them for reasons of corporate strategy, the lowered transaction costs suddenly get very high again.

Doc Searls's work on VRM (this week's TummelVision) is all about making sure that we can retain agency over our own information. I expect to discuss this in depth at Defrag next week.

Posted by Kevin Marks at 15:21 1 comment:
Labels: Activity Streams, enterprise, firewall, OpenSocial, Tummeling, TummelVision, VRM

Monday, 22 January 2007

iPhone's great step back from iChat

I did watch the iPhone Macworld Keynote last week - here's my chapter-list version of the stream so you can skip through it to the bits you find interesting:


(I'd do the same for the download except 1. Apple obfuscated the url enough that I can't be arsed to packet sniff it out and 2. they still don't have HTTP 1.1 seeking support working right, despite me building and demoing it about 5 years ago).

After watching it, my biggest surprise was how much of a step back it was from the rich interaction that iChat supports. With iChat you get presence info, chat, sending documents and integrated audio-video chat (when the other user's computer and connection supports it). Instead, iPhone had a legacy telco worldview baked in, with calls not conveying any further context (watch the combined demo near the end, where Jobs has to retype Schiller's email when talking to him on the phone). The iPhone has the camera on the wrong side to be a videophone, and Jobs did not mention any ability to make calls over Wifi rather than the Cingular network, or anything about IM (as opposed to SMS).

My hope is that this is just Jobs not mentioning the features that don't demo well yet, but my sidekick's AIM integration is the reason I am so hooked on it; it buffers chats server-side so thatintermittent phone connections on the train don't interrupt conversation flow.
Posted by Kevin Marks at 01:42 2 comments:
Labels: AIM, iChat, iPhone, Keynote, Macworld, video, VOIP

Thursday, 11 August 2011

David Cameron should heed Douglas Adams and ORG

Widely reported today are David Cameron's comments to parliament on riots and social media:

Mr Speaker, everyone watching these horrific actions will be stuck by how they were organised via social media.

Free flow of information can be used for good. But it can also be used for ill.

[And when people are using social media for violence we need to stop them.]

So we are working with the Police, the intelligence services and industry to look at whether it would be right to stop people communicating via these websites and services when we know they are plotting violence, disorder and criminality.

I have also asked the police if they need any other new powers.
(the bit in square brackets was in his press statement, but not read in the Commons)

This particular line of reasoning was magnificently rebutted by Douglas Adams in 1999:
Newsreaders still feel it is worth a special and rather worrying mention if, for instance, a crime was planned by people 'over the Internet.' They don't bother to mention when criminals use the telephone or the M4, or discuss their dastardly plans 'over a cup of tea,' though each of these was new and controversial in their day.

I was encouraged recently when the UK Govt abandoned web blocking plans in the Digital Economy Act. Understanding that the internet is there for common carriage (a mere conduit, as the EU puts it) is important. Even on its own terms this threat makes little sense: if people are plotting riots on social media, that is surely exactly the evidence you need to convict them under the UK's statutory Conspiracy law. The telephone, the M4 and cups of tea are much harder to use as sources of evidence.

The Open Rights Group, has a typically measured and thoughtful response to this.

Cameron should be careful, or he'll look to posterity like William Cobbett ranting about the pernicious evils of tea.

Posted by Kevin Marks at 11:22 2 comments:
Labels: conspiracy, DEBill, internet, UK

Wednesday, 16 April 2008

Comcast's Bialystock and Bloom Business Model?

Tomorrow, the FCC is holding a public hearing at Stanford on Broadband network management practices. With striking timing, Comcast today managed to announce a 'Internet Bill of Rights' without inviting any users, and simultaneously cut off Dave Winer's net connection for exceeding their secret usage limits. I can't link to Comcast's policy because their website mungs the text in via javascript - here's what they say:
Excessive use means data usage that is not characteristic of a typical residential user of the service as determined by Comcast.[...]Comcast currently identifies well less than 1% of Comcast High-Speed Internet customers as excessive users each month. [...]Many excessive users consume more data than a business-class T1 line running at full capacity in a month. [T1 is 1.5 Mbit/sec - Comcast claims to offer 12 Mbit/sec for PowerBoost, and 6/8 Mbit/sec standard] [...] Currently, each month Comcast identifies the top bandwidth users of its High-Speed Internet service by determining aggregate data usage across its entire customer base nationwide.

What they are saying is that they use a crude averaging model, and penalize you if you don't fit, for example by using the connection capacity they promise more than 10% of the time. Now, this could be called Procrustean, but it reminds me of The Producers, where Bialystock and Bloom sold a hundred people 10% shares of the show, assuming it would fail. Sadly for Comcast, people like Dave are finding new uses for the net's bandwidth, and not just checking email sporadically any more.

Conventional internet service user models are based on users downloading more then they upload, from common big media sites that can be easily cached. However, as Odlyzko pointed out, citing Lesk's now decade-old work, the dominant form of data creation is photographs. Now all these photographs are actually digital, and we want to share them so others can see them. Because we aren't allowed to run our own servers by the likes of Comcast, we have to upload them to Flickr or Photobucket or Picasa to share them. This gives us an 'upload more than you download' network flow, as we send them up at full multi-megapixel resolution, but browse a few of each others' at thumbnail or reduced size. And that's before we even consider video uploading (which I've noticed Comcast throttles at 0.4 Mbit/sec for me).

Comcast hit the news before by sabotaging Bittorrent transfers by faking reset packets, but what Bittorrent is really doing is arbitraging around the asymmetric network bandwidth delivered by these outdated user models.

Bob Briscoe recently wrote an interesting proposal on handling congestion by TCP signalling to reveal the costs of congestion. This was spun by George Ou as an attack on P2P protocols, but the underlying principle of penalising those who cause congestion is an interesting one. The question I'd like answered is that if I have a gigabit network at home, and the internet backbone is multi-terabit, when Comcast throttles my uploads to 400 kilobits, aren't they the ones causing the congestion?

Posted by Kevin Marks at 23:02 1 comment:
Labels: Bittorrent, bndwidth, Comcast, FCC, internet, net neutrality

Monday, 23 January 2012

Google Plus admits they want fake names

Today, after 7 months, Bradley Horowitz announced that Google Plus will accept some pseudonyms. Kinda. If you can prove you're already famous. And can convince their robot it looks like a name. However, Google Engineer Yonatan Zunger spills the beans in a comment on that thread:

First of all, you might ask why we have a names policy at all. (i.e., why we don’t simply go with the JWZ proposal) One thing which we have discovered, while putting some miles on the system, is that it is indeed important to have a name-based service rather than a handle-based service. This isn’t a matter of functionality so much as of community: You get a different kind of community when people are known as Mary Smith than when they are known as captaincrunch42, and for a social product in particular we decided that the first kind of community is the one we want to build. In order to do that, we want to establish a general norm that the names you put in to the system should be names, not handles.

So one thing that our name checking flow tries to catch is handles, which should normally be nicknames, shown in addition to a name. The other important thing it’s trying to catch is people who are creating individual accounts, rather than +Pages, for non-human entities such as businesses or organizations. The behavior of +Pages is deliberately restricted in the system, and we don’t want people to be creating fake human accounts to circumvent that. The name check turns out to be a very powerful tool to catch these.

Our name check is therefore looking, not for things that don’t look like “your” name, but for things which don’t look like names, period. In fact, we do not give a damn whether the name posted is “your” name or not: we will not challenge you on this basis, nor is there any mechanism for other users to cause you to be challenged for this.

There are two main cases where the name check screws up. One is false positives: people (such as you) who have unusual names which get flagged because they looked like handles. Being able to appeal via things such as drivers’ licenses is useful for this case, since it’s a simple “oh, we got this wrong.” The other case is people such as +trench coat, who are so well-known under this handle that it would be bizarre not to let them onto the system under this name. For this case, we allow appeals based on being well-known under the name: thus the ability to prove the “established pseudonym.” We’ve deliberately set the threshold for that latter case fairly high for now, but we intend to continue to tune it; the objective is that the frequency of such names should basically be the same as their frequency in meatspace.

So to answer your questions one-by-one:

(2) “Meaningful following” only applies to cases of established pseudonyms which do not look like names. The definition of “meaningful” is deliberately vague so that we can tune it, so that it behaves in a natural fashion.

(3) That’s correct; drivers’ licenses are for false positives, not pseudonyms.

(4) Unusual names will indeed hit friction, because of false positives. We’re trying to minimize that, but it’s going to take some trial and error.

(5) Google+ can absolutely be your first identity online. No matter what your language, no matter where you come from. The “established pseudonym” logic should apply to a very small subset of people. If some groups are seeing a higher false positive rate than others, that’s a bug, not a feature, and we have the data available to spot this situation and remedy it.
(posted in full, in case of subsequent retraction, and because G+ doesn't have permalinks for comments)

Yonatan admits what Bradley obscures:that this is an Identity Theatre issue. They don't want your name, They don't care if you have a forename in one language and a surname in another. Let me quote this exactly:

Our name check is therefore looking, not for things that don’t look like “your” name, but for things which don’t look like names, period. In fact, we do not give a damn whether the name posted is “your” name or not: we will not challenge you on this basis, nor is there any mechanism for other users to cause you to be challenged for this.

This is what I suspected when I wrote Google Plus must stop this Identity Theatre

Google+ is letting an algorithm decide what is a name and what isn't. You will be forced into it's Procrustean idea of what names are, or be harassed for it. You have to pass as normal, like call centre workers forced to learn to sound American.

You can create disposable accounts with fake names, as long as they look plausible to Yonatan's bot.


This algorithm has allowed people called 'panel heater' 'The Phoenix Rising' 'tous les mais du monde' and Mehr Decent , a bot with a well-known actress's photo posting links to a single website to follow me (and that's just in the most recent 30 I checked).

So Google continues to encourage fakers and discourage those who need a pseudonym for good reasons.
Posted by Kevin Marks at 14:29 21 comments:
Labels: google, Identity, pseudonyms

Wednesday, 7 June 2006

The BPI gets tangled in DRM

Just after the All-party Internet Group moved towards a sensible position on DRM, the British Phonographic Industry gave confused testimony to the Select Committee for Culture, Media & Sport inquiry into New Media and the Creative Industries.

Obviously, the Record Labels' official lobbying group is going to be self serving, but they do seem very confused by DRM, judging by their headlines:

  • BPI reassures consumers: “We will not sue you for filling your iPod with music you have bought yourself"
  • Failure to extend copyright term "could turn an export into an import” - akin to scattering Britain's crown jewels of music across the globe.
  • BPI to sue illegal website AllofMP3.com
  • Digital downloads can cost more to distribute than CDs
  • BPI hopes to reach voluntary settlement on download royalties
  • Apple should make iTunes compatible with other players
  • Music “more popular than ever”

Let's group these together and deduce some consistent legislative proposals

BPI reassures consumers: “We will not sue you for filling your iPod with music you have bought yourself"

BPI Chairman Peter Jamieson: “We believe that we now need to make a clear and public distinction between copying for your own use and copying for dissemination to third parties and make it unequivocally clear to the consumer that if they copy their CDs for their own private use in order to move the music from format to format we will not pursue them.”

Excellent, so lets have a law explicitly permitting non-commercial copying, and lets also make DRM technology that interferes with it illegal.

Apple should make iTunes compatible with other players

Jamieson called on Apple to open up its software in order that it is compatible with other players. “We would advocate that Apple opts for interoperability,” he said.

Well, iTunes is actually pretty good at turning locked purchased files into uncompressed Audio CDs. That said, requiring them to distribute DRM-free files would solve this problem too. So nice to find a policy that satisfies all your points.

The next three are a bit of a conundrum, however

BPI to sue illegal website AllofMP3.com

AllofMP3.com’s claims to be legal are false, she said. Neither artists nor record companies receive any payment from the site.

BPI hopes to reach voluntary settlement on download royalties

BPI Chairman Peter Jamieson revealed that the BPI, together with music download stores and mobile companies are still trying to reach an amicable settlement in their dispute with music publishers and songwriters over the royalties which must be paid on downloads.

So, the BPI and AllOfMp3.com are both selling downloads that they don't have clear rights to? Tricky stuff. And yet:

Digital downloads can cost more to distribute than CDs


When questioned on the relative prices of CDs and downloads, Richardson revealed that for an independent company like his, the costs charged by digital distributors are actually higher than those for physical product.

Speaking later, he said, “It is early days for digital music. At this point in time the cost of distribution for downloads is actually higher than for CDs. Regardless of that, however, distribution remains a relatively small part of the investment record companies make in music. All of the key costs for a piece of music remain virtually the same whatever format you distribute it on.”

This gets more confusing. Apple takes a small enough proportion of the price per song for the iTunes store that it has been accused of loss-leading them to sell iPods, and AllofMP3.com is just charging for bandwidth, so how are you running up these costs?

Clearly we need to find a way to separate paying for music from distributing it, as combining them, and trying to wrap them up in DRM is what is causing you such problems.

Failure to extend copyright term "could turn an export into an import” - akin to scattering Britain's crown jewels of music across the globe.

“British music is one of Britain's greatest ambassadors, but failure to extend term could turn an export into an import,” he said. “If we lose the Crown Jewels of British music, little money will flow back to the UK.”

Ok, you've really lost me there. If the UK term is lower than foreign ones, as at present, then that is a great way to favour domestic production over imports - you can sell old foreign recordings in the UK with impunity, and you have 45 years more protection in the US so you can export your back catalogue there. Seems like a win-win for the UK public and economy, and suggests there would be a big benefit from shortening copyright terms in the UK further.


Music “more popular than ever”

Asked to summarise the position of UK record companies, Jamieson said, “Music has never been more popular. But it’s not time to break out the champagne just yet. Digital was always a threat and an opportunity, and I believe we are getting beyond the threat stage.

Richardson dismissed the idea that the internet somehow renders record companies redundant. Many of the oft-quoted examples of internet-built bands are simply an adaptation of long-established business methods. “Far from doing without record companies, they have used the internet to get themselves better deals with record companies,” he said.

So, music is more free, more available, more popular, and less subject to manipulation and domination by the labels. I think it is time to break out the champagne.


Technorati Tags: art , audio, BPIP, Digital Commonwealth, digital rights, DRM, economics, law, meme, music, Open Rights Group, ORG, politics, rhetoric

Posted by Kevin Marks at 23:27 No comments:

Monday, 10 April 2006

ABC's TV on demand sounds unattractive

Jeff Jarvis points to ABC's mooted online free shows:

On April 30, ABC will unveil a revamped Web site that will include a “theater” where people with broadband connections can watch free episodes of “Desperate Housewives,” “Lost” and other hit shows on their computers. Episodes will be available the morning after they air and will be archived so people can eventually view a whole season.

Episodes of the ABC shows — which can be paused, rewound and fast-forwarded — will contain commercial breaks that viewers can’t skip, making Disney hopeful it has figured out a way to turn the delivery of programs over the Web into a profit-generating business. Ten advertisers, including Ford Motor Co., Procter & Gamble, Universal Pictures and Unilever, already have signed up.


Well, it's nice to add another option, but this one is only attractive compared to classic over-the-air or 'live' cable broadcast. Let's do a comparison table:
<
<
DeliveryCostTime constraintspace constraintpros and cons
BroadcastFreemust watch live or VCROn your TVs in the USCommercials interrupt - mute and wait
CableMonthly feemust watch live or VCROn your TVs in the USCommercials interrupt it - mute and wait
TiVoMonthly fee for cable and for TiVo directoryCan watch when you like, though will delete itself unless you check itOn the TV with the TiVo, in the USCan fast-forward commercials; must subscribe or record in advance
New ABC LiveMonthly fee for broadbandCan watch when you like from 1 day after TVOn your computer with a net connection - US Only?can't skip commercials
ABC on iTunesMonthly fee for broadband; $1.99 per show with discounts for seasonsCan watch when you like from 1 day after TV, if you have a US credit cardOn your computer with a net connection, don't need net connection after download; can transfer to iPodno commercials; quality is not great
Bittorrent bootlegMonthly fee for broadbandCan watch when you like from a few hours after TV, anywhere in the worldOn your computer, don't need net connection after download; can transfer to iPod and other players; can make DVD with effortCommercials edited out. Is of dubious legality.
DVDPay per series - prices varyCan watch when you like from a few months after TV, region coded to annoy you on your DVD player; On your computer, can transfer to other players with effort and semi-legal toolsCommercials edited out. Maybe extra features

Overall, the options are awkward. I can see some interesting gaps there - if I could subscribe to DVDs by mail every fortnight or month, while the series is still airing, that would be attractive (much more attractive than US networks' scheduling, which seems designed to confuse and disappoint and lose the flow of plot).
The iTunes series subscription could be attractive, if it was closer to the quality you get from HD-ripped Bittorrent or DVD. Tom Coates was saying something similar recently.

The other missing piece follows on from my post about net video last week- what if the cable companies had a cache of shows for a while after airing, or let you retrieve them from each others' PVRs? As the smarter ones have very high speed networks in their served neigbourhoods, this could be very responsive.

Update: Well, that was fast - Time Warner Cable are talking about just this kind of thing, though
the closing line "TV is more powerful than the Internet at the end of the day" is a bit of a shame.

Technorati Tags: ABC, bittorrent, Live TV is Dead, meme, movie, podcasting, QuickTime, streaming, television, video

Posted by Kevin Marks at 23:38 No comments:

Monday, 27 February 2006

Tiered versus Weird

I have made this contrast before, and I think it is another key framing distinction in the net debate.
Internet cloudNetwork engineers draw the Internet as a cloud, because it doesn't matter to endpoints how the packets get there. The packets get routed, but the protocols are designed to cope with messiness, with buffers overflowing, and computers crashing, and wires being unplugged or ripped up by backhoes. This is the mental model the end-to-end principle encourages - the net is just where packets come from and go to, and has a big 'Somebody Else's Problem' field around it. This is one place where engineers and normal people converge - they don't think about how stuff gets there, they just enter a website or email or IM address and there they are.
Internet thought balloonBy contrast, telco's and networking providers, naturally, do see the wires and the complexity, because that's what they do. They can't use the SEP method, so they fall back on thinking hierarchically, which is another way of coping with complexity. This contributes to the difficulty of getting the open network argument across to governments - the hierarchic frame is a good fit for their default approach to organisation and information flow, so regulatory capture is a likely outcome.
There are countervailing ideas in political thought across the political spectrum, from commons theory to anti-trust and deregulation. The immense success of WiFi's tiny slice of free spectrum is promising, but as Doc, Eric and Mitch and Jon point out, the attack on net neutrality is building. We need to keep trying out metaphors of openness and freedom, invisible hands and co-operation, until we find one that fits.

Technorati Tags: caliban, Digital Commonwealth, digital rights, ethics, meme, Open Rights Group, ORG, politics, rhetoric

Posted by Kevin Marks at 19:30 1 comment:

Thursday, 23 February 2006

Simple rule - if you write, get a blog

Today's flash of the bleedin' obvious was that blogs by writers tend to work well. On the face of it, this is a banal observation, but finding the blog by the Grey's Anatomy writers, and Malcolm Gladwell's new blog, reminded me that anyone who writes professionally, who writes because they love it, and can't help but write, should get themselves a blog, so we can all share in the flow of ideas.

After all, just on my favorite's list I have Gaiman, Sessum, Scalzi, Charman, the Nielsen Haydens, Searls, Weinberger and Locke.

It may seem that you lot have a bit of an unfair advantage, but us amateurs do appreciate your good writing and try to learn from you.

Technorati Tags: auctorial, blink, blogs, writing

Posted by Kevin Marks at 23:56 No comments:

Thursday, 10 November 2005

Not consumers or users, but amateurs

Mary takes Intelliseek to task for calling the writers of the web 'consumers', but her suggestion of 'users' is equally infelicitous - even Scoble winces every time he says 'user generated content'.

We already have a word for people who create for the love of it, rather than being paid to, and it is 'amateurs'. As with many other pleasures, when we seek out opinions, we prefer those that flow from passion rather than from payment.

Now it may be argued that, given the decline in the teaching of Latin and French, the loving root of 'amateur' is no longer perceived, so those who write pour l'amour ou pour le sport may see 'amateur' as a slight. In which case lets retranslate it to english and call it 'lovingly created media'.


Technorati Tags: blogs, meme, rhetoric

Posted by Kevin Marks at 11:47 2 comments:

Friday, 12 August 2005

Adam Smith and microformats principles

Lynne Kiesling quotes Adam Smith
The man of system, on the contrary, is apt to be very wise in his own conceit; and is often so enamoured with the supposed beauty of his own ideal plan of government, that he cannot suffer the smallest deviation from any part of it. He goes on to establish it completely and in all its parts, without any regard either to the great interests, or to the strong prejudices which may oppose it. He seems to imagine that he can arrange the different members of a great society with as much ease as the hand arranges the different pieces upon a chess-board. He does not consider that the pieces upon the chess-board have no other principle of motion besides that which the hand impresses upon them; but that, in the great chess-board of human society, every single piece has a principle of motion of its own, altogether different from that which the legislature might chuse to impress upon it. If those two principles coincide and act in the same direction, the game of human society will go on easily and harmoniously, and is very likely to be happy and successful. If they are opposite or different, the game will go on miserably, and the society must be at all times in the highest degree of disorder.
microformats.org says:

microformats are not:

  • a new language
  • infinitely extensible and open-ended
  • an attempt to get everyone to change their behavior and rewrite their tools
  • a whole new approach that throws away what already works today
  • a panacea for all taxonomies, ontologies, and other such abstractions
  • defining the whole world, or even just boiling the ocean
  • any of the above

Smith contrasts:
The man whose public spirit is prompted altogether by humanity and benevolence, will respect the established powers and privileges even of individuals [...]
He will accommodate, as well as he can, his public arrangements to the confirmed habits and prejudices of the people; and will remedy as well as he can, the inconveniencies which may flow from the want of those regulations which the people are averse to submit to. When he cannot establish the right, he will not disdain to ameliorate the wrong; but like Solon, when he cannot establish the best system of laws, he will endeavour to establish the best that the people can bear.
microformats.org continues:

the microformats principles

  • solve a specific problem
  • start as simple as possible
  • design for humans first, machines second
  • reuse building blocks from widely adopted standards
  • modularity / embeddability
  • enable and encourage decentralized development, content, services

I grant you, the microformats prose is terse in comparison, but I see the commonality between the two. Do read Lynne's post in full, and thank you Megan for pointing it out.
Posted by Kevin Marks at 23:03 No comments:

Tuesday, 29 April 2003

Social Software again

I've posted belated Hydra notes from the Social Software Alliance Birds of a Feather and the Journalism Birds of a Feather from Emerging Tech last week. Taking notes using Hydra was an intersting experience, with 3 or 4 other people taking them too, correcting my spelling and so on.

The SSA meeting was fairly chaotic - perhaps reflecting the diverse meanings of 'Social'. Clay Shirky did not show up (or if he did, did not speak up); Dave Winer later poured scorn on the efforts, implying it was all about social climbing.

Friedrich Hayek famously said that the word 'social' empties the noun it is applied to of their meaning. Hayek goes on:

…it has in fact become the most harmful instance of what, after Shakespeare's 'I can suck melancholy out of a song, as a weasel sucks eggs' ( As You Like It , II, 5), some Americans call a 'weasel word'. As a weasel is alleged to be able to empty an egg without leaving a visible sign, so can these words deprive of content any term to which they are prefixed while seemingly leaving them untouched. A weasel word is used to draw the teeth from a concept one is obliged to employ, but from which one wishes to eliminate all implications that challenge one's ideological premises.

At one point in the meeting, writers of social software were likened to scientists at Los Alamos building the bomb, which is certainly hyperbolic, not to say bollocks.

The subsequent Journalism BoF was less hectic, and more measured. One of the most interesting things for me was the various Blogger/Journalist hybrids like Dan, Glenn, Scott and Doc talking about the difference of voice between a blog and a newspaper, where you would have an editor pushing you into the house style. This reminded me of both Boris Johnson's NYT experience and the lamented Tish Williams, who left 'Upside' for 'TheStreet.com' in early 2000, and went from a sparkling original voice to yet another tech journalist. (I wanted to link to some of her stellar pieces at upside, but they are all gone - not even google or the wayback machine can find them)

I think this conflict, rather than layout issues is behind the blog/wiki divide that Joi mentions.

Blogs amplify individual voices. Unlike mailing lists, they don't get lost in the hubbub. Wikis are different - they blur authorship, and drive towards a consensual style. Blogs' temporal flow creates an affordance for conversation that is diluted and washed away in Wikis.

Posted by Kevin Marks at 03:22 1 comment:
Next Posts Home
Subscribe to: Posts (Atom)

This is my personal blog. Any views you read here are mine, and not my employers'.

Atom Feed

Support the Open Rights Group
My photoKevin Marks Me on Twitter
Me on G+

People's thoughts I read:

Daily

Rosie
San Jose Young People's Theatre
Dave Weinberger
Doc Searls
Gonzo Engaged
AKMA
Cory & friends
Denise Howell
Charles Wiltgen
Shelley Powers
James Lileks
Suw Charman
Halley Suitt

Weekly

Andrew Marks
Blogsisters
Arts & Letters Daily
Bricklin, Frankston & Reed
Steve Yost
Jeneane Sessum
Brian Micklethwait et al
Tom Matrullo
Gary Turner

Sporadically

Small Pieces
Stuart Cheshire
RageBoy
Nonzero
Neil Gaiman
Thomas Vincent
Brad deLong
Andrew Odlyzko
ProSUA

No to Mickey Mouse Computers

powered by blogger

Blog Archive

  • ▼  2023 (1)
    • ▼  September (1)
      • Plus Theory
  • ►  2017 (2)
    • ►  May (1)
    • ►  April (1)
  • ►  2015 (7)
    • ►  November (2)
    • ►  May (3)
    • ►  April (1)
    • ►  January (1)
  • ►  2014 (3)
    • ►  October (1)
    • ►  April (2)
  • ►  2013 (5)
    • ►  June (1)
    • ►  May (1)
    • ►  April (2)
    • ►  March (1)
  • ►  2012 (8)
    • ►  December (1)
    • ►  May (1)
    • ►  April (1)
    • ►  March (1)
    • ►  January (4)
  • ►  2011 (11)
    • ►  December (1)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  April (2)
    • ►  January (2)
  • ►  2010 (16)
    • ►  November (1)
    • ►  October (1)
    • ►  September (3)
    • ►  June (1)
    • ►  May (2)
    • ►  April (2)
    • ►  March (2)
    • ►  February (2)
    • ►  January (2)
  • ►  2009 (22)
    • ►  November (2)
    • ►  October (2)
    • ►  September (2)
    • ►  August (3)
    • ►  July (2)
    • ►  June (2)
    • ►  May (2)
    • ►  April (1)
    • ►  February (2)
    • ►  January (4)
  • ►  2008 (29)
    • ►  December (2)
    • ►  November (3)
    • ►  August (1)
    • ►  July (3)
    • ►  June (3)
    • ►  May (5)
    • ►  April (2)
    • ►  February (3)
    • ►  January (7)
  • ►  2007 (45)
    • ►  November (3)
    • ►  October (4)
    • ►  September (4)
    • ►  August (10)
    • ►  July (3)
    • ►  June (8)
    • ►  April (2)
    • ►  March (6)
    • ►  February (3)
    • ►  January (2)
  • ►  2006 (119)
    • ►  December (13)
    • ►  November (8)
    • ►  October (16)
    • ►  September (10)
    • ►  August (3)
    • ►  July (6)
    • ►  June (24)
    • ►  May (3)
    • ►  April (10)
    • ►  March (7)
    • ►  February (8)
    • ►  January (11)
  • ►  2005 (101)
    • ►  December (10)
    • ►  November (13)
    • ►  October (9)
    • ►  September (8)
    • ►  August (7)
    • ►  July (7)
    • ►  June (8)
    • ►  May (12)
    • ►  April (7)
    • ►  March (6)
    • ►  February (1)
    • ►  January (13)
  • ►  2004 (53)
    • ►  December (8)
    • ►  November (5)
    • ►  October (6)
    • ►  September (7)
    • ►  July (5)
    • ►  June (3)
    • ►  May (2)
    • ►  March (3)
    • ►  February (7)
    • ►  January (7)
  • ►  2003 (196)
    • ►  December (12)
    • ►  November (14)
    • ►  October (21)
    • ►  September (23)
    • ►  August (19)
    • ►  July (11)
    • ►  June (14)
    • ►  May (9)
    • ►  April (22)
    • ►  March (20)
    • ►  February (16)
    • ►  January (15)
  • ►  2002 (224)
    • ►  December (15)
    • ►  November (21)
    • ►  October (22)
    • ►  September (12)
    • ►  August (11)
    • ►  July (28)
    • ►  June (19)
    • ►  May (29)
    • ►  April (18)
    • ►  March (19)
    • ►  February (16)
    • ►  January (14)
  • ►  2001 (13)
    • ►  December (2)
    • ►  November (11)

Contributors

  • Kevin Marks
  • Kevin marks