-
Notifications
You must be signed in to change notification settings - Fork 2
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
Kind of scary permissions screen #8
Comments
@weex Thank you for reporting! AFAIK we don't have control over the permission screen you've seen, unfortunately. It's served directly by the Solid Pod Server when you use the app for the first time. This looks like the screen which is served by Node Solid Server (https://solidcommunity.net, was it?) which has rather terrible UX in general. 😆 If there is a way to limit the items on the screen or change selected defaults, i don't know it.
That sounds very broad indeed. There is Solid Interoperability Panel working on a new specification. On first reading it sounded complicated to me and i haven't studied it in detail, but it should allow for finer permission settings. So hopefully the future is brighter; and once again we can blame the issue on the immaturity of the Solid technology. 😝 |
Yes @mrkvon, solidcommunity.net I believe. Maybe if we want to run a pod later we can fix that screen... Or create an issue upstream if there isn't one. One thing I like about text is that it's trivial to update most of the time. But yeah some of these issues are more making notes for the curious vs. expecting a fix. |
We could make this easier for the first-time users, by telling them what to expect before they log in for the first time. Otherwise we can't do much, since this is a UX issue of https://github.com/nodeSolidServer/node-solid-server, which is generally - to put it mildly - UI-challenged 🙂 |
When running locally with
yarn start
, I saw this screen which is a lot of text to read and would probably lose a lot of users. In particular the first checkbox with "Read all documents in the Pod" sounds like a lot. Even as someone who I'm pretty sure has no documents on the pod, I get nervous when confronted with such broad statements.Potential solution(s):
Is there a way to request fewer permissions or to display a simpler view of the situation.
.
The text was updated successfully, but these errors were encountered: