The Social Graph Is Neither

The Social Graph Is Neither is a brilliant article on why the current idea of “social networking” is utterly flawed. Some highlights:

But even if we go ahead and build the Semantic Web, 2004 edition, and populate it with information about all our connections to other people, it still won’t be expressive enough.

There’s another fundamental problem in that a graph is a static thing, with no concept of time. Real life relationships are a shared history, but in the social graph they’re just a single connection.

Social networks exist to sell you crap. [...] Because their collection methods are kind of primitive, these sites have to coax you into doing as much of your social interaction as possible while logged in, so they can see it.

Open data advocates tell us the answer is to reclaim this obsessive dossier for ourselves, so we can decide where to store it. But this misses the point of how stifling it is to have such a permanent record in the first place.

The Future of Multisite

The original use case of the Multisite feature in WordPress (formerly WPMU) was wordpress.com, where users can create and manage their own blogs, independent from all the other blogs in the network. Outside of wordpress.com, this is the more common story: someone sets up a multisite installation and needs to create and manage several sites, [...]

Read full post...

When we travel, we travel not to see new places with new eyes; but that when we come home we see home with new eyes.

G. K. Chesterton

Theme Wrappers

You know what really grinds my gears? Code duplication. And you know where you can find plenty of that? In WordPress themes! This has gotten a little better recently, thanks to get_template_part(), but it’s still not a complete solution.

Read full post...

Smarter Navigation: Version 1.3

In previous versions, the plugin stored individual post ids in a cookie. To avoid having a huge cookie, I limited it to 500 ids. Needless to say, this was not a very scalable solution.
In the current version, it remembers the query vars instead, which are later used to get the adjacent posts.

Read full post...