scct federated backend server
Find a file
2024-08-28 10:29:07 +02:00
migrations persisting messages as incoming to one global chat and each connection being a new user 2024-08-12 19:44:38 +02:00
model sending chat history on request work in progress 2024-08-12 20:50:45 +02:00
server trying to wrap client connections in a wrapper struct 2024-08-28 10:29:07 +02:00
.editorconfig chore: project setup 2024-06-21 18:02:06 +02:00
.gitignore persisting messages as incoming to one global chat and each connection being a new user 2024-08-12 19:44:38 +02:00
.rustfmt.toml chore: project setup 2024-06-21 18:02:06 +02:00
Cargo.lock persisting messages as incoming to one global chat and each connection being a new user 2024-08-12 19:44:38 +02:00
Cargo.toml persisting messages as incoming to one global chat and each connection being a new user 2024-08-12 19:44:38 +02:00
main.rs persisting messages as incoming to one global chat and each connection being a new user 2024-08-12 19:44:38 +02:00
README.md docs: reamde 2024-06-21 21:01:03 +02:00

scct backend

tldr:

  • no capnproto
  • no http framework
  • C2S is a stream
  • S2S is packet based broadcast
  • probably use tungstenite for web clients
  • can we have better streams for mobile/desktop?
  • sea_orm and sqlx are huge but ehh db flexibility is nice feature
  • i have no clue honestly
  • super cool chat thing yayyyyyyyy