-
Notifications
You must be signed in to change notification settings - Fork 32
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
Reword help about data sharing #73
Conversation
Make clear the data is shared with selected applications and link to /sessions for more information (should be done with #72).
Will show the application name after implemented in #72.
One issue with this new wording is that it sounds like the data is only made available for those applications listed under |
One important piece of information that was missing is that, for some providers, access tokens are saved (and provided to applications) as well. For example, we need the OAuth token and token secret for Wikidata to be able to gain write access. In case of OAuth, this isn't an issue since they can only be used in combination with an (if I understand correctly, your unique) application token. However, in the easydb integration, the token is also saved since there are plans to use this integration read/write in easydb as well. Those are not application-specific and could, in theory, be abused. (However, I will research if this is actually the case, and even if it is, we only provide access to trusted applications, so it shouldn't be an issue, right?) Edit regarding easydb: Authenticated session tokens will expire after some (undefined) amount of time. So yes, this token can probably be used to access the easydb instance - that's why we're saving it. |
Yes. Or show the application list as part of /help. |
I merge it into dev already, but I'd still like to have @nichtich look through before we release the new version. |
Make clear the data is shared with selected applications and link to
/sessions
for more information (should be done with #72).