-
-
Notifications
You must be signed in to change notification settings - Fork 414
Display registered addons on BStats #8237
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
base: dev/feature
Are you sure you want to change the base?
Conversation
I disagree with this addition. If an addon wants it's data to be on bStats it'll use it's own bStats. This data does not need to be forcibly public by default. |
Imo this is something should be discussed further, as not only this could be a privacy concern as there’s no way to toggle this off, this also opens up to “addon name spoofing” where this data can be manipulated and misused to display inappropriate content. At least I think adding a config option for this (defaults to 'true') lets the user to control whether they agree to contribute their addon list to this chart. |
Honestly, there's nothing really stopping people from just forking Skript and adding random things to bstats. So there will always be a misuse regardless if this is added or not.
I don't understand how this would be a privacy concern. All it does is log what addons are used, not what/which servers use the addons. |
This isn't a worry imo. Bstats already provides filtering capabilities that make 'inappropriate names' a moot point. I think the opt-out is a good idea, though. |
Or not have the problematic, not needed feature, using common sense. |
Problem
Accurate information about what addons are in use could assist in making decisions about api changes and what challenges users face that they use addons to overcome.
Solution
Adds a pie chart to BStats that displays the names of the registered addons on each server. An example is live on the skript bstats page: https://bstats.org/plugin/bukkit/Skript/722.
Possible downsides:
Possible upsides:
Testing Completed
N/A
Supporting Information
Currently based on feature but can be changed to patch after 2.13.
Completes: none
Related: none