Is Wikipedia geocoding API deprecated/down? - wikipedia-api

I've been playing around with the Wikipedia reverse geocoding API listed at:
https://www.mediawiki.org/wiki/Extension:GeoData
The specific API request I make is of the type:
https://en.wikipedia.org/w/api.php?action=query&list=geosearch&gsradius=10000&gscoord=37.786971|-122.399677&format=json
The API worked great in the past. Today, somehow, the API returns an empty JSON object. Is the API deprecated or down? I can't seem to find any details on the page or the API help page or the MediaWiki page.
If deprecated, is there any alternative I can use?

Apparently it was just a temporary stop: https://bugzilla.wikimedia.org/show_bug.cgi?id=72559#c4

Related

Is there any way to post updates in a business location using google's business api?

As the title says, I'm trying to find a way to post these updates (see picture below) using google's API, I can't find anything about it. I have checked google's business API documentation and most of it's endpoints are deprecated.
At the top of the page there is a deprecation schedule: https://developers.google.com/my-business/content/sunset-dates
There you can find the new API-Endpoint. I'm also looking for a solution to update opening hours, but it's not that easy to find any information. Even bing is better documented.

Twitter API V2 video url

I'm trying to fetch a tweet's video url using API V2.
Using API V1.1 I can use
https://api.twitter.com/1.1/statuses/show.json?id=<ID>&include_entities=true
and get the direct mp4 urls in the response at
extended_entities.media[0].video_info.variants
But using API V2 I can't seem to find any ways to get those, I was only able to get the video thumbnail but not the actual video.
I've tried it with both the lookup and the recent search endpoints but couldn't find a way to do that.
In lookup docs twitter says:
This endpoint was recently graduated from Twitter Developer Labs, and is the replacement of v1.1 statuses/show, v1.1 statuses/lookup, and Labs Tweet lookup. If you are currently using any of these endpoints, you can use our migration materials to start working with this new endpoint.
but that doesn't seem to be the case, is that feature not included ? Also if there is any other way to be able to embed a twitter video in a web page (without the tweet text) that'd be helpful.
The videos are not currently available in the Twitter API v2 at this time. This is a known request.
For those who still looking for an answer, you can do it on the V2 by adding the following parameters :
expansions=attachments.media_keys
media.fields=variants
Your final link should give https://api.twitter.com/2/users/{{uid}}/tweets?expansions=attachments.media_keys&media.fields=variants
Source : https://developer.twitter.com/en/docs/twitter-api/data-dictionary/object-model/media
Progress on twitter-api-v2 media handling, Maybe this will allow the video URLs too in the response.
https://twittercommunity.com/t/v1-1-media-endpoints-available-for-essential-access-in-the-twitter-api-v2/171664

Is there a REST API documentation that only publishes the root URL?

I´m trying to design a REST API for my application and I read a lot about best practices and how REST is supposed to work. One of the most important topics about REST is, that the resources should be linked via references and the client should only know the root URL of the API.
But I cannot find any API documentation that really does this. Every REST API documentation I ever read on the web shows an exact description of the URLs of the possible endpoints.
Is there any API documentation out there that only shows the root URL and describes how to navigate through the resources?
One of the most important topics about REST is, that the resources should be linked via references and the client should only know the root URL of the API.
The root URL and the media types, yes. The client needs to know where to start, and also how to interpret the responses it gets.
Your primary example of a REST API would be the world wide web. You point your browser at www.google.com, and then you just follow links and submit forms until you get the result you want.
Another REST API that might be familiar is Atom Syndication / Atom Pub.
More academically, there is RESTBucks. That paper was somewhat popular, and you can find a number of sample implementations around.
Jon Moore (2011) presented a good demonstration of a hypermedia API.
Every REST API documentation I ever read on the web shows an exact description of the URLs of the possible endpoints.
Yes; bad examples are much more common than good examples.

Soundcloud explore section

I am exploring soundcloud's API, and I have seen that thought through the web you can access explore sections, I haven't found any docs that help you to do so through the API.
Anyone has tried this before?
soundcloud explore section uses new API calls that are still not documented. same with stream.
but you can check under the hood (in chrome developer tools -> network tab) to find new api calls.
for example, main explore section points to https://api.soundcloud.com/explore/sounds/category?limit=10&offset=0&linked_partitioning=1
and rock section points to
https://api.soundcloud.com/explore/sounds/category/rock?limit=10&offset=0&linked_partitioning=1
p.s. don't forget to include your client id in the calls
The API has been updated. You can use following URL to access the explore section (based on #cucko's reply):
https://api-v2.soundcloud.com/explore/categories?limit=10&offset=0&linked_partitioning=1
With client id in the call:
https://api-v2.soundcloud.com/explore/categories?limit=10&offset=0&linked_partitioning=1&client_id=YOUR_CLIENT_ID
The API has been updated.You can use following URL
https://api-v2.soundcloud.com/charts?kind=top&genre=soundcloud%3Agenres%3Aall-music&limit=20&offset=0&linked_partitioning=1&client_id=YOUR_CLIENT_ID

Replacement for Google AJAX search for Local

Since Google has deprecated their old web search API as of recently, what are people using to do customized local search? (i.e. search for "donut shop" near this latitude and longitude) Sticking with the deprecated API? Using another Google API? Another provider entirely?
Their suggestion to use their new Custom Search API doesn't seem useful for local. Maybe i'm missing something under my nose?
Google Places API is in developer preview.
I personally used Yahoo! Local Search
The Yelp API is pretty slick as well -- it'll give you local search capabilities and you can also get ratings information.
I've found this Quora link quite useful:
http://www.quora.com/What-is-the-best-alternative-to-Googles-local-search-API