Reputation
3,806
Next tag badge:
87/100 score
33/20 answers
Badges
2 11 30
Impact
~9k people reached

23h
reviewed Reject oauth tag wiki excerpt
May
1
reviewed Approve Android app for Stack Overflow
Apr
10
reviewed No Action Needed Stack Overflow Extras (SOX)
Apr
7
reviewed No Action Needed StackExchange MathJax Editing Improvements
Mar
15
reviewed Reject discussion tag wiki excerpt
Mar
15
reviewed Reject discussion tag wiki
Mar
15
reviewed Reject app tag wiki excerpt
Mar
15
reviewed Reject app tag wiki
Mar
15
reviewed Reject StinkingBadges - Track your progress towards long-term badges
Mar
14
reviewed Reject StinkingBadges - Track your progress towards long-term badges
Feb
26
reviewed Approve bounty tag wiki
Feb
26
reviewed Approve bounty tag wiki excerpt
Feb
26
reviewed Reject Application Key and AccessToken are not working for Stack Exchange API?
Feb
26
reviewed Close `/me/associated` gives ambiguous/wrong response
Feb
26
reviewed Close How to stimulate `backoff`?
Feb
23
reviewed Approve Why do you need to specify a site when getting the inbox?
Feb
19
awarded  Favorite Question
Feb
17
comment Why do you need to specify a site when getting the inbox?
The only reason the route exists is so that applications which always append site don't get an error trying to invoke the network-based /inbox, which rejects that parameter. Laziness is literally the only purpose for this route, and people should always use /inbox.
Feb
17
comment Why do you need to specify a site when getting the inbox?
Those are network routes, though. This exists explicitly as a site-specific route that duplicates /inbox's functionality. I don't think there's a good reason for the route to exist in the first place, but the behaviour is at least intentional.
Jan
21
reviewed Approve app tag wiki excerpt