 So, I'm going to go through the whole thing and show a few things that we've been working on over the last year, just to kind of give you a sense of what we've been up to. So, one of the first things that we've done is built a new interface for exploring annotations. So, you create on documents, on media, but then you want to be able to look at those annotations and explore them afterwards. So, we built that together with an interface that lets you create profiles and look at the profile of users and for groups. So, for instance, say I create a group here, which is a physics club, and then I get a dashboard here for that club that lets me, first of all, invite new people to this group. It becomes the profile for the group and it becomes the place where annotations accumulate over documents. So, if I go back to a document, here's a preprint on archive, and I go to my group control, I've now got the club there, and I can begin to do some annotations. And I might want to, for instance, grab a little app in the middle, sort the app tag here, the document tag, just a snap, post that. Then I might go to another place, for instance, here's a document, another article, and this is an HTML abstract. I'll just annotate this here. This one's at Elsevier, so I've got my physics club here. So, I'm carrying this group around the internet with me. I'm going to add comments and some tags. This one is maybe Matt, but it's about the documents. Can you see now what's in it? Absolutely. So, now I've got two annotations on two different documents, and if I go back to my interface and I press refresh, then I can explore those documents and the annotations that are on them. I can add, this is a faceted search interface, so the facet that's driving this particular view is the group physics club. But if I click on the tag, then I can start to explore using tags, using facets, the different views of this set of annotations that I want to look at. Annotations also now have addresses and direct links, so if I grab a link to this address or to this annotation, I can tweet it out, for instance, somebody can click on that and then it takes them right to that annotation and lays it over the document, and it's kind of fun to tweet out links to annotations, but also to link annotations together. So, for instance, if I go back to this first document, I can say look over here and make that link. And so, then I start to be able to link to, have annotations that link deeply into other things on the web, and that works, and have that as a ubiquitous layer that can lay over the web wherever I am. So, those are two key things we've released. We're also, I won't steal Juan's thunder here, but we are super excited about our integration with the EPUB reader, RediumJS. So now the same functionality that can lay over PDFs or HTML in about, I don't know, maybe six more weeks, we'll be able to lay over EPUBs using both RediumJS but also EPUBJS. So, that same functionality, this is a demo site, which is actually partially working. You can select text annotated just the same way that you could there. So our goal was to continue to expand the format coverage of annotation to be able to lay over more and more different kinds of things. And then the last thing I'll show you is a set of improvements to the interface that will be coming over the next couple of months, which allow publishers and others that embed hypothesis on a document or at a site to be able to determine and dictate the layers that are authoritative over those documents. So here a journal has embedded annotation on their journal and when you open the interface and you click on the annotations button, it inserts their group as the default layer over that journal. And also in this case that journal or that publisher has already authenticated their users and so the user, the pre-authenticated user comes to the annotation interface already signed in that namespace as opposed to the hypothesis namespace. So the publishers who want people not to annotate in some other system but within their own kind of world can fully integrate this sidebar and this annotation capability controlling both the layers as well as the namespaces of their documents. Of course as users we might want to bring, that's great that that publisher has embedded this tool, but we had a group somewhere else on the web in a different namespace so we still want to be able to bring that context to this journal article. So even though the journal still has, is running their own layers over their journal, I still want to bring perhaps a hypothesis group or a group on another server somewhere perhaps behind my firewall if I'm an employee at a corporation to this document and have those different contexts work fluidly together. So this is the beginning of us teasing apart this framework so that it begins to implement layers from anywhere. It's a truly universal plan. Our goal is that the hypothesis interface is really just a gateway to any interoperable annotation server and that vice versa that the annotations that are stored on our server can be viewed through other annotation clients. This is a long journey. True interoperability starts with things like standards, but some of the more challenging problems are making sure that at the user interface level that features a functionality that needs to be able to work together to be compatible between systems can do that. So it's just a quick snapshot of where we're headed. Thank you very much.