Taking another look I found out why YQL was not always working.
Now added it back in with common words as the fallback – you should always get some tag now!
https://www.dropbox.com/s/me0u6zl5obmlhkf/auto-tags.zip?dl=0
To note, this is hacked together from the original plugin (https://ww.wp.xz.cn/plugins/auto-tag/) and the YQL modification that Beer made (https://ww.wp.xz.cn/support/topic/auto-tags-yql-edition?replies=14)
if you make a plugin which allows using api keys like simple tags (look at the services, opencalais, zemanta, datatxt, t4s) but auto tags by hooking on post saving I would pay for it.
I have looked into the plugin but it uses js and ajax to make the api calls I think, and it should be ported to php into functions to hook to the post publishing.
A couple of options could be:
– Rotate api keys, use only one for each post.
– Use all the api keys, use only the 1-3 most relevants
– of course limit number of tags and black lists.
I would pay for a plugin like this.
There is still a fundamental problem I think with requests length, $content that exceeds ~5840 characters results in a api call which seems yahoo servers can’t handle.
– easiest solution: chop the content at ~5840 char every time and just get the tags of that content
– complex solution: split the content and do an api call for each sub string, than merge tags results and filter out duplicates.
