Kevin hinted at something like this when I was discussing making a FUSE (file system in userspace) implementation of the API on dev.meta.

It would work like this, assuming you had the file system mounted on /stacks :

cat /stacks/stackoverflow.com/users/1/reputation

... You'd see Jeff's reputation. The problem is (and was) is that I'd need to be able to discover all API methods to organize and set up the FS hierarchy, which means some method to discover all available methods and hints as to what they return.

The particular question went to radio silence, I'm not sure if something like that made it into the current beta, but I hope it does :) A FUSE implementation would let lots and lots of languages for where no API bindings exist access the API rather easily.

Edit

The discovery API is here: http://api.stackoverflow.com/0.8/help (of course replace the version as appropriate). See this FAQ. Happy Happy Joy Joy ...

Kevin hinted at something like this when I was discussing making a FUSE (file system in userspace) implementation of the API on dev.meta.

It would work like this, assuming you had the file system mounted on /stacks :

cat /stacks/stackoverflow.com/users/1/reputation

... You'd see Jeff's reputation. The problem is (and was) is that I'd need to be able to discover all API methods to organize and set up the FS hierarchy, which means some method to discover all available methods and hints as to what they return.

The particular question went to radio silence, I'm not sure if something like that made it into the current beta, but I hope it does :) A FUSE implementation would let lots and lots of languages for where no API bindings exist access the API rather easily.

Edit

There is a help option , but its not quite convenient to parse.

Kevin hinted at something like this when I was discussing making a FUSE (file system in userspace) implementation of the API on dev.meta.

It would work like this, assuming you had the file system mounted on /stacks :

cat /stacks/stackoverflow.com/users/1/reputation

... You'd see Jeff's reputation. The problem is (and was) is that I'd need to be able to discover all API methods to organize and set up the FS hierarchy, which means some method to discover all available methods and hints as to what they return.

The particular question went to radio silence, I'm not sure if something like that made it into the current beta, but I hope it does :) A FUSE implementation would let lots and lots of languages for where no API bindings exist access the API rather easily.

Kevin hinted at something like this when I was discussing making a FUSE (file system in userspace) implementation of the API on dev.meta.

It would work like this, assuming you had the file system mounted on /stacks :

cat /stacks/stackoverflow.com/users/1/reputation

... You'd see Jeff's reputation. The problem is (and was) is that I'd need to be able to discover all API methods to organize and set up the FS hierarchy, which means some method to discover all available methods and hints as to what they return.

The particular question went to radio silence, I'm not sure if something like that made it into the current beta, but I hope it does :) A FUSE implementation would let lots and lots of languages for where no API bindings exist access the API rather easily.

Edit

The discovery API is here: http://api.stackoverflow.com/0.8/help (of course replace the version as appropriate). See this FAQ. Happy Happy Joy Joy ...