Skip to content
This repository has been archived by the owner on Jan 31, 2024. It is now read-only.

spec: require user consent for apps to send data to the chat #33

Closed
1 task
WofWca opened this issue Feb 7, 2023 · 1 comment
Closed
1 task

spec: require user consent for apps to send data to the chat #33

WofWca opened this issue Feb 7, 2023 · 1 comment
Labels
api-change-move-to-forum this issue proposes an api change which belong in the forum, so it should be summarised an put there

Comments

@WofWca
Copy link
Contributor

WofWca commented Feb 7, 2023

Something like "apps MUST NOT be allowed to send any data to the chat (sendUpdate()) unless the user has given explicit consent to that". The prompt should also state that the app may share ANYTHING they do inside the app to the chat, so if they don't trust the app, they better not allow it to send data, or not input anything sensitive there (that also makes me think if users should be warned about not putting sensitive stuff in the apps BEFORE they can launch it).

It's because:

  • Apps can potentially used for some fingerprinting. E.g. a stranger sends you an app, you open it and it immediately sends out info about your system to the stranger.
  • Some users may put sensitive stuff inside the apps, not expecting the app to share that info with the chat (e.g. "type your social security number to know who you were in your past life").

The more general idea behind all of this is to tell the users what they should expect from the apps. E.g. they would want to know that apps cannot communicate with the internet directly. Or that they already know it, and assume wrong things based on this (like that apps cannot communicate with the chat either).

TODO:

  • specify how the consent must be given - like a global option for all apps, or per-app, only when they try to send data for the first time, or each time an app sends a message - with full contents of the message, or somethings else.
@Simon-Laux Simon-Laux added the api-change-move-to-forum this issue proposes an api change which belong in the forum, so it should be summarised an put there label Sep 21, 2023
@WofWca
Copy link
Contributor Author

WofWca commented Sep 22, 2023

@WofWca WofWca closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api-change-move-to-forum this issue proposes an api change which belong in the forum, so it should be summarised an put there
Projects
None yet
Development

No branches or pull requests

2 participants