Workflow for home pod actions trigged at remote pods

In the SolidOS Web App world, the users is typically looking at or focussing on particular thing in a given pod, while running web app code which is either

0. running a native app like the Data Kitchen

1. in the domain of that pod (the basic databrowser workflow) which is in fact the user's pod

2. running a web app in a specific domain of its own (like podbrowser.inrupt.com), or possibly

3. in a databrowser app from their own pod which has led them to this different pod through links

Suppose they want to do an action on the thing they are looking at, like liking it or bookmarking it or adding someone to their contacts, chat with them, and so on. At the moment the code just tries to add a bookmark to the user's bookmarks, and often fails except in case 4. One can imagine workflows to allow this to work in cases 1 2 and 3

a) Using the web app permissions system to give the place they are permission.

b) Being redirected to an app like a "Liking" app or a Address Book app which they have already given permission

c) Being redirected back to their own pod data browser where there will be no problem

These redirects could be opening of a new browser tab, or possibly an iframe or pop-up. One would certainly not want to loose the original browser context.

We certainly want to keep the workflow very simple in the native app and local pod cases -- cases 0 and 1 should allow the heart shape to be clicked on and turn pink (or whatever) instantly with no redirection.

No files, tests, or entry points are named. Start by locating the current bookmark or heart-action flow and its permission handling, then clarify which redirect or local workflow should be implemented for cases 0–3; done requires an agreed design that preserves the original browser context.