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

Email: me AT marvinp DOT ca


Jul
2
awarded  Curious
Jan
23
awarded  Yearling
Jan
23
awarded  Yearling
Mar
12
awarded  Enthusiast
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
awarded  Commentator
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.
Mar
2
asked Add close-vote information to the questions object
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
7
revised Suggested Edits Queue for Mere Mortals
deleted 127 characters in body
Feb
7
asked Suggested Edits Queue for Mere Mortals
Feb
2
awarded  Citizen Patrol
Feb
2
answered Is there a limit of API requests?
Feb
1
accepted Add last_access_date field to the shallow_user object
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?
Feb
1
asked Add last_access_date field to the shallow_user object
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
accepted Accept rate not available in the 2.0 API