#hypothes.is

howdy

How does hypothes.is deal with pages which change over time?

howdy der

<dwhly> @kirkins

<dwhly> https://hypothes.is/blog/fuzzy-anchoring/

<nick> https://hypothes-is.slack.com/archives/C074BUPE...

<nick> Another sunny day, another day spent raging at Python packaging tools

<chdorner> @nick is it even possible to test out h#4482 in dev? or so we just need to put it out to qa where we actually send emails

<vannevar> Upgrade pyramid_mailer and repoze.sendmail: https://github.com/hypothesis/h/pull/4482

<nick> @chdorner sorry, only just saw this -- yes, you can test it locally by commenting out the inclusion of `h.debug` in `app.py` and using something like `python -m smtpd -n -c DebuggingServer 0.0.0.0:1025`

<chdorner> oh well, too late :slightly_smiling_face: I've already merged it and will check on staging. I'm pretty sure you tested it already anyway

<chdorner> ok, I can change my password on QA, and emails still get sent. I'm pushing this out to prod

<chdorner> @nick anything specific I can test locally for h#4484?

<vannevar> Upgrade to cryptography 1.8: https://github.com/hypothesis/h/pull/4484

<nick> @chdorner primarily that if you're logged in on master, then switch to that branch, you stay logged in

<nick> (i.e. that derived secrets don't change)

<nick> oh, and you'll need to run `pip install -r requirements.txt` in between, otherwise you ain't testing much

<chdorner> @nick are you looking at h#4486?

<vannevar> Initial Update: https://github.com/hypothesis/h/pull/4486

<nick> @chdorner I will do, but once we've merged the cryptography PR, at which point hopefully that one will automatically update.

<chdorner> just merged

<nick> ah, great

<nick> thank you

<nick> I've closed the pyup "initial update" branch, which triggers pyup opening individual branches for each dep update

<robertknight> This reminds me, we should look into setting up something similar for the client.

<nick> @robertknight snyk.io is probably what you're looking for

<robertknight> nick: Thanks, I’ll check it out

<nick> Manually pushing a bunch of changes to QA. Skyliner hasn't done so because the "safety-ci" check has failed due to an insecure version of html5lib in our dependencies. Fix for that incoming separately.

<nick> sadly my pidfiles change wasn't the whole story

<nick> still reporting as dirty, apparently because `git diff-files` is reporting that the working tree is dirty although it's clearly not...

<nick> either way, everything that actually matters seems to work in QA, so going to prod again

Hi all! May I ask a quick update on what is nowadays the status/plan/progress towards supporting different annotation servers? Separation of client & server repos is a great step towards this; now the questions are:

Regarding the client: (1) Has/will it become possible to use the client with a different h deployment, or (2) perhaps even with other server that follows a particular spec (presumably Web Annotation)?

Regarding the server: (3) Has/will it become easy to self-host an h deployment? And (4, related to 2), does/will it have a standardised API?

nickstenn/nick: maybe you have quick yes/no/soon/never answers to these?

<nick> treora: Hey Gerben!

<nick> In short, that's still a major goal, and we've made some major steps towards making it possible.

<nick> You can use a custom build of the client with your own h deployment already.

<nick> You can't (yet) use the browser extension with other annotation servers. There's no way to configure it, and more importantly the parts of the UI that would need to change to accommodate multiple authorizations isn't done yet.

<nick> Self-hosting h is probably a lot easier than it was last time you tried, although it's still far from perfect.

<nick> And lastly, while we expose all annotations in Web Annotations format (stick `.jsonld` on the end of an API URL for an individual annotation) this is currently only a read-only thing. The h API can't yet ingest annotations in that format.

<nick> But all of the shortfalls there are things we're still planning to remedy. There's just an awful lot of work to do to get there. :slightly_smiling_face:

nick: great, thanks for the info! I just heard the question come up again, now from some Internet Archive-related people; it seems there are plenty people who'd love to see H open up. :)

I guess asking for an estimation when these plans will unfold would be in vain?

I hope to hear more at I Annotate, I plan to be there. Also I am in Berlin until then, happy to grab a beer/bagel any day.

<slackbot> Reminder: Standup in seven minutes! Grab a cup of tea and head over to https://hangouts.google.com/hangouts/_/hypothes...

<slackbot> Reminder: Standup time! https://hangouts.google.com/hangouts/_/hypothes...

<chdorner> @nick just merged the bleach update and closed the pyup PR for it

<nick> Thanks!

<nick> bleach changes look good on QA