409 reputation
310
bio website plus.google.com/…
location Toronto, Canada
age 94
visits member for 2 years, 3 months
seen Oct 15 '12 at 15:33

Email: me AT marvinp DOT ca


Mar
8
comment Anybody up for terminal frontends
I'm not sure what functionality you're looking for from this terminal app, but I've done two myself -- here and here. The first one just gives you access to the suggested edits queue and the second one is akin to a super filter for SE questions. Have fun :)
Mar
3
comment Add close-vote information to the questions object
@PeeHaa I believe write access will be allowed in a future version of the API, not just yet.
Feb
9
comment Suggested Edits Queue for Mere Mortals
@oers Unfortunately no, I haven't added proxy support. But the source code is available so you're welcome to have at it :)
Feb
1
comment Add last_access_date field to the shallow_user object
@Jonathan. From what I understand of filters (in this context), you enable or disable only what you need, but on the backend, all those objects are pulled no matter what - filters only prevent them from being sent to you (thus conserving bandwidth). That's probably the reason they went with the shallow_user object in the first place. Then again, this could all be heresay :)
Feb
1
comment Add last_access_date field to the shallow_user object
@Jonathan. Right, you meant if a /search query returned the full user object - yeah I missed that part. I don't think what you're asking for will be feasible. To be honest, I don't see them even adding the field I wanted. I don't know how their stuff is structured in the backend, but I can imagine that it will be very expensive to return a full user object with each (relevant) query.
Feb
1
comment Add last_access_date field to the shallow_user object
@Jonathan. There's a good chance I've missed the point so bare with me :) Ignore the shallow_user object for now. How would I retrieve the full user object in a /search query using filters?
Jan
31
comment Accept rate not available in the 2.0 API
Thanks Kevin. So, do I get [bug] credit for this one :)
Jan
31
comment Accept rate not available in the 2.0 API
@Jonathan. The reason I specifically mentioned wanting it in the shallow_user object is because question queries (among many others) also include the shallow_user, and my thinking was that it saves another API call to the full user object just to retrieve the accept_rate. And yes, I understand the above query returns a full user object, it was only meant to be an example :)
Jan
31
comment Unable to sort /search results by creation_date
Thanks again Kevin, that took care of it.
Jan
30
comment Update the default filter editor to use the API key
Thanks Kevin, that took care of it. On a related note, I guess it isn't a big deal that the private key=U4DMV... is exposed since the restriction is IP based in any case, right?