Social reading and reviewing, decentralized with ActivityPub
Find a file
Hugh Rundle 8d593e4498 hide replies to posts user cannot see
This is in response to #1870

Users should not see links to posts they are not allowed to see, in their feed. The main question is how to stop that happening.
This commit hides all replies to posts if the original post was "followers only" and the user is not a follower of the original poster. The privacy of the reply is not considered relevant (except "direct").

I believe this is the cleanest way to deal with the problem, as it avoids orphaned replies and confusing 404s, and a reply without access to the context of the original post is not particularly useful to anyone. This also feels like it respects the wishes of the original poster more accurately, as it does not draw attention from non-followers to the original followers-only post.

A less draconian approach might be to remove the link to the original status in the feed interface, however that simply leads to confusion of another kind since it will make the interface inconsistent.

This commit does not change any ActivityPub behaviour - it only affects the Bookwyrm user feeds. This means orphaned posts may be sent to external apps like Mastodon.
2022-08-14 14:17:10 +10:00
.github Settings 2022-07-07 11:37:34 -07:00
bookwyrm hide replies to posts user cannot see 2022-08-14 14:17:10 +10:00
celerywyrm Adds auto-create queues option to config 2022-03-17 09:57:25 -07:00
dev-tools Updates node to version 18 2022-07-26 15:07:40 -07:00
locale Locales update 2022-08-05 09:04:26 -07:00
nginx Adds block to prod config 2022-07-15 13:19:42 -07:00
updates Adds celerybeat update script 2022-03-16 12:53:27 -07:00
.coveragerc [lint] Fix missing new lines. 2021-03-04 18:44:36 +01:00
.dockerignore [lint] Fix missing new lines. 2021-03-04 18:44:36 +01:00
.editorconfig Add specific vendor file 2021-08-23 13:59:23 -07:00
.env.example Much shorter search timeout 2022-08-04 12:16:12 -07:00
.eslintignore [assets] Move some frontend assets to _vendor_ directories: 2021-04-05 16:17:11 +02:00
.eslintrc.js [assets] Document functions and variables: 2021-04-06 16:17:20 +02:00
.gitignore Updates .gitignore for themes 2022-02-28 09:37:51 -08:00
.prettierignore .prettierignore to vendor 2022-02-28 21:23:44 -08:00
.pylintrc Adds line length and import-error to .pylintrc 2022-07-02 10:50:17 -07:00
bw-dev Removes compilescss command 2022-08-07 11:27:52 -07:00
CODE_OF_CONDUCT.md [lint] Fix indentation in .md files. 2021-03-04 19:05:01 +01:00
complete_bwdev.fish Removes compilescss command 2022-08-07 11:27:52 -07:00
complete_bwdev.sh Removes compilescss command 2022-08-07 11:27:52 -07:00
complete_bwdev.zsh Removes compilescss command 2022-08-07 11:27:52 -07:00
crowdin.yml Update Crowdin configuration file 2021-10-06 21:50:47 -07:00
docker-compose.yml Pylint fixes 2022-07-02 12:07:22 -07:00
Dockerfile Go back to one requirements.txt, simplify workflow 2022-06-05 14:57:42 -07:00
LICENSE.md Rename License with a .md extension. 2021-04-28 16:05:12 +02:00
manage.py Updates migrations 2020-09-21 08:10:37 -07:00
pytest.ini Updates tests env 2022-01-09 12:04:45 -08:00
README.md Update README.md 2022-07-11 15:55:17 -07:00
redis.conf Use redis with password in dev 2022-01-05 08:52:28 -08:00
requirements.txt Updates and fixes opentelemetry install 2022-08-04 11:05:18 -07:00
SECURITY.md Create SECURITY.md 2022-06-30 05:46:41 +01:00
update.sh Adds missing update script 2022-03-16 13:32:37 -07:00

BookWyrm

Run Python Tests Pylint

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.

Mastodon Follow Twitter Follow

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 thier posts and what other instances to federate with.

Tech Stack

Web backend

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.