Idea:
Implement per-key access permissions (simple on/off) in order to control which types of data are available to be accessed personal user fields/data.
EDIT: e.g. USER / Available fields: networth, bazaar, display, inventory, hof, travel, events, messages, education, medals, honors, notifications, personalstats, workstats, crimes, icons, cooldowns, money, perks, battlestats, bars, profile, basic, attacks, attacksfull, revives, revivesfull, stocks, properties, jobpoints, merits, refills, discord, gym, timestamp
One can `allow` a given access key to have access to the `root` (User) field plus: `bars`, `profile`, `cooldowns`, `refills`.
Goal:
Allow for greater privacy whilst giving space for value-added tools through API implementations.
Concept:
Each player is able to have more than one api access key (a limit can be imposed of course, even a small limit like 2 or 3).
A player has the ability to manage which types of data/fields a given api key has access to.
E.g. player statistics: one can choose to disclose 'bars' and 'cooldowns' but block access to all other fields (other than parent).
Benefits:
Avoid the downside of sharing one's API key with 3rd parties (allowing access to ALL data).
Be in control of what data is gathered.
Tools can get the exact data they need without having access to more private data.
Tool developers and users trust in each other is increased. In turn, spurring more development with more players willing to give access of certain (and only some) data.
Impact:
Depending on implementation, number of API calls may increase as the total amount of calls allowed for a single player.
Say: if a given player has 2 (two) api access keys and both are being used by external programmes, currently the max calls/sec are per key. This effectively has the potential to double the number of calls being made to the api endpoint.
Apologies I'm on a phone writting this, is the concept clear and why this benefits the community in the sense that it allows players to control which data stays private? (In turn opening up some data to a given end to tools/developers).
EDIT: typos and syntax. minor additions.
H+
Implement per-key access permissions (simple on/off) in order to control which types of data are available to be accessed personal user fields/data.
EDIT: e.g. USER / Available fields: networth, bazaar, display, inventory, hof, travel, events, messages, education, medals, honors, notifications, personalstats, workstats, crimes, icons, cooldowns, money, perks, battlestats, bars, profile, basic, attacks, attacksfull, revives, revivesfull, stocks, properties, jobpoints, merits, refills, discord, gym, timestamp
One can `allow` a given access key to have access to the `root` (User) field plus: `bars`, `profile`, `cooldowns`, `refills`.
Goal:
Allow for greater privacy whilst giving space for value-added tools through API implementations.
Concept:
Each player is able to have more than one api access key (a limit can be imposed of course, even a small limit like 2 or 3).
A player has the ability to manage which types of data/fields a given api key has access to.
E.g. player statistics: one can choose to disclose 'bars' and 'cooldowns' but block access to all other fields (other than parent).
Benefits:
Avoid the downside of sharing one's API key with 3rd parties (allowing access to ALL data).
Be in control of what data is gathered.
Tools can get the exact data they need without having access to more private data.
Tool developers and users trust in each other is increased. In turn, spurring more development with more players willing to give access of certain (and only some) data.
Impact:
Depending on implementation, number of API calls may increase as the total amount of calls allowed for a single player.
Say: if a given player has 2 (two) api access keys and both are being used by external programmes, currently the max calls/sec are per key. This effectively has the potential to double the number of calls being made to the api endpoint.
Apologies I'm on a phone writting this, is the concept clear and why this benefits the community in the sense that it allows players to control which data stays private? (In turn opening up some data to a given end to tools/developers).
EDIT: typos and syntax. minor additions.
H+