I’m finding that Userscripts are fine for limited functionality like the earlier examples, but the more complicated ideas required a proper server. This ‘top-down’ screen-scraping approach comes with it’s own set of challenges. For example, while nesting a series of asynchronous Ajax calls that dig deep into posts, I think I set off a mini DoS attack on the Support forum. It lasted for about 10 seconds before I could kill the out of control browser, but it’s ok… I won’t be charging WordPress.com anything for testing their server load capabilities. 😉
I have moved my ‘experiments’ onto a server, and I’m currently exploring Natural Language processing of posts, using Google API’s. The pic below is a copy of a post being analyzed… It shows the identified entities, as well as a Sentiment Level score (Just how happy or unhappy is the author of this post?)
Really, I’m just playing around, but you never know what might come of it! If you have any thoughts or comments, let me know, and if you find this kind of stuff intriguing, then check out the Google NLP API here.
I added a bit of code to my WordPress Forums Support Userscript that searches the posts for the ‘typing’ tag or any part of the tag like ‘john is typing’.
Here’s a screenshot catching @timethief in the act of responding to a support post (the red topic). Nice!
Another idea that should be fairly straightforward… when responding to a post, have a little green light next to the editor that would change to red if someone has responded to the post since you started.
I’m just playing around, but I would like to know if you have any ideas/suggestions/comments.
Other potential scripting going forward;
- Grab support documentation and display based on tag / content.
- Auto tagging — Search the content of the post and suggest tags based on common keywords/phrases.
- Whois any domains found, and markup the post with results.
- Automatically generate canned responses based on tags found.