I posted to the mailing list two issues over the weekend.One about result number restriction:
Hi, I was just reading the documentation which gives the following URL as an example:http://api.search.yahoo.com/MyWebService/V1/relatedTags?appid=YahooDemo&tag=yahoo&results=2 It is supposed to return only two results yet all 48 are returned? Is this correct? I need to start using this API and I don't know if it will return the correct results. Kind Regards, Paul KinlanAnd the other about Contextual term extraction not processing results after an HTML style tag. i.e anything that has a "<" or ">" in:
Hi, I have been playing with the contextual term extraction API, and I have noticed (well at least I think I have) that if there is a HTML tag in the text for term extraction then the term extraction API doesn't examine data after the starting tag. For instance if I had the following text:I got two replies on Monday (1 day after I posted the problem), one confirming that it is a bug that is being worked on and the other confirming that my problem has just been fixed. Way to go Yahoo! That is the way that I like to see services run. Keep up the good work.I have been trying to play with Blogger BackLinks, and I can say that I don't really like them. I don't really like them because people have to use them! I was expecting Blogger Backlinks to automatically link into the Google Blog search to find a list of all the blogs that link to my post. And then update my page from there. I think what I will do is develop a version that does use them, it will fire a query off to Google and see what happens from there. I mean, after all Google Blog search allows you to do this, and export the results as RSS.The API only seems to analyse up to and including href="xyzabc">. Anything after this in not included in the results. Has anyone else experienced this? Kind Regards, Paul Kinlan www.kinlan.co.uk
About Me: Paul Kinlan
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.