Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add reason why the archive bot is joining the room #262

Merged
merged 9 commits into from
Jun 9, 2023
10 changes: 5 additions & 5 deletions docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,15 +19,15 @@ messages from any given date and day-by-day navigation.

## Why did the archive bot join my room?

Only public Matrix rooms with `shared` or `world_readable` history visibility are
Only public Matrix rooms with `shared` or `world_readable` [history
visibility](https://spec.matrix.org/v1.6/client-server-api/#room-history-visibility) are
MadLittleMods marked this conversation as resolved.
Show resolved Hide resolved
accessible in the Matrix Public Archive.

But the archive bot (`@archive:matrix.org`) will join any public room because it doesn't
know the history visibility without first joining. Any room without `world_readable` or
`shared` [history
visibility](https://spec.matrix.org/v1.6/client-server-api/#room-history-visibility)
will lead a `403 Forbidden`. And if the public room is in the room directory, it will be
listed in the archive but will still lead to a `403 Forbidden` in that case.
`shared` history visibility will lead a `403 Forbidden`. And if the public room is in
MadLittleMods marked this conversation as resolved.
Show resolved Hide resolved
the room directory, it will be listed in the archive but will still lead to a `403
Forbidden` in that case.

The Matrix Public Archive doesn't hold onto any data (it's
stateless) and requests the messages from the homeserver every time. The
Expand Down