Skip to content
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

Enable opening resource with other apps (open-with) #47

Open
josephguillaume opened this issue Oct 30, 2024 · 2 comments
Open

Enable opening resource with other apps (open-with) #47

josephguillaume opened this issue Oct 30, 2024 · 2 comments
Labels
needs refinement Not ready for development, due to open questions or obscurities user story A description of what a user wants to achieve with the application

Comments

@josephguillaume
Copy link
Contributor

Particularly in pod mode, if I navigate to a resource I want to either automatically redirect to a preferred app or be offered the opportunity to open the resource in another app.

In the context of SAI, which operates on the principle of least privilege, each individual app is limited in what it can access. In pod mode, PodOS would presumably have universal access to the pod and therefore could play an important role in enabling follow your nose between apps.
solid/data-interoperability-panel#325

If another user navigates to a resource on my pod, I also want to provide them with a useful default view of the resource, but I would want to offer them to open in their preferred app. With SAI and the principle of least privilege, my pod browser would be unlikely to have access to that information and my pod browser would instead offer to have the resource opened in their authorisation agent.

@josephguillaume
Copy link
Contributor Author

If in pod mode and logged in, the pod browser would load applicable app registrations for the resource and provide a UI element to select the app to open with.

If there are no app registrations, then an external set could be used or a UI provided to edit/add app registrations.

@josephguillaume
Copy link
Contributor Author

If SAI is supported, PodOS would also need to either be the user's registered authorisation agent and allow granting access to the app to be used, or be able to direct the user to their authorisation agent to complete this operation.

If PodOS is not the user's authorisation agent, a UI element is provided to open the resource with the user's authorisation agent.
This is similar to how following someone when on a different Mastodon server involves first returning to your own home server.

@angelo-v angelo-v added user story A description of what a user wants to achieve with the application needs refinement Not ready for development, due to open questions or obscurities labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs refinement Not ready for development, due to open questions or obscurities user story A description of what a user wants to achieve with the application
Projects
None yet
Development

No branches or pull requests

2 participants