It’s just data

The Tragedy of the API

Evan Williams: I perhaps now understand the need for standards bodies more than I ever have before—even though the term gives me willies. [via ScriptingNews]

Returning to Business

For the first time in two weeks, the swelling and infection from the tick bite in my leg is starting to recede, and today I didn't wake up feeling as dizzy as I have been feeling the last week. I've paid my price for carelessness in not being... [more]

Trackback from Burningbird

at

Pingback from TIG's Corner

at

We're trying to figure out how the SSA can help thsi situation.  Discussion on list.  Here's a Wiki page:
http://www.socialtext.net/ssa-edit/index.cgi?Generic_Weblog_API

Posted by Marc Canter at

I don't know whether the SSA could or could not help.  I clicked Marc's link and it asked for authentication and registration just to read.

plonk

Posted by Ken MacLeod at

My (and Marc's) bad.  Marc posted the editing link, which requires registration.  The browsing link is:

  http://socialtext.net/ssa/index.cgi?Generic%20Weblog%20API

Posted by Ken MacLeod at

I doubt a standard is needed, but if one is created, I'd vote for something like Sam's RSS-in-SOAP.

The existing, widely adopted, protocols are relatively restricted.

Posted by Mark A. Hershberger at

Mark, thanks.  It is nice to know that somebody is listening.  But unless you are Dave, Evan, Ben, or Mena, it looks like your vote doesn't count...

Simple.  Extensible.  Unicode enabled.  Standard.  Based on RSS.

Sigh.

Posted by Sam Ruby at

Yeah, I was following that thread, the silence was deafening. How depressing.

Posted by joe at

Looks like we're locked in the trunk this time.

Posted by Simon Fell at

Since I'm writing my own multi-blog server software (in AxKit and
Postgres) and weblogging client (in Emacs, of course), I can ignore
any trunks that they create.  I think Joe and Sam can, too.  Even if
the "big guys" ignore it, we'll have something more standard than the
"Standard".

Of course, I can't ignore any of the weblogging APIs out there.
That's just the reality if I want people to use my server.  But,
suppose I started a moderate weblog hosting operation that supported
SOAP-in-RSS and told my users what they could get if their tool
supported it, Wouldn't I then have some sway with the developers of
tools like w.Bloggar?

There is no trunk if you write the server software and bring lots of
users to bear.

(Speaking of Unicode: the funny thing was that I briefly had some
arabic and chinese language testers.  I don't know how well it worked,
but I know I saw non-western charecter-sets.)

(Isn't there some sort of auto-discovery link for the content api that you
could put on your comments.rss file, Sam?)

(Is the email comment interface down?)

Posted by Mark A. Hershberger at

s/SOAP-in-RSS/RSS-in-SOAP/;

Typos are the natural outcome of late-type typing.

Posted by Mark A. Hershberger at

And casting is the natural outcome of early manifest typing.  So?

Posted by James Robertson at

Email interface is back online, and there is no trunk.

Posted by Sam Ruby at

Looks like we're locked in the trunk this time. [Simon Fell] ...

Excerpt from matt.griffith at

Web Services, Weblogs and the Future.

In recent weeks a significant amount of discussion has been ongoing as to the future of Weblog APIs. At issue is that there are two similar, but different Web service APIs in use, but the community is in favor of one. Unaddressed issues remain and I... [more]

Trackback from tima thinking outloud.

at

Add your comment