Is there any hope for an API, like a NodeJS based one or something like that in the futur?
We'd certainly like to build and offer a public API for developers - right now, the site is built exclusively using JSON API calls; you can see some of them if you look at network requests while browsing around the site. If you're creative, I'm sure you can come up with a way to use these APIs...
That said, a proper, well-documented API is something we'd like to offer, but will likely have to wait until we've launched, or we get a bunch of requests for really awesome apps people would like to make. :D
A simple rest api would be more than enough.
Rest is easy to use from many coding languages as it is a simple http(s) request and is powerful.
Ahah yeah sorry I totally meant REST! I was just thinking about NodeJs techs and my mind got confused!
Nice, thanks for the hint, I'll look at that! And for the answer!
Looking forward to this happening. Why? I think this site would be yet only the second after SF to ever have one :p
So please make this happen! And if you do I am sure it'll be good. =) There's a number of things I can see being coded already - for instance, a dropbox-esque sync system for artwork. Drop it in, it uploads as draft! A subfolder with all the metadata stored as JSON to keep information backed up locally. Would allow an artist to "draw directly to the site", so to speak.
Just one of this bird's random thoughts. o.o
Hehe yeah, I'm currently developping a mobile app, there is so much to do!
I'd very much like a public API with OAuth2 authentication, as I'd like to hook my own app into Furry Network. In the meantime, if you're happy with us reverse-engineering the app's internal endpoints, I can do that for now.Depending on what language the site is written in, I'd like to offer my services in building a public-facing API. With Weasyl's announcement that they're going open source, it's my intention to assist with a similar project there, expanding their existing but limited API.
I know the site is still in beta, but im going to try to document the API that is in place, if anyone wants to help just ask :)
I have kinda left thé dev projection I started when I asked thé question. But i may start again in à few weeks so thanks for thé Doc!
I'd love for an OAuth or OpenID endpoint to be added to support at least basic web-app pairing; with that a lot of the other API functionality would fall into place almost automatically since the site is already so heavily JSON based.
Honestly just keep building the site using JSON and client-side formatting, and 99% of the work for an API is already done, you don't even need to 'officially' support any of it beyond the authentication endpoints that'd be needed, just make old API calls return an error if ya' replace them and web-apps can adapt while you're still sorting out the site fully.
Authentification does work now, but poorly. I've used it with "success" but I get randomly diconnected. Since the site is in beta it is enought at the moment to use the beta "API".
Well without a unique ClientID for apps you can't really do OAuth/OpenID stuff, there's no way to register for one of those that I can see.
Yes of course, at the moment the only way to use the API is just to retreive the Bearer id and work with it until it is renewed.
It would be great to have a simple REST api to use - e621 have a great one that has been useful in some small app development I've been doing.
An publicly documented API would awesome, I'd love to e.g. download stuff from this website to watch it on my phone when I'm driving to or from work.
Customer support service by UserEcho