I have been using the yahoo yql service for reading rss feeds from websites, but today the rest url returned error
https://query.yahooapis.com/v1/public/yql?q=select%20title%20from%20rss%20where%20url%3D%22http%3A%2F%2Frss.news.yahoo.com%2Frss%2Ftopstories%22&format=json&diagnostics=true&callback=
Result :
{"query":{"count":0,"created":"2017-08-29T03:09:44Z","lang":"en-US","diagnostics":{"publiclyCallable":"true","url":{"execution-start-time":"1","execution-stop-time":"3","execution-time":"2","http-status-code":"400","http-status-message":"Bad Request","content":"http://rss.news.yahoo.com/rss/topstories"},"user-time":"3","service-time":"2","build-version":"2.0.164"},"results":null}}
Did they stop the service or any change needed to get it worked?
I've been having the same issue. If you keep calling it, it eventually works. I put a workaround in to wait a second and try again for now. Hope you get an answer soon!
Related
I referred to the other post in stackoverflow in an attempt to set up a RSS feed for Google news for my website. URL format for Google News RSS feed
Here's an example link:
https://news.google.com/rss/search?q=NERU+GmbH+&+Co.+KG+when:7d&hl=de&gl=DE&ceid=DE:de
If you put the link into browser, you will see result with pub date back in 2022, despite the "+when:7d" parameter in the URL
I cannot find any documentation on this as well. Any thoughts?
Probably this is because there is no results for the given search terms at the given time range.
If you enter to this link - which is the non-rss version of your link:
https://news.google.com/search?q=NERU%20GmbH%20when%3A7d&hl=de&gl=DE&ceid=DE%3Ade
You wont see any results.
Consider also that Google News RSS "if I recall correctly" is deprecated, so, its URL parameters might not work as expected.
I'm using POST https://www.instagram.com/query/ and able to get many comments with a query:
ig_shortcode(<media-code>){comments.last(300){count,nodes{id,created_at,text,user{id,profile_pic_url,username,follows{count},followed_by{count},biography,full_name,media{count},is_private,external_url,is_verified}},page_info}}
But I can't do it for likes. I get error 400. I've tried the query:
ig_shortcode(<media-code>){likes{count,nodes{user{id}}}}
but the result is limited to 10.
There is offical GET /media/media-id/likes but it's too complicated to get the permission.
Are there other ways?
I found an unoffical Instagram-API which does requests like official Instagram mobile client without any permissions: https://github.com/mgp25/Instagram-API
It has working method $i->getMediaLikers($mediaId).
How would I get the next page or more results for a feed?
For example, when I go to Security Now feed page, there is no "next" link of any kind and the url parameter of "page=100" does nothing:
http://leoville.tv/podcasts/sn.xml
I get only 1 page of results of about 20 episodes. However my Google Reader can successfully retrieve episodes that are earlier than that.
Indeed it is true that Google Reader caches the items and it is NOT possible to paginate on RSS2, RSS or Atom feeds (unless they have rel=next link, which none of them seem to have).
However, we can leverage the existing Google Reader infrastructure, with some work, to retrieve a list of, say 200 items!
Given the above podcast url we retrieve the latest 200 episodes by:
Using the ...google.ca/reader/atom/feed prefix instead of the usual view/feed as can be seen in your google reader.
Appending n=200 as the query parameter.
So we have:
http://www.google.ca/reader/atom/feed/http://leoville.tv/podcasts/sn.xml?hl=en&n=200
There is a very insightful reverse-engineered google-reader API project located at http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI
Google reader caches RSS entries. You can't get any more from the actual feed if they don't allow for it.
I am trying to subscribe to an RSS feed for a fighter's history via MixedMartialArts.com, but this particular website updates the pubDate for each of the fights, causing duplicates every time the pubDate is updated.
http://www1.mixedmartialarts.com/?go=rss.fighterRecord&pid=8878384A5C892D13
However, other attributes of each remain the same, particularly <title>.
What can I do (maybe via Yahoo Pipes, or other normalizer) to fix this issue temporarily until they correct the problem on their end?
I use Google Reader, and find that it is very good at dealing with malformed feeds.
I understand that when fetching an atom feed, you can specify the number of items to return, and the items will have a continuation field that you can use to start subsequent fetches at a position after the items you've already fetched. The question is: how do you find out if there's anything more to fetch without actually trying to fetch more?
Every atom feed that you get from the Google Reader API will provide a "continuation" token if there's more on the server. If this token is not found in the atom feed, there is no more.