Replies (with or without tags) to primary/original annotations are unable to subsequently be found in the main public stream or via search at https://hypothes.is/search.
Steps to reproduce
- Make a reply to any public annotation (with or without tags)
- Use https://hypothes.is/search to search the username of the reply or one of the original tags
- The reply can’t be found
The original (more complicated) example that uncovered the issue
From https://doi.org/10.6092/issn.1971-8853/8350 which redirects to https://sociologica.unibo.it/article/view/8350, I can click on the pdf icon to get to https://sociologica.unibo.it/article/view/8350/8272 which I can download locally and then reopen in Chrome to annotate with the Hypothes.is client.
I was able to make an original public annotation: https://hypothes.is/a/Nysv1HyTEeyaC2cnv3ZCPQ
Having subscribed to my public individual user feed, this annotation (via the annotation permalink and not via the original document) was found in Ton Zijlstra‘s RSS reader, and he was able to reply to it: https://hypothes.is/a/p3uUBJc8EeyuRmfRyGEGfQ.
Oddly the URL https://sociologica.unibo.it/article/view/8350/8272 when activated for Hypothes.is doesn’t show any of the annotations though I would suspect that the .pdf fingerprint should match that of the downloaded and annotated version. Alternately visiting https://uni-bielefeld.de/soz/luhmann-archiv/pdf/jschmidt_niklas-luhmanns-card-index_-sociologica_2018_12-1.pdf shows 51 annotations in the Chrome extension, though none of them are visible and the .pdf file doesn’t load on the page which returns a 404. Ton Zijlstra, having none of these URLs would otherwise not have been able to find or reply to annotations I’ve made other than having the original pointer via his RSS feed.
This last part non-withstanding, after making his reply to my annotation (directly at https://hypothes.is/a/Nysv1HyTEeyaC2cnv3ZCPQ), Ton Zijlstra is now no longer able to find his original annotation in the https://hypothes.is/search online interface. It’s as if it’s completely disappeared as the main web search interface is unable to find it via username and/or tags and (likely by design) the main public thread only shows top level annotations and not replies.
I’ve tried some similar experiments on my own replies to annotations. I’m unable to search my own annotations (via https://hypothes.is/users/chrisaldrich) or use either a user-based or tag-based search to find those same annotations after they were made, thus they’re essentially lost to me and others unless I can find the original document and trace my way back to them. These replies are obviously available via feeds (RSS/ATOM) and the API (using the urn:x-pdf:471902ab75f5683c53518d14f95f0dfe key), but they are essentially lost to the vast number of users who won’t have recourse to these methods.
Similarly searching Ton Zijlstra’s user name: https://hypothes.is/users/tonz, one will see no public annotations despite his public reply to a public annotation. The reply can be found at https://hypothes.is/stream.atom?user=tonz and via API calls.
After having made a reply to an annotation (with or without tags), one should expect to be able to search their own annotations or specific tags and find those public replies to annotations again.
Whether or not the main web stream (https://hypothes.is/search) filters out replies, they should still be able to be found via subsequent direct search.
Searching for one’s previous replies, via user, tag, or otherwise doesn’t find them, though they certainly exist and are findable in feeds and API.
Related, possibly helpful for the above
- Document fingerprint in the example above: urn:x-pdf:471902ab75f5683c53518d14f95f0dfe
- docdrop version of the same fingerprinted pdf: https://docdrop.org/pdf/Niklas-Luhmanns-Card-Index_-Th—Schmidt-Johannes-F.K_-0rcv9.pdf/
- Example extant annotation that doesn’t resolve on https://uni-bielefeld.de/soz/luhmann-archiv/pdf/jschmidt_niklas-luhmanns-card-index_-sociologica_2018_12-1.pdf#annotations_HzcGQHyFEeyQAqNHDXjO3Q
I’ve tried on other platforms and browsers and platforms with similar results, but I’m using Windows 10 and see the same behavior in both Chrome (Version 98.0.4758.102 (Official Build) (64-bit)) and Firefox (97.0.1 (64-bit)).