Skip to content
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

Replacement for isshiki reports #4367

Closed
nonamethanks opened this issue Mar 28, 2020 · 1 comment
Closed

Replacement for isshiki reports #4367

nonamethanks opened this issue Mar 28, 2020 · 1 comment
Labels
Services Issues related to services maintained in other repositories.

Comments

@nonamethanks
Copy link
Member

nonamethanks commented Mar 28, 2020

Brought up first on discord: most isshiki reports are now dead. It's probably not a good idea to just create new ones in the same place for various reasons, including privilege issues (downvote and flag reports shouldn't be visible to normal users), accessibility and the fact that they were pretty raw outputs.

It would be useful to have this kind of report integrated into the site, something like a /statistics or /reports endpoint.
We currently have the amazing user report by @BrokenEagle, it's been a prototype for three years now and it is a great example of what "official" statistics could look like. Due to the fact that it's processed externally however, that report has been only generated monthly so far. There's also forum limitations because large tables don't scale well visually, on any but the bigger resolutions.

Implementing something similar serverside would have the advantage of being available for shorter time deltas (though weekly, like isshiki was, is well enough), it could be generated much faster, as it would not be bound on api requests, and as already mentioned the access to more "private" reports like up/downvotes, flags and similar could be controlled through already existing mechanisms.

This is related to issue #4217, or rather that issue would be a subset of this if such a thing is implemented.

@BrokenEagle BrokenEagle added the Services Issues related to services maintained in other repositories. label Apr 7, 2020
@nonamethanks
Copy link
Member Author

Fixed by 203067b.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Services Issues related to services maintained in other repositories.
Projects
None yet
Development

No branches or pull requests

2 participants