Get users -> deactivate 3rd party access to API -> lose users -> reactivate 3rd party access The circle of life. Wonderful.
Opening the Instapaper API
21–30 of 32 posts
Re: Opening the Instapaper API
#22Get users -> deactivate 3rd party access to API -> lose users -> reactivate 3rd party access The circle of life. Wonderful.
Re: Opening the Instapaper API
#23All 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?
Because it's an RPC-based API?
Re: Opening the Instapaper API
#24This surprises me a bit: "All requests should be made via the POST method, and all parameters should be passed in the POST request-body and not in the query-string." So even typical GET are sent as POST (/api/1/bookmarks/list) Is there any reason to do that?
That it's RPC over HTTP, POSTing everything is the normal (and, really, proper) way to do RPC over HTTP.
Re: Opening the Instapaper API
#25How do you find an RSS feed of all archived Instapaper articles? This is needed to connect Pinboard with Instapaper.
Re: Opening the Instapaper API
#26How do you find an RSS feed of all archived Instapaper articles? This is needed to connect Pinboard with Instapaper.
It's provided as a `link rel="alternate" type="application/rss+xml"` on the /archive page (or any other folder). Sadly less and less browsers display these (or even indicate there's one) so you'll have to dive into the JS console or page source to extract the URL. I don't think there's an easier way to get at the RSS feeds.
Re: Opening the Instapaper API
#27I love this! I feared that Instapaper development would stagnate after Marco sold it. Even though he said that they will develop a lot of new features, you know how it often times is when companies/apps get bought. But i'm happy to see quite the contrary! What i love about Instapaper is the fact, that it doesn't fuck around. It tries to be one thing and one great thing only. I don't want to see tweets, i don't want t…
Re: Opening the Instapaper API
#28I love this! I feared that Instapaper development would stagnate after Marco sold it. Even though he said that they will develop a lot of new features, you know how it often times is when companies/apps get bought. But i'm happy to see quite the contrary! What i love about Instapaper is the fact, that it doesn't fuck around. It tries to be one thing and one great thing only. I don't want to see tweets, i don't want t…
Unfortunately "not stagnating" and "developing a lot of new features" these days usually means you will in fact soon start seeing tweets, related articles and what other people think besides your texts.
Which is a shame, because I too love the minimalistic approach of Instapaper.
Re: Opening the Instapaper API
#29Re: Opening the Instapaper API
#30This surprises me a bit: "All requests should be made via the POST method, and all parameters should be passed in the POST request-body and not in the query-string." So even typical GET are sent as POST (/api/1/bookmarks/list) Is there any reason to do that?
It gets even better: > If the response is not valid JSON, it should be interpreted as an HTTP 503 "Service Temporarily Unavailable" error, and the request should be retried later. Why not just return 503?