2a5f722f6e
The queries as they previously existed required joining together 12 different tables, which is extremely expensive. Splitting it into four queries means that the individual queries can effectively use the indexes we have, and should be very fast no matter how many statuses are in the database. Removing the .distinct() call is fine, since we're adding them to a set in Redis anyways, which will take care of the duplicates. It's a bit ugly that we now make four separate calls to Redis (this might result in things being slightly slower in cases where there are an extremely small number of statuses), but doing things differently would result in significantly more surgery to the existing code, so I've opted to avoid that for the moment. Fixes: #2725 |
||
|---|---|---|
| .github | ||
| bookwyrm | ||
| celerywyrm | ||
| contrib | ||
| dev-tools | ||
| locale | ||
| nginx | ||
| updates | ||
| .coveragerc | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.example | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierignore | ||
| .pylintrc | ||
| bw-dev | ||
| CODE_OF_CONDUCT.md | ||
| complete_bwdev.fish | ||
| complete_bwdev.sh | ||
| complete_bwdev.zsh | ||
| crowdin.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| LICENSE.md | ||
| manage.py | ||
| pytest.ini | ||
| README.md | ||
| redis.conf | ||
| requirements.txt | ||
| SECURITY.md | ||
| update.sh | ||
BookWyrm
BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Federation allows BookWyrm users to join small, trusted communities that can connect with one another, and with other ActivityPub services like Mastodon and Pleroma.
Links
About BookWyrm
BookWyrm is a platform for social reading. You can use it to track what you're reading, review books, and follow your friends. It isn't primarily meant for cataloguing or as a data-source for books, but it does do both of those things to some degree.
Federation
BookWyrm is built on ActivityPub. With ActivityPub, it inter-operates with different instances of BookWyrm, and other ActivityPub compliant services, like Mastodon. This means you can run an instance for your book club, and still follow your friend who posts on a server devoted to 20th century Russian speculative fiction. It also means that your friend on mastodon can read and comment on a book review that you post on your BookWyrm instance.
Federation makes it possible to have small, self-determining communities, in contrast to the monolithic service you find on GoodReads or Twitter. An instance can be focused on a particular interest, be just for a group of friends, or anything else that brings people together. Each community can choose which other instances they want to federate with, and moderate and run their community autonomously. Check out https://runyourown.social/ to get a sense of the philosophy and logistics behind small, high-trust social networks.
Features
Post about books
Compose reviews, comment on what you're reading, and post quotes from books. You can converse with other BookWyrm users across the network about what they're reading.
Track reading activity
Keep track of what books you've read, and what books you'd like to read in the future.
Federation with ActivityPub
Federation allows you to interact with users on other instances and services, and also shares metadata about books and authors, which collaboratively builds a decentralized database of books.
Privacy and moderation
Users and administrators can control who can see their posts and what other instances to federate with.
Tech Stack
Web backend
- Django web server
- PostgreSQL database
- ActivityPub federation
- Celery task queuing
- Redis task backend
- Redis (again) activity stream manager
Front end
- Django templates
- Bulma.io css framework
- Vanilla JavaScript, in moderation
Deployment
Set up BookWyrm
The documentation website has instruction on how to set up BookWyrm in a developer environment or production.