Web Platform Docs launches

Published Wednesday, 17 October 2012 7:40AM CDT by filed under Internet

0
Web Platform Docs launches

The usual suspect big players in the web industry: Adobe, Apple, Facebook, Google, Microsoft, Mozilla, and others under the auspices of the World Wide Web Consortium (W3C) have launched the Web Platform website in an attempt to unravel the increasing complexity of web development. The early-release “alpha” website inclues a wiki, discussion forums, a blog, the #webplatform IRC channel, and a separate tutorials wiki with more to come.

The goal of the site is to consolidate the best web development documentation, tips, and best practices available and then keep all of it up to date. If successful, such an undertaking would be most welcome as it’s nearly impossible to stay current on emerging specifications that change on an all too frequent basis.

One of the more interesting aspects of the site is the possibility—however dim—that emerging standards will be discussed openly. While most of the content will be provided by the W3C member companies mentioned above, anyone can contribute to the wikis on an equal basis.

Take me to the river.js

Published Monday, 10 September 2012 7:40AM CDT by filed under Internet

0
Take me to the river.js

Last week, Dave Winer formalized his river.js format, for JavaScript Object Notation (JSON)-based interoperability. The format has been in use—mostly by Winer—since 2009 and is used in his “river of news” aggregation model. Winer describes river.js as “a JSON-based format that serves to communicate between aggregators and browser-based apps that display the rivers.”

The river.js format is best thought of as a syndication format for a collection of multiple content feeds. Where RSS was a syndication format for a single content source, river.js is a syndication format for aggregated collections of content sources.

Winer has also published River2, a “river of news” feed reader that uses the river.js format.

The river.js format is a cornerstone in Winer’s larger vision of an open Twitter-like ecosystem. An open, web-based ecosystem is, in Winer’s view, a better alternative to advertising supported or subscription-based models. Over the weekend, Winer issued a challenge to the TechCrunch Hackathon participants, inviting them to explore the ecosystem ideas he’s proposed.

Branch: More siloed content with no interoperability

Published Thursday, 30 August 2012 7:46AM CDT by filed under Internet

0
Branch: More siloed content with no interoperability

When I received my notice that I had been accepted into Branch, the email suggested I use the service to get my ideas out of my drafts folder and receive feedback from trusted peers. That sounded reasonable until I figured out that in order to participate in a Branch conversation, you have to be “accepted” by someone already participating in that particular conversation, and to get that precious feedback you have to send invitations to participants. I’ve found that some of the best feedback comes from folks I don’t know, or most certainly don’t know well enough to impose upon with a request for public feedback.

At first glance, this seems problematic, but after reflecting on it a bit, it seems to be a fairly sound way of boosting an otherwise low signal-to-noise ratio as well as eliminating spam and trolling. When you “subscribe” to a “branch,” or conversation in Branch, you get updates via email and your Branch inbox. How very quaint.

But those are just minor quibbles.

Branch was co-founded by Princeton drop-out Josh Miller in New York City with backing from Ev Williams’s, Jason Goldman’s, and Biz Stone’s Obvious Corporation.

Stone told Jessica Roy, writing for the New York Observer, “Thoughtfulness makes Branch different. Every decision made in building the platform was given craftsman-like attention, and that sort of attention has an impact on the way people perceive and use the service.” As Roy notes, “Branch, with its invite-only model and focus on quality conversations among identified users, is one of the first well-backed attempts at revitalizing online discourse, but it’s also a gated community seeking to promote intelligent dialogue: Unlike most of the internet, no dumb, off-topic, or anonymous opinions are allowed.”

After taking a quick look at Branch—one of the first generation of Twitter spawn to hatch—it seems to offer an interesting structure for conversations (and side conversations, which could be really, really interesting) but little interoperability with other systems and no way to get what you have to say in (except through Branch itself) or what you’ve said out.

No job too small for DrupalSquad

Published Wednesday, 29 August 2012 8:34AM CDT by filed under Internet

0
No job too small for DrupalSquad

DrupalSquad, a service providing ala carte development, service, and support for website owners running the Drupal content management system (CMS), was announced at DrupalCon Munich. A joint venture of Warecorp, based in Minneapolis, and New York City-based New Amsterdam Ideas, DrupalSquad promises to make it exceptionally easy to purchase services related to Drupal in small, affordable bits. Although DrupalSquad has offices in Seattle, New York, Minsk, and Minneapolis, it’s services are currently offered only in English.

DrupalSquad is currently in private beta and adding new customers on a first-come, first-served basis.

Here’s how it works: A Drupal website owner visits DrupalSquad’s website and enters a brief description of his or her problem or project outline. DrupalSquad then provides an online estimate which the website owner can accept or reject. All estimates are provided at no charge nd are fully guaranteed. If the website owner accepts the estimate, he or she enters their credit card information on the DrupalSquad website and DrupalSquad’s technology team begins work, updating their progress in the online job tracking system.

