This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
1MMcM
I'm sure there's a solid engineering reason why touchstones are so much less reliable than Search.
So perhaps we could have a workaround in the interim, instead of all spending time trying to finesse the current thing when it turns up red or stalls in loading.
For example,
(1) Allow separate key and display parts in the touchstone. Perhaps separated by vertical bar ("pipe"), like in Wiki markup.
(2) Allow unambiguous keys. Such as #work-id or #lastfirst. Something you can copy / paste from the work / author page URL after Search. In fact, why not allow the whole URL (but interpret it so that it's listed at the top and in conversation backlinks).
So perhaps we could have a workaround in the interim, instead of all spending time trying to finesse the current thing when it turns up red or stalls in loading.
For example,
(1) Allow separate key and display parts in the touchstone. Perhaps separated by vertical bar ("pipe"), like in Wiki markup.
(2) Allow unambiguous keys. Such as #work-id or #lastfirst. Something you can copy / paste from the work / author page URL after Search. In fact, why not allow the whole URL (but interpret it so that it's listed at the top and in conversation backlinks).
