nodeSolidServer / nodeSolidServer/node-solid-server
acl:trustedApp limits usefulness of decentralized social apps
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
As was already pointed out in https://github.com/nodeSolidServer/node-solid-server/issues/1672#issuecomment-1059452233, when somebody has shared their data hosted on NSS with me, I can't access those data with a web app of my choice, I have to use the same web app they used.
This limits usefulness of otherwise interoperable apps that work on top of any kind of social non-public data.
In comparison, CSS doesn't use acl:trustedApp, and I can use an app of my choice to access the data shared with me.
Has this been discussed already? Is this a desired behaviour? It looks to me like it's an unfortunate side effect, since it limits one of goals of Solid Project[^personal]: People can choose which app they want to use.
[^personal]: as I understand it
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked issue 1672 comment and the behavior of acl:trustedApp in node-solid-server, then compare it with the CSS behavior described here. Clarify whether this restriction is intended and define the expected access behavior before identifying the relevant ACL implementation and validation needed for a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100