Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Ok, I thought you would say that. At the moment it seems stable. If someone does use the method wrongly, then I might just make it an editor, and not do the posting, and wait till a write API is created (hopefully I won't be old and dead by then ;)) It still gets Captchas if the users tries to post too much, and prevented from posting if the quality is too low, exactly like the site.
@GeorgeEdison luckily iOS manages the cookies pretty well, but there issues with that even. If we could have a login page that returned a JSON page saying successful or not, and documentation of what cookies are needed we could have write access without as much effort on the server side.
@GeorgeEdison, thanks, it's basically a "front" for the website, but it took a lot more time to get it work as much as it is now. If the routes that the StackExchange sites use to post questions were documented, and a variation of the login page were made, it would be much easier to do write access.
@KevinMontrose, I see the point about simplifying it. I have read lots about "problems" where there is more than one site on a server, having different certificates for multiple sites on one IP. Surely stack exchange is the opposite of that problem?