Timeline for How to get a list of all StackExchange employees?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7, 2018 at 7:44 | history | edited | Gaurang Tandon | CC BY-SA 4.0 |
added 18 characters in body
|
| Jul 6, 2018 at 6:59 | comment | added | Gaurang Tandon | @BrockAdams Ah, I see. I missed the part about it being the same quota per IP. Hmm, I think we can remove it then. I will check it once and update results accordingly. Thanks for the heads up :D | |
| Jul 6, 2018 at 6:52 | comment | added | Brock Adams | Oh, sorry. I somehow overlooked the filter in the script you linked. And IIRC that access token thing will only help you if your other API calls, from the same IP address, use a token too, but one for a different app. | |
| Jul 6, 2018 at 6:35 | comment | added | Gaurang Tandon |
@BrockAdams "20 minutes is not so bad if ..." alright. "Why are you sending an access_token?" Without an access token, all apps - which are without an access token - sending requests to SE API are dumped into the same quota. Considering that I am using up nearly 40% of that quota in one go (almost 4000 API calls), I thought getting a separate access token for my app would be better, and ensure uninterrupted access to the API. I read that here. Also, I am already using a filter=!*MxJcsv91Tcz6yRH ;)
|
|
| Jul 6, 2018 at 6:02 | comment | added | Brock Adams |
That's good and 20 minutes is not so bad if you have a chron job doing it during off hours and store it to a public file (not localStorage). Why are you sending an access_token? That should not be needed. Also, if you use a filter to cut out unneeded fields, it will run faster. (See this Q&A also.)
|
|
| Jul 6, 2018 at 5:42 | comment | added | Gaurang Tandon | @user43888 I updated the post. Hope you don't mind the method 2 ;P | |
| Jul 6, 2018 at 5:42 | comment | added | Gaurang Tandon | @BrockAdams I have updated the post based on the method you posted. It gave the exact results as expected, however it took nearly 20 minutes on my slow internet :( | |
| Jul 6, 2018 at 5:40 | history | edited | Gaurang Tandon | CC BY-SA 4.0 |
positive updates :D
|
| Jul 5, 2018 at 11:41 | comment | added | user43888 | The comment by Brock Adams describes what my Google Apps Script does. Once a a week, it scrapes of all MetaSE users, recording their is_employee status. Once a day, it refreshes the list by re-checking the users last known as employees. | |
| Jul 5, 2018 at 6:15 | comment | added | Brock Adams | By your math, it could take as little as 3 minutes to sift through every user on MSE. And who is/isn't an employee should change rather rarely. So, you should be caching this information, heavily, anyway. ... Go ahead and fetch all users and store the employee ids, in JSON format in a public file that your script will fetch. You need only update the file every 2-3 weeks, and you could set a cron job to do that. | |
| Jul 5, 2018 at 5:51 | history | edited | Gaurang Tandon | CC BY-SA 4.0 |
added 653 characters in body
|
| Jul 5, 2018 at 5:41 | history | answered | Gaurang Tandon | CC BY-SA 4.0 |