Chris Aldrich

@wiobyrne If you change the date/time linked URLs from
https://hypothes.is/a/Y03z2H4QEeiWPlcSnuxgKA to
https://hyp.is/Y03z2H4QEeiWPlcSnuxgKA
They'll link, instead of to the standalone versions which might be more appropriate for syndication link usage, to the original document on the web and auto-scroll to the location of the annotation. This might give you a tiny bit more of the UI functionality you're looking for.

@mrkrndvs I found a solid example of highlighting and annotation using my own website in conjunction with @pressfwd and @hypothes_is on a great @audreywatters piece. It's closer to some of the UI I'd like to have, though the CSS still needs work.
http://boffosocko.com/2017/05/10/un-annotated-by-audrey-watters/

@mrkrndvs I'm curious if you manually cut & paste your replies for others' sites (who may not support webmention or even pingback/trackback) into their old-school comments sections?

I often worry that without that, or without replying to versions on Twitter if they syndicated, they won't see my response via pingback/trackback or other means. Instead my reply sits all alone on my site and they don't have the benefit of seeing it at all unless they come across it organically otherwise.

Generally when I manually cut and paste replies, I'll often use the comment's "website" field to include the permalink for my comment and then I'll take the permalink for my comment and add it to my syndication links since I've manually syndicated it.

Sometimes I notice that including multiple links in a reply can also run afoul of spam filters.

One of my favorite set of machinations occurred recently when I wrote this reply to Jon Udell: http://boffosocko.com/2018/01/07/reply-to-annotating-web-audio-by-jon-udell/

Jon came back to his original post and appended his own comment to document my comment in the most circuitous of manners which included using his annotation tool Hypothes.is: https://blog.jonudell.net/2018/01/06/annotating-web-audio/#comment-474656

Interestingly we both used WordPress, Hypothes.is, and Twitter to carry on the conversation. I was quite impressed that he took the time to circle back around and document my end of the conversation since he must have missed my pingback (he doesn't have webmentions) and my manual cut & paste, but did manage to see the notification on Twitter.

It all just goes to show that you've got to keep your eye on the tech that you and everyone else is using until it's broadly and evenly distributed. One day perhaps...

@audreywatters @mtechman @hypervisible @onewheeljoe Even with the script blocking @hypothes_is it is still possible to annotate hackeducation.com. Fortunately, though public annotations appear in the Chrome extension as existing, they don't physically appear on the site itself and need to be searched for manually to be found. I was able to do this with only just a few minutes of work, and could probably hack something more significant with some time/effort.
https://hypothes.is/a/KR0dXDYNEeeEH7_5Zf-ZuQ
http://boffosocko.com/wp-content/uploads/2017/05/annotation.png

Hypothes.is should really try to do a better job of preventing abuse in these types of situations so writers needn't worry about providing abusers the ability to use a writer's own platform to harass them. Perhaps borrowing the NIPSA concept from Flickr for flagged annotations and/or accounts? (NIPSA is an acronym for "Not In Public Site Areas", and an admin feature of Flickr that allows their support staff to mark an account such that posts from it will not be shown in search results and other similar public views of posts.)

@krisshaffer Nice mention of Hypothesis Aggregator in WPTavern today: https://wptavern.com/web-annotations-are-now-a-w3c-standard-paving-the-way-for-decentralized-annotation-infrastructure

@realkimhansen @signlfm If you hadn't been aware, this came out earlier in the week and may be of overlapping interest:
Three recommendations to enable Annotations on the Web | W3C News https://www.w3.org/blog/news/archives/6156
https://www.w3.org/annotation/
Their method of breaking down the problem and their vocabulary may be particularly useful; the overlay onto audio may be another problem altogether...

I also thought this post (with code) by Aaron Parecki, while a relatively simple concept, was exceptionally cool. https://aaronparecki.com/2017/02/19/4/day-61-media-fragments

UX Suggestion · Issue #3 · kshaffer/hypothesis_aggregator https://github.com/kshaffer/hypothesis_aggregator/issues/3

Towards the end of using this plugin as part of an online "notebook" or commonplace book, it would be nice to have finer control over the listings of the annotations.

As an example, look at: http://boffosocko.com/2016/06/18/a-new-thermodynamics-theory-of-the-origin-of-life-quanta-magazine/
The original post was a "bookmark" to an article which was then annotated, solely by me. When embedding the annotations (in this case the shortcode included one author and one specific tag), it becomes overly redundant to repeatedly include that the annotations were by me, that they're from the same article, and including the picture multiple times. As this is likely a frequent use case for such a plug in, perhaps when the same annotator is repeated all the annotations could come under one heading and similarly if it's the same article, those could be concatenated along with just one photo as well.

Suggested output:
TITLE OF PAGE1 | #
PHOTO from PAGE1
Annotations by AUTHOR1:
- annotation 1 from PAGE1
- highlight 2 from PAGE1
- highlight 3 from PAGE1
- annotation to go with highlight 3 from PAGE1

TITLE OF PAGE2 | #
PHOTO from PAGE2
Annotations by AUTHOR1:
- annotation 1 from PAGE2

Annotations by AUTHOR2:
- annotation 2 from PAGE2
- annotation 3 from PAGE2

This type of logic isn't too difficult given the current configuration though it may require some thought for the pending changes to add and/or functionality for multiple authors and multiple tags.

One particular hurdle may be cases where the order of annotations could potentially tell a "story" and even more so when there are multiple authors providing multiple annotations (for example when using this in a classroom setting versus a single-author notebook.)

Providing a visual indicator like # which includes a wrapped permalink URL for the particular article could allow the user to also quickly jump to that page and see the broader flow of annotations on a single page, especially in a classroom type setting where dozens of students may have made hundreds of annotations which may provide a slightly better contextual UI experience, while still allowing the (shortcoded) web page to include all of the annotations for historical purposes.

Potential future features · Issue #2 · kshaffer/hypothesis_aggregator https://github.com/kshaffer/hypothesis_aggregator/issues/2

This plugin is spectacular by the way... Here are some thoughts on future development:

It would be great if the displayed text output from the shortcode included a permalink to the original annotation on Hypothesis. As a UI suggestion, perhaps you could place it after the title of the annotated page thusly:
URL WRAPPED TITLE | < a href="permalinkhere">#</a>

Being able to circumscribe dates for displayed annotations could be useful, particularly in cases where one wants to highlight only a handful of annotations from a particular user with a particular tag but specific ones within certain time parameters. Additionally pages with embeds could, over time, require importing huge numbers of annotations which may not be ideal, or the context may change with significant future annotations that aren't relevant to what could be a static post that's trying to highlight just a few particular annotations. Time parameters could also prevent future possible spam on unwatched embeds with only "tag" parameters that could be targeted by bad actors.