DISQUS

Evan Prodromou · 1 year ago

Dave, thanks for the note about Identi.ca. I wanted to point any potential developers to our embryonic API documentation, here: http://laconi.ca/Main/Twitter-compatibleAPI . It's principly a diff between what we support and what Twitter has in their documented API.

We're very interested in hearing from devs about the API, whether we've implemented things correctly, what kind of response they're getting, and what's missing. We're especially interested in discussing how to compatibly extend the API to support new features in the future.

dave · 1 year ago

I added a link to your document in my blog post.

saperduper · 1 year ago

cool! really good news!

Enkerli · 1 year ago

Excellent news!
The API is probably a large part of what made Twitter so interesting and identi.ca can bring nano-/microblogging further through its emphasis on openness.
One way Twitter may benefit is also by getting some load off its servers while maintaining its overall architecture be the main basis for nanoblogging.

Pete Prodoehl · 1 year ago

As I suggested! :)

dhmspector · 1 year ago

Any ida why the site (http://laconi.ca/ - linked of of http://identi.ca/doc/source) that is supposed to have the sources code available is constantly a 404? 'been that way since day one.

Evan Prodromou · 1 year ago

I have no idea about that. It's been mentioned a couple of times before, though. I moved the laconi.ca site to its own server in early July, and the only reason I can imagine problems coming up is DNS propagation errors.

I can, of course, see the site fine.

jonknee · 1 year ago

Oddly enough I can't access it in Safari but can with FireFox and cURL. This is probably why you're seeing these complaints. Here's the message in Safari:

"Safari can’t open the page “http://laconi.ca/” because the page doesn’t exist. Make sure the address for the page is correct."

The problem seems to be that your server is responding with a 302 Found but not providing the other URL as a Location (it looks like a standard 200 OK request just with the wrong header).

john conroy · 1 year ago

Thanks for this: trackback from cmswire (near the end): http://tinyurl.com/6bdx9b

Pete Prodoehl · 1 year ago

Also, we are making TwitterFox work with identi.ca: http://identi.ca/notice/111135 http://flickr.com/photos/raster/2680148113/

MikeSchinkel · 1 year ago

I agree, this is an incredibly positive thing! All too often corporate ego or even developer ego gets in the way of common sense and pragmatism and what results are incompatible APIs. Hat's off to Evan Prodromou's wisdom. APIs are like the 3 prong electric plug; why would anyone think it makes any sense to build one differently when there are so many otherwise compatible electric outlets available?

That said, it's unfortunate that this Twitter standard that is being cemented is RCP-over-HTTP instead of truly RESTful services with resources-as-nouns and the HTTP GET/POST/PUT/DELETE as the only verbs. From experience that concern, which to some might appear as overly pedantic actually does provide some tangible benefits. But alas, nothing is ever perfect.

craniac · 1 year ago

Dave Winer,
Thanks for taking the time to make sense of identi.ca for me, and for promoting some interoperability in the micro-blogging venue.

wlohse · 1 year ago

You're so great, Dave. Thanks for thinking, and doing it out loud.