Unable to search or find public replies to annotations in public stream

Filed an Issue GitHub - hypothesis/client: The Hypothesis web-based annotation client. (GitHub)
The Hypothesis web-based annotation client. Contribute to hypothesis/client development by creating an account on GitHub.

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

  1. Make a reply to any public annotation (with or without tags)
  2. Use https://hypothes.is/search to search the username of the reply or one of the original tags
  3. 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.

Expected behaviour

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.

Actual behaviour

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.

Additional details

Related, possibly helpful for the above

Browser/system information

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)).

Hypothesis caching the same post title for all annotations on a single site

Filed an Issue hypothesis / client by hypothes.ishypothes.is (GitHub)
The Hypothesis web-based annotation client. Contribute to hypothesis/client development by creating an account on GitHub.

Steps to reproduce

  1. Annotate any page on https://boffosocko.com
  2.  View https://hypothes.is/search?q=url%3Aboffosocko.com%2F* 

Expected behaviour

I would expect the titles of the various annotated posts displayed on H to be that of the <h1> tag on the annotated page or some other logical name based on a parsing algorithm.

Actual behaviour

The titles for almost all the annotations on my website (since 2016), regardless of the page they’re on, appear to be the incorrect title: “Top Ed-Tech Trends of 2015: Indie Ed-Tech”. The few exceptions seem to be the self-hosted .pdf files on my domain/storage that I’ve annotated.

Browser/system information

This appears to be browser and OS independent

Additional details

The only post on my website related to the title which appears seems to be https://boffosocko.com/2020/05/16/top-ed-tech-trends-of-2015-indie-ed-tech-audrey-watters/ which contains copies of the annotations I made on Audrey Waters’ page. See: http://hackeducation.com/2015/12/21/trends-indie#annotations:soppjJeoEeq9gccaKJdTtg

Some time around 2016 Audrey disabled annotations on her site (due to abuse, though it appears she’s since re-enabled them?). Is it possible that the H client has somehow cached the title of her post and is somehow mapping it as the title for all of the annotations made on my site? Having looked at the pages which have been annotated on my site, there’s nothing hiding in or related to the the meta data or rel=”canonical” links that would indicate that they should have the titles that H is finding for them.

v4.2.2 Errors in Weather Near me widget

Filed an Issue dshanske/simple-location by David ShanskeDavid Shanske (GitHub)
Adds Basic Location Support to Wordpress. Contribute to dshanske/simple-location development by creating an account on GitHub.

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-sloc-weather-widget.php on line 74

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 883

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 883

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 883

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 883

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 888

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 891

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 895

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 904

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-weather-provider.php on line 904

Warning: array_key_exists() expects parameter 2 to be array, string given in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-sloc-weather-widget.php on line 84

Warning: Invalid argument supplied for foreach() in /homepages/32/d491429024/htdocs/boffoblog/wp-content/plugins/simple-location/includes/class-sloc-weather-widget.php on line 95

Bug in the Weather Widget display of sunrise/sunset and moonrise/moonset

Filed an Issue Simple Location (GitHub)
Adds Basic Location Support to Wordpress. Contribute to dshanske/simple-location development by creating an account on GitHub.
I’m noticing that the sunrise/sunset and moonrise/moonset details in the Weather Widget are “off”. It currently displays the following:

Sunrise: 10:40 pm
Sunset: 10:47 am
Moonrise: 10:54 am
Moonset: 10:32 pm

Sunrise should be 7:13 AM (roughly for today) though 6:13 AM for tomorrow after Daylight Saving Time changes tonight. Moonrise today should be roughly 5:52 pm and moonset at 6:14 am.

Manually changing the lat/long in the Weather widget doesn’t seem to fix it. I also get the same numbers if there isn’t lat/long in the widget but have them in the user profile in the location section.

I’m using OpenWeatherMap as the provider, and I notice I’m getting two different readings for the sunrise/set & moonrise/set depending on whether I’m using the User Last Seen Widget or the Weather widget, so maybe the issue is hiding in the difference between calculations of one versus the other? The weather widget is the one giving the incorrect readings.

Feature request: Recent Kinds Widgets and/or Now page aggregation

Filed an Issue Post Kinds Plugin for WordPress (GitHub)
adds support for responding to and interacting with other sites using the standards developed by the Indieweb Community - dshanske/indieweb-post-kinds

Recent Kinds Widget

