Social Annotation Powered by Matrix
Populus-Viewer is a tool for decentralized social annotation, built on pdfjs, wavesurfer.js and the Matrix protocol. You can use it to read PDFs, listen to audio, or watch videos, and have rich discussions in the margins, with your friends, classmates, or scholarly collaborators.
Each uploaded file is attached to a matrix space, and each annotation to the file becomes a room within that space. Populus-Viewer has been tested with synapse and dendrite, but should be compatible with any spec-compliant matrix server.
To learn more or talk about the project, find us on Matrix. The project should currently be considered beta-quality. UX is unpolished, bugs are likely, and features are missing. Bug reports and feature requests are welcome.
recording.mp4
Populus-Viewer currently supports:
- Highlight and pin-drop annotations on PDFs
- Timespan annotations on audio and video files
- Annotating spatial regions of images and video files
- Audio and video messages
- Message edits and redactions
- Replies and reactions
- Unread message counts
- Markdown for text formatting (via commonmark.js)
- LaTeX for mathematical notation (via KaTeX)
- Integration with bots
- Typing notifications
- Room invitations
- Synchronized reading positions across devices
- Single Sign On (via Google, university, or another SSO provider), given a matrix server that supports it
If there's a feature supported by Matrix that you think would make for a better social annotation experience, please open an issue or a PR!
Populus' annotations are stored on your Matrix server in a format compatible with the w3c Web Annotation Data Model. The details are documented in a couple of related matrix spec proposals:
- MSC3775: Markup Locations for Audiovisual Media
- MSC3752: Markup locations for text
- MSC3592: Markup locations for PDF documents
- MSC3574: Marking up resources
To try out Populus-Viewer, just point your browser at our github pages instance. You're welcome to use the default testing server, but be aware that this server may be torn down or replaced at any time. Also, be aware that the testing server isn't federated, so it won't be possible for users on other servers to join your discussions or vice-versa. We may consider running a larger public instance in the future once client development is further along.
To get started tinkering with the source code, clone this repository and then run:
npm installto download dependencies and install them locally.npm run-script buildto build the browser JS, which will end up in thedistdirectory.npm run-script serveto serve the contents ofdistat localhost:9000, and auto-reload on changes.
Similar projects include:
But I couldn't resist trying something new :)