Hmmmm…
$.ajax({
type: “GET”,
url: “http://www.tumblr.com/edit/” + id,…
Looks like it just edits post immediately after posting it to add the tags, doing it via parsing the post edit page. No wonder Tumblr team dislikes it - missing-e generates two additional queries for every ask replied to, nearly tripling the server load.
Two queries? One to get the ID of the post and the other for submitting tags, or one to get whole edit form (with all data) and then one for submitting everything?
But yeah, when you put it that way it is understandable they don’t really like it that much.
Well, one query sends the answer form to the server, it gets sent anyway.
But missing-e also fetches edit form ($.ajax({type: “GET”,url: “http://www.tumblr.com/edit/” + id, … and so on ) with the second query, parses it, and sends it back ($.ajax({type: ‘POST’, url: this.url, and so on) to alter the tags with the third query.
And it uses html page (a bit more load on server), not the api, because it’s much easier to ban the application by its api key.
Yeah, that’s what I meant with the second part. So true, it indeed triples the load, for a single user that wouldn’t be a problem but with this many people using Missing-e…