It’s a reasonably frequent design/functionality pattern to see widgets from social media services. (Goodreads is an example that provides a widget for recent reads. Twitter does so for notes. There are countless others.) 

In an IndieWeb world, it would be nice to highlight what one has recently read, watched, or listened to (as examples). Towards this functionality, it would be nice if Post Kinds could provide the ability to add widgets for a variety of the post kinds to sidebars or footers.

As a baseline I could envision each widget having:

  • a configurable title (“Recently read”, “Food diary” for eats & drinks, “Microblog” for recent notes, bookmarks, etc.)
  • a chooser for one (or more) of the many various (enabled) kinds
  • a variable N to allow for display of the N most recent of the chosen kinds; 5 or 10 might be a reasonable default; a time-based variable to run across the post within a recent period (days, weeks, months) might be a an interesting alternative as well

For display of a single kind, the widget might default to displaying:

  • a heading made of the post kind icon along with “Recent [Post Kind Name plural]”
  • Response Property Name (wrapped with the original permalink if it exists) by Author name (if it exists)
  • An optional published date for the original content (if it exists) or the date the site owner published the post kind (if it exists) (the original content date would be better for context, I think)
  • A fleuron () or hash (#) which could be wrapped with the permalink of the original Post Kind post.

UI example: 


If the chooser in the widget allows for displaying multiple kinds at the same time, then one could have a widget for “Recent Media Consumed” or for displaying a sidebar microblog that could include Notes, bookmarks, reads, etc. (Making it similar to embedding one’s Twitter feed into a sidebar.

For encouraging outside consumption, the widget could also have a small RSS icon with a link to that Kind’s (or Kinds’) feed.

Naturally there could be some configuration for reasonable display defaults for some of the various Post Kinds./

Now archive page

Given some of the potential similarity of the widget work above, it would also be fun to have Post Kinds generate an archive page that shows by kind either the N most recent posts for each kind or all the posts within the last M days, O weeks, or P months.

This could be used to automatically generate the idea of a Now page that gives a quick overview of what a person has been up to over a relatively recent time period. A month of posts would be a good default.

One might also be able to use a solution like How to Add WordPress Widgets in Post and Page Content as a means of embedding the widgets into such a Now-type page, which could give the user the ability to pick and choose which order to place the particular kinds into based on the site owner’s discretion.

Scrolling issue on mobile highlighting using via with Chrome and Brave browsers

Filed an Issue The Hypothesis web-based annotation client (GitHub)
The Hypothesis client is a browser-based tool for making annotations on web pages. It’s a client for the Hypothesis web annotation service. It’s used by the Hypothesis browser extension, and can also be embedded directly into web pages.

Steps to reproduce

  1. On mobile version of Chrome using the via.hypothes.is prefix to activate Hypothesis on any website.
  2. I try to highlight a specific piece of text beyond a single word.

### Expected behaviour
I would expect to be able to slowly and accurately highlight a specific piece of text.

### Actual behaviour
Once I’ve got a small piece of text highlighted and try to expand it with the “handlebars” to go either up or down the page, generally beyond text on the same line, the cursor jumps immediately down to the very bottom of the page and it becomes essentially possible to select a particular block of text.

### Browser/system information
Chrome browser v 86.0.4240.75 on Android 9

### Additional details
I’ve experienced this before on earlier versions of Chrome/Android. I’m not aware of it having ever worked properly before. I don’t experience the same issue on the mobile version of Firefox on the same phone.

@williamgunn has reported a similar bug when using the Brave browser as well at:

Add Post Kinds fields to WordPress Search

Filed an Issue dshanske/indieweb-post-kinds (GitHub)
adds support for responding to and interacting with other sites using the standards developed by the Indieweb Community
I’ve noticed that the built-in WordPress site search is generally abysmal because so much of the content of my site is handled by Post Kinds and the search doesn’t look through any of the common Post Kinds data fields. 

As an example, trying to search for watches of particular television shows I know I’ve watched don’t show up because I leave those post title-less and don’t specifically tag them.

Is there something in the codex that will allow you to hook these fields into WP’s internal search?

Support for cycling in icon set

Filed an Issue Simple Location by David ShanskeDavid Shanske (GitHub)
Adds Basic Location Support to Wordpress.
I only noticed because I actually went to post something while cycling around the neighborhood, but you seem to be missing a cycling option and a bicycle icon.

The only other edge cases I can immediately think of are scooter, roller skates, tractor, skateboard, gondola, and horse drawn carriage. Though these may be harder to find icons for and exceptionally rare in any case…

Good job on having nearly every other mode of transportation by the way.

Add this Website

Filed an Issue maxboeck/whimsical (GitHub)
A curated list of websites with an extra bit of fun.
URL: https://www.kickscondor.com/
Author’s Twitter Handle: (optional)@kickscondor

The fun feature I like most about this site is… the design aesthetic and the regular highlighting of quirky, fun, and off-the-beaten path content that it features. (It’s also very likely a great source for other whimsical and interesting websites and creators).

IndieWeb Newsletter should include new videos from the IndieWeb Archive.org account

Filed an Issue This Week in IndieWeb (GitHub)
Weekly digest of IndieWebCamp activity. Contribute to indieweb/this-week development by creating an account on GitHub.
I don’t remember if the Newsletter used to pick up videos from the IndieWebCamp YouTube account, but I’m pretty sure we haven’t set up any automation for the IndieWeb Newsletter to find and highlight our Archive.org videos. This feature would be nice to have, particularly on weeks following IndieWebCamps to notify everyone that the videos have been processed and posted.

Here’s a page on Archive.org for creating search queries without output of a variety of formats for raw data or even feeds: https://archive.org/advancedsearch.php#raw

The search should include at least videos posted from the IndieWeb account: https://archive.org/details/@indieweb

It might be worth having it pick up anything with the tags or common keywords like IndieWeb, IndieWebCamp, Webmention, Micropub, etc., but this may also require some moderation or oversight.

Filed an Issue Introducing: Quotebacks by Tom Critchlow (tomcritchlow.com)
A chrome extension to quote the web
Tom, first off, this looks awesome! 

My first question is: is there a list of CSS features for styling the way quotes look on one’s site? Your defaults are pretty solid, but I’m sure folks will want to tinker. Is there a way to contribute different styles to a list of a handful that the extension could make select-able on my site?

Second, I haven’t actually been able to use the functionality at all. It took a few minutes to find the pop up window that I ignored on install to figure out the ctrl-shift-s command. Once that was sorted, I’ve got another browser extension (The Great Suspender) that uses this same key sequence which then triggers that and not Quotebacks. Perhaps having the ability to custom configure the key sequence would be useful as would the ability to click on the browser extension icon as a means of triggering the quote save (a common pattern for extensions).

I’ll also note that even after disabling the other conflicting extension and refreshing, the ctrl-shift-s still doesn’t work, but I’m not sure what the conflict or issue may be. Having a few methods for triggering save would definitely be a benefit.

Finally, in addition to some of the other discussion I’ve seen which may nudge you to support fragmentions, Google just released highlight and scroll across the web from search this past week. Like fragmention, it provides an alternate method for a link to go to a webpage, scroll to and highlight the quoted portion(s). Perhaps a nice additional feature? (I suspect that fragmention may be easier and simpler to support.)

Replied to A thread on Hypothes.is in relation to Audrey Watters' Top Ed-Tech Trends of 2015: Indie Ed-Tech by Audrey Watters, Jeremy Dean, Dan Whaley (Hack Education / Hypothes.is)

it supports students and teachers and schools in managing their own infrastructure, their own labor, their own data.

—Audrey Watters

Ok, so is hypothes.is doing this? How can it?

  • my annotations must be better accessible/organizable --the current "My Annotations" is not enough
  • annotation must be exportable

—jeremydean on Dec 30, 2015

And ultimately, you need to be able to completely run your own annotation infrastructure, but create and access it through a universal client.

—dwhly on Dec 30, 2015

Sure. Less clear to me how that looks/works and what that I do today online is similar in "ownership." But does your "you" refer to students or teachers or schools or all of the above?

The first two (I list) seem key in terms of practical adherence to these principles for everyday users.

—jeremydean on Dec 30, 2015

It's similar in character to the Domain of One's Own initiative. From a long term perspective, you might be better off taking ownership of your own infrastructure, that you can carry with you and guarantee will be available over long time periods (decades to centuries). Hypothes.is should at the very least permit you to do so if you prefer-- regardless of whether we continue to provide an annotation service at scale (which I very much think we should).

Your question around "you" is an important one. I might for instance, set up my own annotation server for my personal notes-- with the confidence that I'll always be able to find a reliable hosting provider for those. Similar to how I have my own web domain, and I host it at one place now, but I can always move it if that location goes out of business-- and my website will be identical to its current form in the new place. In the same way, my current personal email is through an address at my own domain. I don't need to depend on gmail being around forever.

As a teacher, I might use a more common service provider (like Hypothes.is) for class lessons-- one that my students are already likely to have accounts on. As web travelers, we're really accustomed to browsing seamlessly between servers-- it's understood to be the essential architecture of the web. Bringing it to the world of annotations has extraordinary benefits (IMHO) and will serve to foster more adoption and more diversity of applications.

—dwhly on Dec 30, 2015

I’ve been thinking over some of this question for the better part of a decade and even more pointedly since November.

Some of what I’ve been looking at relates back to the renaissance ideas of the commonplace book as well as memory techniques dating back to ancient Greece and even further back. There are ideas like wikis (personal as well as public–Audrey references a great post by Mike Caulfield in her article) and online notebooks tools like Evernote, OneNote, TiddlyWiki, Roam Research, etc. If a student could quickly add all their highlights/annotations into their website, online notebook, Zettelkasten, or other related learning tools, then they could use them for reading, reviewing, or even spaced repetition as provided by platforms like Anki, Mnemosyne, or NeuraCache.

Going back to Jeremy’s original question though:

Ok, so is hypothes.is doing this? How can it?

Hypothesis could immediate do this and quite effectively if it supported the W3C recommended Micropub spec. In short, it’s a standard and open source method for publishing data to a broad spectrum of surfaces so that developers don’t need to build custom solutions for each of thousands of snowflake platforms.

That is, in addition to its current functionality, you could add some code to make Hypothesis a Micropub client!

The quickest and most flexible approach I might suggest would be to allow users to publish their annotations/highlights not only to their accounts, but have UI to trigger a micropub request to their website, online notebook, or other platform.

There’s nothing more I’d want than an easy way to own all the data I’m collecting with Hypothesis and Micropub could quickly add it for a wide variety of set ups and systems. There are already implementations of Micropub servers for a variety of CMS software including WordPress, Drupal, Known, Craft, Jekyll, Kirby, Hugo, Blot, and Micro.blog with others being added, including Grav. Some of us are actively working on adding it to Wiki-related software as well. Since large portions of the Domain of One’s Own movement are built on these handful, you’d have some pretty quick coverage of not only all this space but even more.

I suspect your dev team could build an implementation in just a few days and it would open up a huge advantage for allowing users to more easily own their H related data on their own websites or in other online locations (while still utilizing the Hypothesis platform for more complex functionality).

There’s some solid documentation and a wealth of open source clients you could look at or borrow code from as well as a test suite. I suspect the IndieWeb Dev chat channel would surface a few additional developers to answer questions about any other issues as they crop up.

If you’d like a quick 5-10 minute demo of how this works for a handful of other clients in conjunction with something like WordPress, I’m happy to volunteer the time and spitball some potential ways Hypothesis could dovetail it and leverage its power.

Filed an Issue Make a Comparator (splot.ca)
Create your own! This tool will produce much better results if the images are much larger than the intended size (e.g. 1400 x 800 at least) since it needs to downsize the original to fit the different dimensions.
Alan, I took a swing at trying out the live Comparator SPLOT today. It’s very cool looking! Sadly I kept getting an error in the WP upload interface simply saying “An error occurred in the upload. Please try again later.”

I was uploading a simple .jpg of about the same size and dimensions as those recommended and already in the repository. I tried a few different photo sizes and types with the same result, so I’m not sure what the underlying issue may be. Unless something has changed dramatically, my one guess would be to check the storage limits on the hosting account. I’ve seen that sort of failure before when running out of physical space on a host.

Incidentally, from a security standpoint, I’ll mention that it appears one has the ability within that interface to delete others’ previously uploaded photos. (May want to look at that as a potential future improvement.)

Hope you’re holding up!

Filed an Issue Post Via Email (reading.am)
Post Via Email Send a link in the body of an email to this address and we'll post it to your account. It's handy for posting from your phone or favorite app, so save it in your address book for easy access. But remember, keep it super secret because anyone who has it can post!
@reading It looks like posting via email is having issues? Error shows: “the domain mailman.reading.am couldn’t be found.”

Map archives don’t display map for Google Maps

Filed an Issue Simple Location by David Shanske (GitHub)
Adds Basic Location Support to Wordpress. Contribute to dshanske/simple-location development by creating an account on GitHub.
When adding /map/ to date-based archives and using Google maps as the map provider, the map doesn’t display on the page.