Open ChurchOfTheSubgenius opened 8 months ago
Thanks.
This looks great; very helpful for comparing/contrasting the codebases.
This looks great; very helpful for comparing/contrasting the codebases.
Indeed, The code is as stupidly simple as it can be except for the UIA bypass. It might be possible to move that up to the router as a middleware.
What are we doing at sync
? I'm sure this requires some extra work on the router level.
A few comments:
Update Display Name/Avatar
should have an optional /:room_id
suffix for room-specific membership changes.
Fetch all events
isn't supposed to expose all server events including or is it? We might be able to allow users to share i.e. threads by marking them as public.
I'm listing out all the API coverage on both the existing golang backend and the rust server. This list should help us understand where we're at regarding reaching feature parity with the golang backend.
POST /account
POST /login
GET /logout
GET /account/session
POST /account/token
POST /account/password
POST /account/password/verify
POST /account/password/reset
POST /account/password/update
POST /account/verify/code
POST /account/verify
POST /account/verify/email
POST /account/display_name
POST /account/avatar
GET /username
GET /email
Get /feed
GET /notifications
GET /notifications/sync
POST /notifications/read
GET /discover
GET /public_spaces
GET /media/presigned_url
GET /media/upload_url
GET /gifs/search
GET /gifs
GET /link/metadata
GET /events
POST /event
POST /event/state
POST /event/redact
POST /event/redact/reaction
PUT /event/upvote
PUT /event/downvote
GET /room/{room_id}/messages
GET /room/{room_id}/sync
GET /room/{room_id}/members
GET /room/joined
POST /room/join
POST /room/leave
POST /room/join
POST /room/{room_id}/invite/{user_id}
POST /space/{space}/join
POST /space/{space}/leave
POST /space/create
POST /space/room/create
GET /space/emoji
GET /{space}/events
GET /{space}/{room_id}/events
GET /{space}/state
GET /{space}/power_levels