continuwuation/continuwuity
10
27
Fork 24
Code Issues 89 Pull requests 28 Projects Releases 18 Packages 3 Activity Actions

feat: Synapse compatible admin API #748

New issue
Open
opened 2025-04-14 21:05:59 +00:00 by Jade · 3 comments
Jade commented 2025-04-14 21:05:59 +00:00
Owner
Copy link

Obviously, we can't match all synapse endpoints fully. However, having some level of compatibility is useful.

Obviously, we can't match all synapse endpoints fully. However, having some level of compatibility is useful.
nex commented 2025-04-14 21:12:41 +00:00
Owner
Copy link

See also: https://github.com/nexy7574/conduwuit-admin-api-proxy/

Having our own rich API alongside a synapse compatible one would be the best of both worlds.

See also: https://github.com/nexy7574/conduwuit-admin-api-proxy/ Having our own rich API alongside a synapse compatible one would be the best of both worlds.
nex changed title from Synapse compatible admin API to feat: Synapse compatible admin API 2025-04-15 00:36:48 +00:00
nex added this to the 0.6.0 milestone 2025-06-18 16:38:55 +00:00
nex commented 2025-08-08 23:11:56 +00:00
Owner
Copy link

I don't think we should implement a synapse compatible API - things we need that aren't site-exclusive can be converted into an actual specced endpoint, and we can have our own private API for things specific to continuwuity.

I don't think we should implement a synapse compatible API - things we need that aren't site-exclusive can be [converted into an actual specced endpoint](https://github.com/matrix-org/matrix-spec-proposals/pull/4323), and we can have our own private API for things specific to continuwuity.
tcpipuk commented 2025-08-10 17:27:19 +00:00
Owner
Copy link

Big fan of starting off a spec'd API and letting Synapse look to adopt it, though I'd also say we take as much as is good/usable from the Synapse version as possible - we don't want to implement rubbish, but it'd be good to make it easier for them to adopt a centralised standard.

Hopefully part of the design would be that it's extensible (i.e. any homeserver can add more stuff that other servers aren't expected to support) so then we could just build our admin API under the same API tree instead of needing a second special /continuwuity/ tree? 🤔

Big fan of starting off a spec'd API and letting Synapse look to adopt it, though I'd also say we take as much as is good/usable from the Synapse version as possible - we don't want to implement rubbish, but it'd be good to make it easier for them to adopt a centralised standard. Hopefully part of the design would be that it's extensible (i.e. any homeserver can add more stuff that other servers aren't expected to support) so then we could just build our admin API under the same API tree instead of needing a second special /continuwuity/ tree? 🤔
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
nex/feat/provide-fast-joins
hydra/public
nex/feat/force-leave-room
renovate/actions-checkout-5.x
nex/feat/manual-extremities
tom/ci-fedora-rpm
illegal-car-mods
jade/dep-updates
jade/renovate-config-changes
renovate/termimad-0.x
renovate/cargo_toml-0.x
nex/fix/sync/leave-omission
renovate/toml-0.x
renovate/rand-0.x
renovate/nix-0.x
renovate/minicbor-serde-0.x
renovate/ctor-0.x
renovate/axum-client-ip-0.x
renovate/axum-monorepo
jade/rocksdb-10-5
nex/fed-improvements
tom/fixes
nex/feat/async-media
nex/feat/4277-harmonized-reporting-endpoints
nex/feat/fast-joins-hack-do-not-use-DO-NOT-USE
jade/musl-images
nex/feat/better-logging
trigger-ci-so-latest-isnt-on-illegal-car-mods
jade/parking_lot
jade/docs-updates-20250701
nex/fix/msc4307
nex/feat/pins-backfill
jade/upload-ci-binaries
jade/admin-command-docs
jade/tuwunel-2025-06
jade/tuwunel-2025-06-old
jade/ai-slop-db-docs
nex/fix-create-auth
jade/version-stats
jade/read-receipts
dahsa_uwu/axum-0.8
jade/rust-toolchain-no-targets
jade/logging-features
jade/syncv5-typing
jade/msc2815
jade/relations
jade/purge-sync-tokens
morguldir/see-eye
jade/css-small-screen
nex/wip-751
tuwunel-rebase
test
oddlid/rename-admin-room-bot
strawberry/nix-ci-stuff
strawberry/valgrind
strawberry/morgs-snake-sync-jason-main
newer-media-endpoints
folly-coroutines-async-io
federation-retry-timer-port
bad-attempt-at-extracting-homeserver-signing-key
room-deletion-attempt-do-not-use
v0.5.0-rc.7
v0.5.0-rc.6
v0.5.0-rc.5
v0.5.0-rc4
v0.5.0-rc3
v0.5.0-rc2
v0.5.0-rc
v0.4.7-rc
v0.4.6
v0.4.6-rc
v0.4.5-rc
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
Labels
Clear labels   
Bug

Something isn't working as intended

  
Cherry-picking

Commits picked from other conduit projects

  
Database

This requires or includes changes to the database

  
Dependencies

Something dependency related

  
Dependencies/Renovate

Automatic dependency upgrades by Renovate

  
Difficulty
Easy
Low difficulty to implement - touches few parts of the codebase, low complexity

  
Difficulty
Hard
High difficulty to implement - touches many parts of the codebase, high complexity

  
Difficulty
Medium
Medium difficulty to implement - touches more parts of the codebase, higher complexity

  
Documentation

Improvements or additions to documentation

  
Enhancement

New feature or request

  
Good first issue

Good for newcomers

  
Help wanted

Additional eyes and keyboards are required for this one

  
Inherited

Issues that have been inhereted from the project pre-fork

  
Matrix/Administration

Features pertaining to homeserver administration

  
Matrix/Appservices

Features pertaining to the appservice API

  
Matrix/Auth

Features pertaining to authentication

  
Matrix/Client

Features pertaining to client-to-server interactions

  
Matrix/Core

   
Matrix/Federation

Features pertaining to server-to-server interactions

  
Matrix/MSC

Features pertaining to unstable matrix features

  
Matrix/Media

Features pertaining to media interactions

  
Meta

Related to housekeeping, maintenance, or other repo-meta.

  
Meta/Packaging

Packaging

  
Priority
Blocking
This issue is blocking the next release

  
Priority
High
This issue is very important

  
Priority
Low
This issue is of a rather low priority

  
Security

This item is related to general security

  
Status
Confirmed

  
Status
Duplicate
This issue or pull request already exists

  
Status
Invalid
This issue doesn't seem right

  
Status
Needs Investigation
This issue needs further investigation

  
To-Merge

   
Wont fix

This will not be worked on

  
old/ci/cd

Ci/CD

Archived

  
old/rust

Pull requests that update Rust code

Archived

No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
Milestone
Clear milestone
No items
No milestone
0.6.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.

Dependencies

No dependencies set.

Reference: continuwuation/continuwuity#748
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?