network profile
| bio | website | kevinmontrose.com |
|---|---|---|
| location | New York City, New York | |
| age | ||
| visits | member for | 3 years |
| seen | May 20 at 22:53 | |
| stats | profile views | 736 |
Stack Overflow Valued Associate #00004
For no good reason, I'm on twitter. I hear its compelling... somehow.
I also have a blog.
|
Mar 4 |
comment |
What sizes are the images available through the /sites endpoint? A few corrections. logo_url is whatever size the site's actual logo is, and can change as sites get new designs. favicon_url is an .ico, and can technically hold multiple resolutions, but 16x16 is guaranteed for favicons. Our trademark guidelines only restrict using the logo in advertising, you can use it to identify sections/modes/content/etc. in your app without issue. |
|
Feb 21 |
comment |
How do I find all questions/answers per a tag? Only questions have tags, if you want answers to tagged questions you have to come at them from a question direction. For /questions or /search you can add question.answers to your filter to get the answers along with the question (as they're not included in the default filter). .total likewise isn't included by default. Maximum pagesize is 100, if you need more than 100 results you have to make multiple requests. |
|
Jan 29 |
comment |
Get my profile information after authentication @PiyushSardana The key is required when using an access_token (the console appends it's own key to requests when you "Get Token" with it [for GET's, POSTs require you enter your app's key & a paired access_token into the console]). For non-authenticated requests all it gets you is a higher # of requests per day. |
|
Dec 11 |
comment |
API documentation console unsuccessfully tries to load MiniProfiler results @DanielLidström I just disabled miniprofiler on production for the API, there's no "user session" so there's no reason to push down results. Nothing fancy. |
|
Sep 19 |
comment |
HTTP 400 “Bad Request” while using “access_token” in request Url George's answer is probably correct, making an http request with an access_token should error. The response body should have something like {
error_id: 406,
error_name: "access_token_compromised",
error_message: "Access token sent over non-HTTPS request, it has been invalidated"
} in it. |
|
Sep 10 |
comment |
Do the terms “key” and “access_token” refer to the same thing? @hippietrail - you get access tokens by kicking off an authentication flow. A user does have to grant them explicitly, you could store them in a database or something once you have them but you can't create them without a user's approval. |
|
Aug 14 |
comment |
When will the “site” field be absent from an “inbox_item”? @Alex - there's an error if you're using the /users/{id}/inbox method because the site no longer exists, but if you're using /inbox there's no error because you're not querying a specific site. |
|
Jul 30 |
comment |
Official Stack Exchange Test App @systempuntoout no, the API console is not authorized to write (too open to abuse). It'll get a little cleaner as the beta gets closer to ending, but for now it basically just documents the available parameters on write methods. |
|
Jul 25 |
comment |
The migrated predicate on advanced_search seems underachieving @Gilles - we've built and indexes are finished updating, everything should be good now. |
|
Jul 25 |
comment |
The migrated predicate on advanced_search seems underachieving @Gilles I believe that will be fixed in the next build + a re-index. API search indexes are a bit in flux at the moment... |
|
Jul 12 |
comment |
StackAsk - Ask questions from iPhone and iPad - Now free on App Store! @Dynamic a limited write API is under development. When it'll be released is uncertain. |
|
Jun 18 |
comment |
/posts/{id}/revisions breaks for posts with [tag:*] content I think this is actually a bug with [tag:*] syntax, a fix will be out once I can disentangle this... |
|
May 22 |
comment |
Deprecating API V1.x @Jeff - nagging has been going on, and will continue. |
|
Apr 30 |
comment |
/me API endpoint returning 500 error Well, yes this is a bug. It should be giving you a more sensible error, but it looks like you're sending ['access_token'] instead access_token; as in, you're actually sending [, ', and ]. |
|
Apr 26 |
comment |
“client_id not provided” when trying to obtain an access_token @KristianGlass no worries, just post it as an answer so others can get themselves out of similar predicaments. |
|
Apr 26 |
comment |
“client_id not provided” when trying to obtain an access_token Hmmm, that's really weird. That error message is literally behind a "client_id != null" check, I'll dig into the traffic logs and see if anything stands out. Random thought, can you control the serialization order? If so, move client_id to the very front of the POST body; if the error message changes/goes-away that'd be indicative of an encoding error somewhere. |
|
Apr 24 |
comment |
Separate Request Quotas for Authorized [app]s @systempuntoout - you should use one of your (as in, your user's) app "slots". Basically, as the app author authenticate a no_expiry token and use it. |
|
Apr 5 |
comment |
Inbox unread since parameter not working No, it's a bug in our code; I think the since parameter is working... just sometimes bogus things are getting pulled out of the cache, so that the since code isn't even running. |
|
Apr 5 |
comment |
Inbox unread since parameter not working Hmm, I bet this is a caching bug. Should have an update/fix shortly. |
|
Apr 5 |
comment |
Registering app for API 2.0 key without Oauth domain @George - fair enough, wasn't aware of the signing differences. |
