21 Matching Annotations
  1. Last 7 days
    1. Create an IFTTT.com recipe to port your Hypothesis RSS feed into WordPress posts. Generally chose an “If RSS, then WordPress” setup and use the following data to build the recipe: Input feed: https://hypothes.is/stream.atom?user=username (change username to your user name) Optional title: {{EntryTitle}} Body: {{EntryContent}} from {{EntryUrl}} <br />{{EntryPublished}} Categories: Highlight (use whatever categories you prefer, but be aware they’ll apply to all your future posts from this feed) Tags: hypothes.is Post status (optional): I set mine to “Draft” so I have the option to keep it privately or to publish it publicly at a later date.

      Posting this solely to compare my Hypothes.is highlights and annotations on my website with Will's version.

      I'm still tinkering with mine and should have a Micropub based version using IFTTT and Webhooks done soon.

  2. Sep 2019
    1. In April of 2019, at a digital learning conference, Manuel Espinoza spoke with educators, technologists, and annotation enthusiasts about R2L.d-undefined, .lh-undefined { background-color: rgba(0, 0, 0, 0.2) !important; }.d-undefined, .lh-undefined { background-color: rgba(0, 0, 0, 0.5) !important; }1Nate Angell and “the role that Hypothesis plays in human rights work.”

      Manuel Espinoza, “Keynote,” AnnotatED Summit, April 2, 2018, https://youtu.be/5LNmSjDHipM.

  3. Aug 2019
    1. Now you have the extension up and running.

      If you see this annotation, you have annotations up and running :)

    1. Art by O’Hare and Bell highlight - both visually and conceptually - the dialogic quality of annotation expressing power.

      While I'm reading this, I can't help but wishing that Hypothes.is would add a redaction functionality to their product. They could potentially effect it by using the highlighter functionality, but changing the CSS to have the color shown be the same as that of the (body) text instead of being yellow.

  4. Jun 2019
    1. They both obviously point to the same specific page, and their beginnings are identical. The second one has a # followed by the words “I’m not looking” with some code for blank spaces and an apostrophe. Clicking on the fragmention URL will take you to the root page which then triggers a snippet of JavaScript on my site that causes the closest container with the text following the hash to be highlighted in a bright yellow color. The browser also automatically scrolls down to the location of the highlight.
  5. Apr 2019
    1. But thirdly, and most valuably, the template gives you a big space at the bottom to write sentences that summarise the page.  That is, you start writing your critical response on the notes themselves.

      I do much this same thing, however, I'm typically doing it using Hypothes.is to annotate and highlight. These pieces go back to my own website where I can keep, categorize, and even later search them. If I like, I'll often do these sorts of summaries on related posts themselves (usually before I post them publicly if that's something I'm planning on doing for a particular piece.)

    1. I find it somewhat interesting to note that with 246 public annotations on this page using Hypothes.is, that from what I can tell as of 4/2/2019 only one of them is a simple highlight. All the rest are highlights with an annotation or response of some sort.

      It makes me curious to know what the percentage distribution these two types have on the platform. Is it the case that in classroom settings, which many of these annotations appear to have been made, that much of the use of the platform dictates more annotations (versus simple highlights) due to the performative nature of the process?

      Is it possible that there are a significant number of highlights which are simply hidden because the platform automatically defaults these to private? Is the friction of making highlights so high that people don't bother?

      I know that Amazon will indicate heavily highlighted passages in e-books as a feature to draw attention to the interest relating to those passages. Perhaps it would be useful/nice if Hypothes.is would do something similar, but make the author of the highlights anonymous? (From a privacy perspective, this may not work well on articles with a small number of annotators as the presumption could be that the "private" highlights would most likely be directly attributed to those who also made public annotations.

      Perhaps the better solution is to default highlights to public and provide friction-free UI to make them private?

      A heavily highlighted section by a broad community can be a valuable thing, but surfacing it can be a difficult thing to do.

  6. Mar 2019
  7. Feb 2019
    1. There’s also a robust ecosystem of tools to follow users, monitor site annotations etc.

      Wait? What!? I've been wanting to be able to follow users annotations and I'd love the ability to monitor site annotations!! (I've even suggested that they added Webmention before to do direct notifications for site annotations.)

      Where have you seen these things hiding Tom?

  8. Jan 2018
    1. merely stops you from writing in the margins here on this website.

      Does the script Audrey Watters is using really stop people from annotating her site directly?

      Based on my quick test, one can still (carefully) use Hypothes.is to highlight and annotate her site, but the script at least prevents Hypothes.is from showing that annotation. When visiting her site with Hypothes.is' Chrome browser extension on, it does show that there is one annotation on the page. It then requires some hunting to find this comment.

  9. Nov 2016
    1. The New York Times

      I'm wondering if the NY Times used the summit to figure out how to prevent annotating at all? Somehow I'm not able to reasonably use either Hypothes.is or Genius with it in multiple browsers.

      In particular I just can't highlight anything on the page, and attempts usually end up moving me to a new article. Blech!

    1. This is a picture of the first HTTP web server in the world. It was Tim Berners-Lee's NeXT computer at CERN. Pasted on the machine is an ominous sticker: "This machine is a server, do not power it down!!". The reason it couldn't be powered down is that web sites on other servers were starting to link to it. Once they linked to it, they then depended on that machine continuing to exist. If the machine was powered down, the links stopped working. If the machine failed or was no longer accessible at the same location, a far worse thing happened: the chain between sites becomes permanently broken, and the ability to access that content is lost forever. That sticker perfectly highlights the biggest problem with HTTP: it erodes.

      This is interesting, since the opening video for https://hypothes.is/ mentions the early web also - in this case, for its annotation features that were removed.

      It seems to me that hypothes.is is even more powerful used on IPFS content identified by hash since that underlying content cannot change.

      Thanks to both services I'm doing exactly this right now!

  10. Apr 2016
    1. appreciate your help

      I think that a major part of improving the issue of abuse and providing consent is building in notifications so that website owners will at least be aware that their site is being marked up, highlighted, annotated, and commented on in other locations or by other platforms. Then the site owner at least has the knowledge of what's happening and can then be potentially provided with information and tools to allow/disallow such interactions, particularly if they can block individual bad actors, but still support positive additions, thought, and communication. Ideally this blocking wouldn't occur site wide, which many may be tempted to do now as a knee-jerk reaction to recent events, but would be fine grained enough to filter out the worst offenders.

      Toward the end of notifications to site owners, it would be great if any annotating activity would trigger trackbacks, pingbacks, or the relatively newer and better webmention protocol of the WW3C out of the http://IndieWebCamp.com movement. Then site owners would at least have notifications about what is happening on their site that might otherwise be invisible to them.

      Perhaps there's a way to further implement filters or tools (a la Akismet on platforms like WordPress) that allow site users to mark materials as spam, abusive, or other so that they are then potentially moved from "public" facing to "private" so that the original highlighter can still see their notes, but that the platform isn't allowing the person's own website to act as a platform to give reach to bad actors.

      Further some site owners might appreciate graded filters (G, PG, PG-13, R, X) so that users or even parents can filter what they're willing to see. Consider also annotations on narrative forms that might be posted as spoilers--how can these be guarded against? (Possibly with CSS and a spoiler tag?) Options can be built into the platform itself as well as allowing server-side options for truly hard cases.

      My coding skills are rustier than I wish they were, but I'm available to help/consult if needed.

    1. If anyone is aware of people or groups working on the potential integration of the IndieWeb movement (webmentions) and web annotation/highlighting, please include them in the comments below–I’d really appreciate it.

      The IndieWebCamp.com site lists a small handful of people with Hypothes.is affiliations who had websites, but none of the seem to be active any longer. Perhaps we can track some of them down via twitter?

  11. Mar 2016
    1. ELA teachers can have their students analyze the rhetorical strategies in that same debate using an application like Hypothes.is. Looking at this speech through the lens of two different perspectives can deepen students’ knowledge.
    1. and

      And searching the web in general; searching and finding the connections among content rather than searching just for content.

  12. Feb 2016
    1. playful annotation in the open.
    2. This format [Hypothesis] is much better for me as far as encouraging participation. With the old discussion format that listed all the readings then posed questions for group discussion, I felt a bit overwhelmed by the long responses people offered and had a hard time jumping into the conversation. With Hypothes.is, I can offer my thoughts as I go, which I find to be much more effective in my assimilation of the information.
  13. Jan 2016