4a0aa9d681
Prior to this change ( setting the Mobiquo_is_login: true header ), the official android client would do many login calls - one every other API call, more or less. This makes us persistent instead.
Tapatalker
This project is intended as a Tapatalk-to-Discourse bridge, with the primary aim of allowing mobile users to receive push notifications of updates in a Discourse forum.
It's implemented as a Tapatalk-compliant XMLRPC endpoint that talks to a Discourse instance using its REST API. Keeping both services at arms-length should have some benefit.
The primary motivation is for the new York Minxters roller derby forum, so some of this might end up being a bit rough and ready. We'll see.
It is, in fact, rough and not-yet-ready. Current setup needs all the commits in https://github.com/lupine/discourse_api , sinatra, chronic, maybe some other bits.
I'm currently running "Forum Fiend" against this code. The aim is to get to basic guest and logged-in-user support for reading and replying to topics, as well as receiving push notifications.
To get it running, I'm using rackup to get a HTTP server up. I then use nginx with a proxy_pass directive to send http://my-forum/mobiquo/mobiquo.php to the server.
Current status is that you can view the category list and enter individual topics (sometimes) with forum fiend. Another Android application - "convo" - doesn't accept us as a valid Tapatalk endpoint yet. No idea on Android. We currently implement enough of get_config that the tapatalk directory will accept requests to register sites running this. No idea if the official client can cope, though.
So many TODOs...