Where does ELK.ZONE fit in to the "make discovery actionable" research?

[bumblefudge]

A propos of today's W3C Breakout Day presentation about possible ways to standardize how [extended or protocol-handler-registered] browser could act on the AP they discover on pages, I was left wondering where elk.zone fits into the landscape.

Specifically, once a browser "installs" a SPA called elk.zone, any AP-enabled webpage can be reopened "in" elk, which is a Mastodon client and thus interacts with the AP on a given page "from" the end-user's "home server". In effect, whenever someone sends me an AP link, I open it in my browser, and if I want to like or reply, I insert "elk.zone/" between https:// and the domain instead of using the "take me home" modal offered by the remote server. This, too, could be generalized or incorporated into, e.g., a browser extension pre-configured with the end-users home-server credentials; it could, for example, enable federation automatically on an AP-declaring page via JS APIs, and if that fails, fallback to an "elk.zone" style homepage-redirect. Not the most elegant solution, but maybe one worth considering, if only to talk people out of it 😅

Just leaving an issue for later, I know this isn't currently in-scope of the TF, but wanted to write it down before going about my day and forgetting this "shower thought"

[bumblefudge]

i'm receiving word that elk.zone actually only works for Mastodon-API servers. For the purposes of the above comment, imagine instead a hypothetical https://caribou.zone that parses a given page for the discovery mechanisms outlined in the Note and works on AP-enabled pages with no reference to any APIs presumed on the domain root.