Robert Knight robertknight

## fetch-annotation-pages.py
import os

import requests

search_after = ""
page_size = 200
group = os.environ["HYPOTHESIS_GROUP"]
access_token = os.environ["HYPOTHESIS_ACCESS_TOKEN"]
max_to_fetch = 10_000  # Max annotations to fetch before we stop

## hypothesis-canonical-links.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              0 stars
            
          
                robertknight
                / hypothesis-canonical-links.md
            
            
              Created
              July 7, 2022 10:37
            
              
                How Hypothesis interacts with canonical links (`<link rel=canonical>`)
              
          
      View hypothesis-canonical-links.md
  
      
    Hypothesis and canonical links
What are canonical links?
A <link rel="canonical" href="{url}"> tag in the <head> of a page specifies the canonical/"main" URL for the current page. When the same content can be accessed at different URLs, it specifies the preferred URL for the page. It was originally introduced for use with search engines.
For example, https://www.smore.com/577k7, https://www.smore.com/577k7-whatever and https://www.smore.com/577k7-the-edtech-monthly all return the same page. That page has a <link rel=canonical> field which specifies https://www.smore.com/577k7-the-edtech-monthly as the preferred URL.
See also https://en.wikipedia.org/wiki/Canonical_link_element.

  
## vitalsource-local-hypothesis.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                robertknight
                / vitalsource-local-hypothesis.md
            
            
              Last active
              June 30, 2022 10:18
            
              
                Testing VitalSource assignments with your local Hypothesis development environment
              
          
      View vitalsource-local-hypothesis.md
  
      
    VitalSource assignments in the LMS are different than other assignment types because the document is being displayed in a reader maintained by a third-party (VitalSource) rather than Via. This third-party reader always tries to load the production version of Hypothesis, whereas when Via is used to deliver a document, your local instance of Via will use your local Hypothesis client. A workaround for this issue to enable local testing is to redirect the request for the client's boot script to point to your local client, and modify the local client to ignore parts of the Hypothesis configuration in the page where the client's boot script is loaded.
The approach documented here can also be used in other situations where you want to subtitute the production Hypothesis client with the local one, in a page or web application where we can't modify the script tag that loads the client.

Configure your browser to redirect requests for the client's boot script at https://hypothes.is/embed.js to http://localhost:5000


## orientation-test.html
<html>
  <title>Canvas drawImage EXIF orientation test</title>
  <style>
    #dropZone {
      width: 300px;
      height: 100px;
      background-color: #aaa;
      border: 1px solid #ccc;
    }

## license-report.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                robertknight
                / license-report.md
            
            
              Last active
              January 17, 2023 22:37
            
              
                License report for Hypothesis project dependencies
              
          
      View license-report.md
  
      
    Hypothesis frontend project license report
This report lists the direct npm dependencies of the main Hypothesis frontend projects. See this internal Hypothesis Slack thread.
How to generate the report
The data below was generated using https://github.com/ironSource/license-report, with the following license-report-config.json configuration file:
{

  
## private-memory-stats.py
import os
import sys


def process_private_memory(pid):
    smaps_path = f"/proc/{pid}/smaps"
    total = 0
    for line in open(smaps_path, 'r'):
        field, val = [val.strip() for val in line.split(':')]
        if field != "Private_Dirty":

## generate-svg-components.js
/* global process */

'use strict';

const fs = require('fs');
const { basename } = require('path');

const escapeHtml = require('escape-html');
const htmlParser = require('htmlparser2');
const prettier = require('prettier');

## hypothesis-client-wcag-a11y.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                robertknight
                / hypothesis-client-wcag-a11y.md
            
            
              Last active
              February 25, 2020 13:16
            
              
                Hypothesis client remaining a11y work
              
          
      View hypothesis-client-wcag-a11y.md
  
      
    This is a brain-dump of remaining work to achieve a fully accessible [1] Hypothesis client.
[1] fully accessible means that you can use all the functionality with a keyboard (or keyboard-emulating input device)
and screen reader (or other assistive tech) conveniently and that it meets (both in letter and spirit) all the WCAG criteria.
That doesn't necessarily mean that everything is as fully optimized as it could be (eg. in terms of what keyboard shortcuts are available to speed up various workflows).
Development tasks:

Make it possible to activate highlights with the keyboard
Make it easier to execute Annotate / Highlight commands using the keyboard


## reviewing-dependency-updates.md

      
              1 file
            
          
              0 forks
            
          
              1 comment
            
          
              3 stars
            
          
                robertknight
                / reviewing-dependency-updates.md
            
            
              Last active
              February 3, 2020 20:42
            
              
                How I review dependency updates
              
          
      View reviewing-dependency-updates.md
  
      
    How I review dependency updates
These are some notes on my process when I review dependency updates for both JavaScript and Python projects
at Hypothesis.
Before you add a dependency
Before adding a dependency to a project, consider the impact on future maintenance. If what the dependency does for the project can be implemented with only a few lines of code, or can be implemented in an alternative way using dependencies the project already has, it may be a better choice to do that and avoid the dependency.
Dependency update process

  
## gen_charmap.py
import sys
import time
import unicodedata


def gen_charmap_new():
    current_cat = None
    current_cat_start = None
    ranges = []
	import os

	import requests

	search_after = ""
	page_size = 200
	group = os.environ["HYPOTHESIS_GROUP"]
	access_token = os.environ["HYPOTHESIS_ACCESS_TOKEN"]
	max_to_fetch = 10_000 # Max annotations to fetch before we stop
	<html>
	<title>Canvas drawImage EXIF orientation test</title>
	<style>
	#dropZone {
	width: 300px;
	height: 100px;
	background-color: #aaa;
	border: 1px solid #ccc;
	}
	import os
	import sys


	def process_private_memory(pid):
	smaps_path = f"/proc/{pid}/smaps"
	total = 0
	for line in open(smaps_path, 'r'):
	field, val = [val.strip() for val in line.split(':')]
	if field != "Private_Dirty":
	/* global process */

	'use strict';

	const fs = require('fs');
	const { basename } = require('path');

	const escapeHtml = require('escape-html');
	const htmlParser = require('htmlparser2');
	const prettier = require('prettier');
	import sys
	import time
	import unicodedata


	def gen_charmap_new():
	current_cat = None
	current_cat_start = None
	ranges = []