lib.reviews now detects edit conflicts: It warns you if someone else updated the content you were working on, and suggests you check the latest version before accidentally overwriting those changes.
Very few aspects of lib.reviews support true collaborative editing so far (review subject descriptions for one), but in principle you could conflict with yourself (e.g., due to having two tabs open while editing the same review), and that is detected through the same mechanism.
The Data Access Layer that powers lib.reviews is now its own GitHub project, rev-dal. The DAL is the interface between the web app (what you interact with) and our PostgreSQL database.
The “rev” stands for “revisions” — one thing that characterizes most data in lib.reviews is that it’s versioned and supports multi-author collaboration in principle.
We’ve started using this DAL for another project, AGPWiki, so it made sense to pull it out of the lib.reviews monolith.
This should have no user-facing impact whatsoever, but if anything suddenly throws up weird new errors, please do let us know.
To make review feeds easier to scan through, reviews (except super-short ones) are now collapsed by default with a “Read more” link. I’m sure the UX for this could be improved, so don’t hesitate to open an issue or ping us on Mastodon if you have thoughts or ideas in that respect. Shout-out to Nortix and Enigma for the initial discussion about this change.
(Happy new year! Aiming for federation in 2026! :-)
We develop the lib.reviews platform. That’s both server-side and client-side code and design (!), as well as any additional tools, apps, etc. If you’re technically minded but want to help more with docs, developer outreach, user needs analysis, you’re also more than welcome to join.
For now we use this team primarily to keep a diary of our work.
Number of members: 5 (view list)
Number of reviews: 0
Moderators:
You agree to license all technical contributions under CC-0 (public domain); see: https://creativecommons.org/publicdomain/zero/1.0/
We’ve opted for these terms for our codebase to make re-use and extension minimally complex.