You need to join the Votes row to your per site User.id
The from and where clause needs to become this:
from posts p
inner join votes v on v.PostId = p.id
and v.VoteTypeId = 5
inner join posts q on q.id = coalesce(p.parentid, p.id)
inner join users pu on pu.id = v.userid -- your favorites
where pu.accountid = '+ cast(@accountid as nvarchar) + ';'...
This is not an official API, but it is not too hard to simulate the login via OpenID and use the session to start executing a query, poll the job that executes it and retrieve the results in the end. I do most of my Stack Exchange development work in Java, but it should be easy to port to other languages even if you don't know Java. I'm using fairly standard ...
The simplest solution is to click on your user profile, and then "Select your next badge". If not obtained yet, Proofreader will be in the collection and there is a bar that tracks your progress (e.g. below).
Here is a SEDE query which attempts to list reputation on 'Legendary Day' for all users who have the badge. It runs faster than I expected on this site, but we only have 15 Legendary users here:
# User Legendary Day Rep
1 Jeff Atwood 2010-03-23 13:17:...
I plead guilty ...
Since Peer Pressure and Disciplined badges are awarded pretty soon after deletion, you can (if the posts are later undeleted) check the timestamps of the badge with the post history timestamps. Here is a SEDE query where I only count the instances where the owner of the post deleted and undeleted it. They might have done so because they ...
I edited the query, eliminating the condition that the date of creation of the review task result must be less than the date of the last edition of the post.
I also reduced the selected columns, and added the link to the timeline of the post. Finally, I limited the results to 500, resulting in the following query:
SELECT TOP 500
Unfortunately, you can't. It seems like review timestamps are deliberately truncated before they enter SEDE, just like votes: Why is vote time missing in the SE data dump and SEDE?. I'll update the Database schema documentation for the public data dump and SEDE to reflect this. Note that the ReviewTaskResults table doesn't include the user who made the ...
You don't need SEDE for this, the regular search is perfectly capable of this.
user:me is:a score:1 -[feature-request]
For me, that search query produces the following results:
Of course, it can be done in SEDE and it's a nice exercise. Here are some pointers:
Join the Posts table with itself, the ParentId of the answer is the Id of the question
The decrease of moderation activities might actually be a good thing in your case. According to this metasmoke report, Drupal Answers saw much less spam in 2019 than in 2018:
I've written a SEDE query comparing the number of questions and answers networkwide, to answer How can we find the fastest growing sites within the last year?. It's a bit of overkill ...
When a question got 5 close votes it ist closed and the reason is shown below, but as long as there are not enough votes, you can savely use the close link. It will display a list of reasons first, why you "want" to close it too. You don't have to choose, but you see the pending reasons as a small number beneath each option.
The main problem with SEDE is that data is only updated once a week, on Sunday morning. So 'active during the last week' is going to be tough (depending on when you run the query). That said, this SEDE query is close to what you're looking for. You'll need your user ID and a date before last Sunday, e.g. 2019-12-01:
You are comparing apples and oranges.
In the first query you take the creationdate of the post to group on the total number of comments for a post that was created in a certain year.
In the second query you take the creationdate of the comment to group the total number of comments created each year.
I can totally write comments today on a post that was ...
Unfortunately, this isn't possible. That field is only present (or at least populated in the Stack Overflow database and not on the other sites). So SEDE won't be able to give you these results.
There's a Database schema documentation for the public data dump and SEDE which tells you which fields are available, but Job Title isn't one of them.