feat: Add endpoints required for API-based takedowns and room bans #1301

Merged
nex merged 1 commit from nex/feat/admin-api-takedowns into main 2026-01-18 19:09:36 +00:00
Owner

Introduces a minimal API that will allow Draupnir and Meowlnir to issue room takedowns on continuwuity.

For people eager to see a full admin API, this PR does not introduce that, but only what is needed for the aforementioned need. The full API will take much longer to implement.

Adds:

  • PUT /_continuwuity/admin/rooms/{room_id}/ban
  • GET /_continuwuity/admin/rooms/list

Once merged, appropriate SDK implementations will be created.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
Introduces a minimal API that will allow Draupnir and Meowlnir to issue room takedowns on continuwuity. For people eager to see a full admin API, this PR does *not* introduce that, but only what is needed for the aforementioned need. The full API will take much longer to implement. Adds: - `PUT /_continuwuity/admin/rooms/{room_id}/ban` - `GET /_continuwuity/admin/rooms/list` Once merged, appropriate SDK implementations will be created. **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
nex added this to the 0.6.0 milestone 2026-01-18 18:49:29 +00:00
feat: Add endpoints required for API-based takedowns and room bans
All checks were successful
Update flake hashes / update-flake-hashes (pull_request) Successful in 25s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m27s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m53s
Documentation / Build and Deploy Documentation (push) Successful in 1m26s
Checks / Prek / Pre-commit & Formatting (push) Successful in 2m59s
Release Docker Image / Build linux-amd64 (release) (push) Successful in 9m50s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 37m21s
Release Docker Image / Build linux-arm64 (release) (push) Successful in 14m53s
Release Docker Image / Create Multi-arch Release Manifest (push) Successful in 29s
Release Docker Image / Build linux-amd64 (max-perf) (push) Successful in 16m54s
Release Docker Image / Build linux-arm64 (max-perf) (push) Successful in 17m10s
Release Docker Image / Create Max-Perf Manifest (push) Successful in 19s
Checks / Prek / Clippy and Cargo Tests (push) Successful in 38m52s
ebc8df1c4d
nex requested review from Owners 2026-01-18 18:50:09 +00:00
Jade approved these changes 2026-01-18 18:55:13 +00:00
nex merged commit ebc8df1c4d into main 2026-01-18 19:09:36 +00:00
nex deleted branch nex/feat/admin-api-takedowns 2026-01-18 19:09:36 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
Reference
continuwuation/continuwuity!1301
No description provided.