Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically enable Hypothesis (only on certain sites?) #1253

Open
nairiboo opened this issue May 18, 2023 · 2 comments
Open

Automatically enable Hypothesis (only on certain sites?) #1253

nairiboo opened this issue May 18, 2023 · 2 comments

Comments

@nairiboo
Copy link

https://hypothesis-open.slack.com/archives/C6Y375TT3/p1678893693075289

I suspect this would be a better place than issues. I've been using hypothesis for years, and the friction when annotating has always been a barrier for me. IMO, annotation should feel like a native part of the browser, which it just isn't when you need to click the badge. There are three approaches I've seen discussed
Active everywhere
This one is by far the most simple, but introduces many problems. Some pages without content bound to a permalink are undesirable to annotate on, like timelines and search engines, so seeing annotations there would be terrible. Additionally, the tooltip could conflict with tooltips on the original page, like editing tooltips or native annotation functionality (though it would be nice if everyone just used hypothesis 😁)
Active if there are prior annotations
With this one, it's not active everywhere, but not much better. The same timeline problem applies, and I frequently find myself being the first one to leave annotations. It enhances the social aspect, but purely as an annotator, I don't think anything is gained
My idea: heuristics
There are certain qualities of content that can effectively determine if

  1. the user is likely to want to launch hypothesis
  2. Anticipating that would not degrade the UX, even if the user didn't actually want to.
    The most obvious heuristic is meta tags, which are a blessing. For articles to embed appropriately in sites like discord, twitter, and slack, (as well as SEO?) websites add meta tags which can give some insight into the content. Specifically, the og:type property with the content of article seems to be widespread among the content I annotate, and is standardized. In my opinion, this is the best of both worlds. Hypothesis, by design, is unlikely to be intrusive in articles, and in almost all cases it will already be active when the user goes to annotate.
@nhan000
Copy link

nhan000 commented Aug 17, 2023

I'd like to voice my support for the active everywhere feature. I think this would be a major improvement.

If you're using this for private groups, sites likely won't be cluttered with highlights. So the extension can be set to be active everywhere and to the profile that the users chose. The current situation that has a number indicator next to the logo is too subtle and hard to notice because our eyes don't usually go to the extension section for every website. If the extension is active everywhere without users having to trigger it, the number indicators on the side are much easier to see
image

However, I think we can also learn from Readwise, which has a good design: They add a banner right below the address bar, where our eyes usually are, so it's really easy to notice if you have highlighted this website before.
image
(Screenshot grabbed from this video)

Thank you so much for making Hypothesis. I'm a big fan!

Related: #1487, #1123

@robertknight robertknight changed the title Easier access to annotations in webapp Automatically enable Hypothesis (only on certain sites?) Jan 26, 2024
@AnweshGangula
Copy link

just for reference, this was discussed few years back here: #1487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants