You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If app can be configured through uri, by providing storage root, user's webid, etc, then that can serve as an api for integrating, launching the app from many contexts with desired configuration.
Thanks for your work.
The text was updated successfully, but these errors were encountered:
With multiple recipe lists or cookbooks, it would be useful to specify which to open. This could probably be done with the same query param as for a recipe.
If this is possible, then I think specifying the storage root would not be necessary - if a user has multiple storage roots or wishes to open a cookbook not in their storage root, they would already be able to do so.
I see two use cases for specifying webid in the Uri:
being able to derive a storage root for a different user, e.g. I want to see someone else's cookbook. This relates to View and follow my friends recipes #25 My guess is that this is better implemented through the ability to specify a cookbook to open, and it would be the linking application's responsibility to discover the user's cookbook and deep link straight to it.
specifying the account to log in with. As long as Solid-OIDC is the dominant authentication mechanism, I'm not sure how useful this would be because user input is still required. The most that can be achieved is streamlined autocomplete rather than full automation? Efforts with FedCM might change this, but Umai would then need to be compatible with FedCM rather than providing an custom means of specifying a webid.
Yeah, I'm still not sure about the storage root or webId params, but maybe I could implement a generic way of deep linking and the app would perform client-site redirection to the appropriate route. For example app.com?view=https://myrecipes.com/ramen#it would redirect to app.com/recipes/ramen?id=https://myrecipes.com/ramen#it, etc.
If app can be configured through uri, by providing storage root, user's webid, etc, then that can serve as an api for integrating, launching the app from many contexts with desired configuration.
Thanks for your work.
The text was updated successfully, but these errors were encountered: