vBulletin API for FP - Developers

Although an API is planned past vBulletin 4.1 I want to look into making one. If it was implemented on Facepunch what kind of features would you want and why?

The ability to retrieve threads and their posts, just for making personal applications and desktop widgets, customised tickers and such.

Retrieve complete threads, this could be useful for archiving and referencing, like Torquil said. Also retrieving users profile information and post count would be cool, as well as lists of posts and threads created by said user.

I can foresee people wanting ratings to be accessible to someone can make a ratings counter for the rating whore masses.

make threads update live with new posts / edits

~Thread location ~Thread name ~Username of posts ~Post Count ~User usergroup ~Posts & Signup Month/Year ~Ratings ~Online/Offline ~Login Abilities ~Avatars ~Ability to sent posts That's all I can think of. Really want this, it'd be quite awesome. With all of the above it'd be possible to create a fairly basic Facepunch application.

Well you already may know what I'm going to say, but: I would like to have a TapaTalk API (so I can use TapaTalk). You may extend that API with features other people do request. It already provides most of the requested stuff here.

[QUOTE=aVoN;24683572]Well you already may know what I'm going to say, but: I would like to have a TapaTalk API (so I can use TapaTalk). You may extend that API with features other people do request. It already provides most of the requested stuff here.[/QUOTE] Is the TapaTalk API easy to use by other applications?

Are we ready to change to VB4 now?

[QUOTE=garry;24684581]Are we ready to change to VB4 now?[/QUOTE] Yea, we are ready.

[QUOTE=aVoN;24683572]Well you already may know what I'm going to say, but: I would like to have a TapaTalk API (so I can use TapaTalk). You may extend that API with features other people do request. It already provides most of the requested stuff here.[/QUOTE] I asked about it in the labs thread and he said that VB4 is standard to have a mobile theme or something so hopefully it's not required.

[QUOTE=garry;24684581]Are we ready to change to VB4 now?[/QUOTE] Do it already.

[QUOTE=garry;24684581]Are we ready to change to VB4 now?[/QUOTE] No, not yet. The API isn't high on the priority list I'll probably add it later.

[QUOTE=compwhizii;24686029]No, not yet. The API isn't high on the priority list I'll probably add it later.[/QUOTE] Who said anything about the API? I still think it's almost time for Vb4.

[QUOTE=andersonmat;24690205]Who said anything about the API? I still think it's almost time for Vb4.[/QUOTE] Yeah it's almost time. I think there's a few more things to do before switching

Right now the only thing that is stoping me from wanting VB4 is there is no "Read Threads" or "Popular Threads" pages. Other than that I think it is almost time. [editline]06:53PM[/editline] Oh yeah and the mobile skin.

Is vB actually worth it if it takes this long to get to a functional state?

[QUOTE=jaybuz;24691373]Is vB actually worth it if it takes this long to get to a functional state?[/QUOTE] So stopping and learning how to modify another forum software, recoding all of the custom stuff, and editing the style (Which is taking up most of the time) would take less time? How do you calculate that?

Possibly for a mobile application to call posts and threads down. Also a ticker style page in the apps home screen.

Give us enough apis to call so we can make a mobile Facepunch reader

[QUOTE=compwhizii;24693356]So stopping and learning how to modify another forum software, recoding all of the custom stuff, and editing the style (Which is taking up most of the time) would take less time? How do you calculate that?[/QUOTE] Uh, I think he was on about whether it was worth switching at all.

[QUOTE=Marlamin;24683625]Is the TapaTalk API easy to use by other applications?[/QUOTE] Yes, it is. At least I have seen several apps now (just take XDA-App) which uses the TapaTalk API. How I see it so far, it's just doing normal http requests (POST or GET - Have not looked so deeply into the API yet) on a php-script. But you have to contact the tapatalk team before you get the documentation on the API ([url]http://www.tapatalk.com/api/api.php[/url]). [editline]01:13PM[/editline] [QUOTE=PieClock;24685081]I asked about it in the labs thread and he said that VB4 is standard to have a mobile theme or something so hopefully it's not required.[/QUOTE] Yes I read it too. But I still would like to have a simple PHP script installed (basically he just needs to upload it to the webserver - copy & paste job) to vBulleting so I can use my beloved TapaTalk.

Multiple output formats. Replacing .php with .json gets a JSON representation of any page. Replacing it with .atom gets an atom feed, .xml gives you XML version, etc. The json version should be returned as jsonp if an additional "&jsonp={callback}" arg is added to the query string.

Some progress [url]http://fpvb4.compwhizii.net/fp_api.php?module=forum[/url] Lists forums. By default it outputs JSON but you can also choose XML with the format parameter. More will come later. Adjust depth with depth parameter. [editline]08:28PM[/editline] [url]http://fpvb4.compwhizii.net/fp_api.php?module=forum&format=printr&depth=3&node=1[/url]

Maybe when you're done you can make an API guide with some examples so some users can figure out what to do.

yeah

[url]http://fpvb4.compwhizii.net/fp_api.php?module=thread&node=2[/url] List threads, more options in a bit

Why do we need a custom API with no support from anything when we could just have TapaTalk which is already supported by several applications and is more mature? It makes no sense.

[QUOTE=Xera;24731022]Why do we need a custom API with no support from anything when we could just have TapaTalk which is already supported by several applications and is more mature? It makes no sense.[/QUOTE] [list=1] [*]We have complete control over. TapaTalk's code is a mess and I would not enjoy modifying it. [*]Flexibility. From what I understand TapaTalk only does XML-RPC to communicate to it's application. We can support any protocol we want. [*]Our API will be documented so that anyone can develop an application to use it. I don't think TapaTalk has that. [*]We can support Facepunch only features. [*]We can add control over who can use the API with API keys and such [*]I am developing the API alongside Hexxeh who is developing a mobile application for it. [/list]

Ticker, it also should give the client application information on which usergroup someone is in. [editline]07:48AM[/editline] Also, whats taking the design so long, that should be done after a day of work and a week of tweaking.