ESSOAr Launches Hypothesis Annotation
ESSOAr now offers Hypothesis annotation on their prepublication platform for early research outputs.
We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ...
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.
ESSOAr now offers Hypothesis annotation on their prepublication platform for early research outputs.
Last week we hit 6M total historical annotations (having announced the 5M annotation milestone overall only in mid-March). Hypothesis is now recording a million annotations every quarter. We ended June […]
Annotation alone is a powerful way to remix the web. When you add Twitter into the mix, possibilities multiply.
My good friend John Perry Barlow passed yesterday. John Perry, together with Gerry Percy, was Hypothesis’ founding (and till yesterday, active) board member. From the very beginning, he understood and […]
One of the most requested features we’re consistently asked for here at Hypothesis is the ability for group creators to moderate annotations that are made by group members. The rationale […]
Hypothesis is proud to show its support as a primary stakeholder for the Initiative for Open Citations (I4OC), an effort just announced to lead the scholarly industry towards opening the […]
A Message from the Engineering Team Up until this point, we have lived in a < 1.0 world. We have focused on shipping quickly and pushing innovative changes regularly. However, […]
This morning we have been made aware of a security vulnerability affecting Cloudflare, a major internet infrastructure company and our Content Delivery Network (CDN) provider.
All traffic to Hypothesis passes through Cloudflare’s servers in order to improve the performance and security of our service. Unfortunately, it appears that a bug in Cloudflare’s software may have leaked some traffic that should have been private into the pages it served for other customers’ sites. Put simply: it’s possible that communications that should have been private between our users and Hypothesis were not.
At the moment we have no evidence to suggest that any Hypothesis user’s private data was leaked as part of this vulnerability, but we are taking steps to minimise the risks posed by any possible disclosure.
The Annotating All Knowledge Coalition was founded as a forum for accelerating the development of a pervasive interoperable annotation layer across all scholarly works. Figuring out what, exactly, an interoperable annotation layer means was one of the first goals of the coalition. We took the first steps towards defining what an interoperable layer looks like and how it should operate at our Face to Face meetings at FORCE2016 and I Annotate. So what are the next steps?
Participants in both events felt strongly that the best way to move forward was to “Just do it”, that is, identify a use case where you have a need to share annotations across: tools, content, platforms, workflows.
This is a write-up of some research that I did for a session with our dev team at Hypothesis about how to make our code reviews a more pleasant and […]