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: 4 (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.
This team has not published any reviews yet.
Instead of contacting us on IRC or Mastodon to get an account, you can now simply request it through a web form. Any user with moderator permission will be able to approve such requests as they come in. If you’d like to become a moderator, please don’t hesitate to reach out via lib.reviews@permacommons.org.
As with all web forms, we may have to tighten things a bit further if form spam becomes a problem, e.g., with a simple text CAPTCHA.
It’s pretty wild that we haven’t had this until now, but you can finally reset your password if you’ve lost it, provided you’ve configured an email address on your account.
To do so, simply visit: https://lib.reviews/forgot-password
To protect user privacy, the feature won’t tell you if an account exists for a given email address. To mitigate spam risk, it’ll also only send one token every 3 hours.
The main reason this wasn’t done sooner is that email is a bit of a pain to deal with. To mitigate against spam, it has to be carefully configured to pass SPF, DKIM and DMARC checks (various techniques used to ensure the email is legitimate). This in turn should reduce the risk of email landing in your spam filter.
We’re currently using the free Mailgun plan, which should work well while we’re small. Now that we have the first email feature, it will be a lot easier to add the next one, which will likely be the account request process (sending email to moderators to review/approve requests).
Every lib.reviews user can pass along account invitations once they’ve written their first reviews. These registration addresses look like this:
https://lib.reviews/register/<invite code>
Now, if you want to invite a friend to join and immediately also sign up to join a team you participate in, you can do so. Just pass along an invite like this:
https://lib.reviews/register/<invite code>?team=<some team>
For example, if you want to recommend they join the Vegans/Vegetarian team:
https://lib.reviews/register/<invite code?team=veg(etari)an
This will result in a sign-up page for them like this:
Sign-up page with vegetarian team preselected (Own work. License: CC-BY-SA.)
You can also offer multiple teams with ?team=<first team>&team=<second team>&team=<third team>, and so on. It’s a bit of an Easter Egg feature for now; in future, I hope to integrate it more with the team management tooling.
This is the first new feature for lib.reviews since the recent modernization work. It seemed only appropriate to start with a feature that was open as a pull request since (checks notes) 2018! Thanks to Patrick Noll for the original work on the idea.