Mashing up Multiple WebIDs and Pods
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Tim Berners-Lee @timbl Aug 26 14:17 said in gitter/solid/chat
@joepio Thanks for the link to all the UI material and ideas.
I’d like us to design interfaces to our sold stuff, whatatever pods it may be on. I’d like to be able to by default look at stuff in four pods, and at each point, say looking at photo albums or photos, be able to turn on and off different pods from the merged view.
Like layers on a map.
He reiterated similar ideas in the SolidOS meeting on 2021-09-08 and also mentioned a related feature - the ability to use multiple identities simultaneously while keeping the identities hidden. If I'm understanding correctly, combining this idea with the one above would mean I could be looking at a mashup of my photos from my work and play IDs without anyone but me knowing that I am associated with both IDs.
My thoughts are that these kinds of things are most easily doable by authorizing an ID for multiple pods - if my workID Pod and my playID Pod both assign the homeID as authorized to read photos I'm all set after one login. But it might also be worth considering the longer route for SolidOS - let all WebIDs operate simultaneously. If I try to get resource X with WebID Y and that doesn't work, the app tries WebID Z or offers a new login prompt.
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
No files, tests, or entry points are named. Start by identifying the existing WebID, pod authorization, and login flows; completion requires an agreed design and acceptance criteria for merged views and simultaneous identities before implementation can be judged done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100