network profile
| bio | website | stackexchange.com/users/… |
|---|---|---|
| location | Paris, France | |
| age | 33 | |
| visits | member for | 2 years, 5 months |
| seen | May 17 at 19:51 | |
| stats | profile views | 8 |
Moderator♦ pro tempore on French Language and Usage and Computer Science. I'm also a unix amateur, and a developer with a computer science background and security leanings by trade.
Interested in embedded systems? Join the Embedded Programming and Design proposal!
Avatar picture slightly adapted from a photo by Luridiformis (Zonda Grattus) (except where I use another picture).
|
Apr 29 |
comment |
TIARA - a tool for enhancing SE beauty Why show only closed questions? Downvoted questions might need closing, whereas I don't know why downvoted closed questions would be different from non-downvoted closed questions. |
|
Feb 23 |
revised |
Format a list of questions updated example link |
|
Dec 1 |
awarded | Yearling |
|
Nov 21 |
awarded | Commentator |
|
Oct 26 |
comment |
Prefered way to retrieve all search results See the question: if there's a deleted result, it's counted in the 100. I guess deleted results are eliminated late in the chain. I thought …/page=2 just after …/page=1 was counted differently, but I can't find a reference to that now, I might have imagined it or confused with some other site's API. |
|
Oct 26 |
comment |
Prefered way to retrieve all search results Ok, this technique works to avoid skipping an item in the middle. It assumes there aren't 100 questions with the same date (this is unlikely to happen naturally, but what about a mass import?). Your termination condition is wrong, there can be less than 100 results at any time. This technique is rather costly; as I understand it, querying page=2 after page=1 is cheaper in the backend (because the data is already sitting in some cache, I guess), and from the user's point of view it's cheaper because it doesn't count as a separate request against the API usage quota. |
|
Sep 22 |
comment |
Draft Specification for API v2.0 For the paging issue, a cumbersome workaround seems to exist (I haven't tried it). |
|
Sep 17 |
asked | Scrape the site list, show sites sorted by answer ratio |
|
Sep 17 |
awarded | Citizen Patrol |
|
Sep 10 |
awarded | Autobiographer |
|
Sep 6 |
awarded | Talkative |
|
Sep 6 |
awarded | Organizer |
|
Sep 6 |
revised |
Hacks for JL&U Site added tags |
|
Sep 5 |
comment |
Stack Overflow UI Translation via Greasemonkey Follow-up on Meta SO |
|
Sep 5 |
suggested | suggested edit on Hacks for JL&U Site |
|
May 31 |
comment |
Insert direct documentation links in to answers Related: Editor buttons for injecting documentation links |
|
Apr 22 |
comment |
Stack Exchange Side-By-Side Edit and Preview Nice, if your screen is large enough. Bug: I can't see the edit summary in side-by-side mode (Chrome 11.0.696.48). I can return to normal mode to fill it in, but that makes it more likely that I'll forget to enter a summary. Feature request: being able to see the question (with scrolling). |
|
Feb 28 |
comment |
Prefered way to retrieve all search results Er, so, does that mean I should start again from the beginning if I see a deleted item? |
|
Feb 28 |
asked | Format a list of questions |
|
Feb 28 |
comment |
API search page size limit mismatch Weirdly, api.stackoverflow.com/1.1/search?tagged=c&pagesize=100 returns only 99 questions. Going down, api.stackoverflow.com/1.1/search?tagged=c&pagesize=10 returns only the same 9 questions as api.stackoverflow.com/1.1/search?tagged=c&pagesize=9 . Is this by design (I can think of legitimate reasons such as a deleted question)? This makes me wonder how to get all the results of a search. |