DrupalSquad’s on-demand approach alleviates the problems associated with long-term commitments, a focus on only large, project-oriented work, and having to vet smaller developers’ level of expertise and tendency to take on more work than they can complete. Following the wisdom of Mr. Natural, DrupalSquad uses a “purpose-built task management platform” ensuring that the right tool is indeed used for the job.

Drupal is an incredibly complex piece of software and something like this has been needed for quite a while. I only wish my current CMS of choice—ExpressionEngine—had a similar offering.

[Ed. note: As I was researching this article, I became aware that a former colleague, Leif Utne, is DrupalSquad’s vice president of business development and an employee of one of DrupalSquad’s corporate parents, Warecorp.]

Medium: Quality through degrading authorship isn’t likely

Published Tuesday, 28 August 2012 8:16AM CDT by filed under Internet

0
Medium: Quality through degrading authorship isn’t likely

Twitter is six-and-a-half years old. In tech time that’s old; really old. It started life as a short message service (SMS) communication platform for small workgroups within Odeo, a podcasting company. In 2010, Ev Williams stepped down as Twitter chief executive and it’s been mostly downhill since. Williams’s other big success, Blogger, was also an off-shoot of a larger, unsuccessful project—Pyra’s project management software.

Williams’s next big adventure—again with his Twitter and Blogger partner Biz Stone—is Medium, an attempt to raise the quality level of publishing on the web with a new publishing platform. Articles are organized into “collections” that share a common theme and template and can be either open to submissions or closed. Anyone with a Twitter account can read and rate Medium articles. Only an invited elite are allowed to actually publish on Medium so far. Some Medium collections are text-dominant; some are photograph galleries.

Dave Winer notes that Medium’s collections are upside-down categorization: “Instead of adding a category to a post, you add a post to a category.” Instead of organizing content chronologically, like weblogs, Medium organizes content based on reader ratings. The concept is that the cream will rise to the top, becoming more visible.

Joshua Benton, writing for the Nieman Journalism Lab at Harvard, notes that for the last eight years or so, publishing on the web has migrated from individual-driven publishing back to centralized institutions. “That was when a few smart people realized that there was a balance to be found between the organization and the individual,” writes Benton. “The individual sought self-expression and an audience; the organization sought sustainability and cash money.” The new business model surrounding publishing, Benton observes, revolves around serving users “by helping them find an outlet for personal expression, then build a business around those users’ collective outputs.”

Benton also points to the second-biggest downside to Medium from my perspective: “... It degrades authorship, renders it secondary, knocks it off its pedestal.” Clicking on a byline in Medium, for example, links to the author’s Twitter feed, not a bio or archive of the author’s other work. Benton claims that this is a feature because authorship doesn’t scale. It’s the collection—not the author—that matters in Medium. “Medium doesn’t want you to read something because of who wrote it; Medium wants you to read something because of what it’s about,” writes Benton. And, as Benton points out, when authorship is degraded, all authority (and probably financial benefit) rests with the platform. That Medium hopes to raise the qualitative bar while simultaneously degrading authorship is a disturbing irony. Quality has consistently been associated with authorship, not platform. The power of the hypertext link ensures that will remain the case on the web. The best advice I can offer Williams’s and Stone’s team is to spend time (re)reading Robert Pirsig’s Zen and the Art of Motorcycle Maintenance, paying special attention to Phaedrus—especially his reemergence—and Pirsig’s Metaphysics of Quality.

That’s not to say that topic-based publishing on the web won’t be successful. It almost certainly will, especially in terms of discoverability of useful information. It’s just that there’s no real need to separate authorship from topicality; in fact I’m pretty sure that author discoverability within topic streams will emerge as the most successful model. Unfortunately, it will come at the expense of serendipity; some of us will gladly give up interesting and accidental for useful topicality.

But the biggest downside to Medium from my perspective is its lack of interoperability. There are no RSS feeds, no way for a degraded author to get his or her content out of Medium. Discoverability is crowdsourced and siloed, so the chances for serendipitous accidental discovery—something I find absolutely crucial—is replaced with homogeneity. Once again Dave Winer, in his first Medium article, articulates this succinctly. Winer has pledged “to only use systems that let me flow stuff in and out while maintaining originals in my own space,” so his Medium post is surprising. He explains in another article on his own site how this came to be and his hopes for Medium.

I’ll see Winer’s pledge and raise it with the suggestion that we all only use systems that let us flow stuff in and out while retaining the information authority of our original work.

Page 2 of 26 pages  < 1 2 3 4 >  Last ›