can an embedded client’s share link omit hyp.is?

[judell]

For APA (and others, e.g. Atypon), via’s no-cookie policy is a showstopper. But when the client is embedded, there’s no need for via.

So what’s the problem? Share links.

An embedded client provides hyp.is links that resolve, unnecessarily and problematically, through via. Could an embedded client be configured to (and perhaps default to) plain (non-hyp.is) share links?

[dwhly]

Could an embedded client be configured to (and perhaps default to) plain (non-hyp.is) share links?

I'm not sure what a "non-hyp.is" share link is. AFAIK we have no such thing. We did have via share links, but that's the problem here. There is an outstanding issue though that would address this: hypothesis/product-backlog#720 Which is essentially to be able to know a priori when the client is embedded on a target page before bouncer routes to via.

(Cards like this that are feature requests should be filed in product-backlog btw. Only client bugs should be filed in client repo.)