The idea is very similar, but I can't agree with a few implementation details: - The extension shouldn't need to have access to the page. Inserting an iframe into the page seems wrong. - The extension shouldn't own the comments. It should be a window to the comments, not a gatekeeper. It should be possible to implement alternative UIs and alternative extensions and connect them to the same comments. - The extension should allow to switch the UI and the data server.

I like the inline annotations, but likely it'll need full access to DOM.

I'm not intimately acquainted with the internal of hypothes.is but there is an open API, based on open standards. So you can build whatever you want with it.

I stopped using it as I moved to Firefox a year ago. More important, they didn't provide a link to download my data at least in that time.

All the data here is actually stored in indexedDb and localStorage. I guess I'll implement import/export next time.

This actually looks a lot cooler than the OP. :)

Edit: oh wait...chrome only

I think it's good. It's based on open standards, has a proactive and engaged organisation behind it and, crucially, a community of users.

Not to detract from the OP.

(Edit: It's an open standard. There are plugins for different browsers, a web interface and API)

There is a bookmarklet that works for firefox.