I'm implementing it now (as you noticed) and have run into an interesting issue. The wording of 3b86 suggests that the intents are distinct between users. That is, the end user inputs their handle, the handle is queried via webfinger, and supported Intents are returned.

However, the intents themselves don't really distinguish between users.

So I could have a localStorage session with multiple handles registered (e.g. julian@activitypub.space, nodebb@fosstodon.org), etc. — this works fine.

But if I had two handles with the same domain, alice@example.social and bob@example.social, then my intents can't be targeted, can they... I just fire off the request (or rather, I have the end user's browser navigate) to the intent URL and whatever account is logged in will be the actor.

Did I miss something, or was there a way to distinguish actors in Activity Intents?

P.S. I find it highly amusing that you had to click through to activitypub.space to read my whole post, but because I don't support Activity Intents yet, you can't reply properly <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f923.png?v=a8002752e25" title="" />