Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
paulhallett
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
31.
▲
Searching for Approximate Nearest Neighbours Using Python
(developers.lyst.com)
15 points
by
paulhallett
11y ago
|
0 comments
32.
▲
by
paulhallett
11y ago
I think we've encountered another situation where developers who don't fully understand HTTP best practices and standards, are asked to adapt their internal API services to work on the web :(
33.
▲
by
paulhallett
11y ago
All the methods that need to append `add`, `delete`, `update` to the URI. Why aren't you just using HTTP methods for this? Why do I have to POST everything? Do you know what POST is supposed to be used for?
34.
▲
Asynchronous Web API Services
(phalt.co)
1 points
by
paulhallett
11y ago
|
0 comments
35.
▲
by
paulhallett
11y ago
Deprecating an API is a bad way to go, especially if the API is fairly new. This post is telling me two things: 1) Dropbox's API was not designed correctly the first time. It should not just be a representation of their internal stuff
36.
▲
How I Would Build Dropbox's New Web API
(phalt.co)
15 points
by
paulhallett
12y ago
|
2 comments
37.
▲
Building a Star Wars API: An Update
(phalt.co)
2 points
by
paulhallett
12y ago
|
2 comments
38.
▲
by
paulhallett
12y ago
Oh wow you were there? Thanks!
39.
▲
by
paulhallett
12y ago
Local caching will be the way to go. All resources will have a "date_updated" or similar attribute which you can check against.
40.
▲
by
paulhallett
12y ago
This is mostly just a typo in the examples I put, but I will consider using only strings for this type of stuff, to avoid issues.
41.
▲
by
paulhallett
12y ago
Bloody markdown and no spell checker. I rely on them far too much, thank you
42.
▲
by
paulhallett
12y ago
Oh that's a good point. Do I want my data to be consistent with the 1997 releases or the originals!?
43.
▲
by
paulhallett
12y ago
Good ol' scraping from websites like wookiepedia. And watching lots and lots of Star Wars. I have the blurays, so I should be in for a fun experience whilst collecting the nitty gritty data.
44.
▲
by
paulhallett
12y ago
So RESTfully, I think this is normal. You should be able to call a resource and then be fed back all of those resources (usually paginated to say, 20 per request). It will have this style of lookup.
45.
▲
by
paulhallett
12y ago
PokeAPI is getting an update - http://phalt.co/if-you-have-data-they-will-consume-it/ and it will have better fuzzy matching.
46.
▲
by
paulhallett
12y ago
Ah, you didn't see the film_id & episode_id reference in the second example?
47.
▲
by
paulhallett
12y ago
:D My other API for Pokémon is also great for demos and teaching APIs - http://pokeapi.co
48.
▲
by
paulhallett
12y ago
Check the bottom of the page ;) We'll have episode VII details as and when it gets released.
49.
▲
by
paulhallett
12y ago
The data is being scraped from sources online and by watching the films about a thousand times. As the data is already available freely elsewhere, I won't be charging or keeping the data, I'll provide it just like I do on http:&#
50.
▲
by
paulhallett
12y ago
Ah thanks! It would be far more exciting if it was the weapon though...
51.
▲
by
paulhallett
12y ago
I guess the main reason is that data dumps are sometimes hard to sift through, can become inconsistent (if there are multiple copies) and because from my experience, if you provide an API for something, someone will use it. On the flip side
52.
▲
by
paulhallett
12y ago
This is awesome, and another great example that "If you provide data, people will consume it"!
53.
▲
by
paulhallett
12y ago
Please do :D
54.
▲
by
paulhallett
12y ago
As well as ID, we'll do some fuzzy matching on the URLs as well, so GET /api/vehicle/t-65-x-wing and GET /api/planets/mustafar will also work
55.
▲
by
paulhallett
12y ago
ETA is end of January :)
56.
▲
by
paulhallett
12y ago
Good point. I set the URL config to catch all URLs and redirect back to the home page (anticipating people would try the API). Once things die down I'll push up an update. Getting a heavy bit of traffic right now.
57.
▲
by
paulhallett
12y ago
Good spot!
58.
▲
by
paulhallett
12y ago
We're working on it, sorry!
59.
▲
by
paulhallett
12y ago
Hi Mike, this is Paul, I am making this API too :D
60.
▲
by
paulhallett
12y ago
Hey! Thanks. I made the Pokémon API as well - http://pokeapi.co The backend on that is Django. I might stick with what I know, or build SWAPI in Go. At the moment, we're still very early stage, so we can choose soon.
More ›