-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog on Pro hitting 300,000 requests and noting design of service to prompt publication of previously private requests is working #1280
Comments
Or for another angle I've just noticed we've recently crossed 100,000 requests previously private are now public:
Couple of key points off the top of my head…
|
Yes. Many of the 25% of embargoed requests will still be within their initial, default, 3 month embargo period. That statistic would presumably be even more impressive/reassuring if requests made within the last 3 months were excluded. I wonder if embargo extension is common or rare?
Theoretically "community", but in practice lots of the effort comes from a small number of people, many of whom are, or have been, WDTK volunteers. We know this kind of thing happens elsewhere eg. on Wikipedia but it's worth noting. See also: |
As Richard says, if the ones that are still embargoed are more recent, it could be that this would trend towards 100% if we were to turn new requests off for a bit. In terms of commercial use, I've noticed this company use pro, (I'm guessing to gather the data for some of their products): https://neosypher.com/ |
We could mention things we're considering doing to encourage publication of even more Pro requests/responses: |
Flagging this for me to look at, as we should hit the 200k mark very soon (IIRC was just over 196k last time I checked). |
We've made it! I'll get on this. |
The alternative is to hang fire until 250,000 - shouldn't take that long. |
Helen mentioned that we have hit this milestone for Pro now so it's worth investigating writing this post in the next cycle |
I think we hit 300,000 this week... |
This has been wrapped into the blog post drafted at https://docs.google.com/document/d/1DJoloEXQNC6vyGSagPK-6mlkb2HIJW2-wSDvu1W1x0s/edit#bookmark=id.7c4fzoyyzx75 |
A suggested by @garethrees at 100k, relevant for 200,000.
We should mark this milestone when it comes by blogging to highlight good use of the service.
The text was updated successfully, but these errors were encountered: