pep
/
muchrooms
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
XMPP MUC (0045) implementation in Rust
103 Commits 4 Branches 0 Tags 358 KiB
Rust 100%
Go to file
Maxime “pep” Buquet 4366ae116a
Remove unnecessary clones 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
 		2023-10-26 18:11:01 +02:00
src Remove unnecessary clones 2023-10-26 18:11:01 +02:00
.editorconfig Add .editorconfig 2022-12-28 10:32:43 +01:00
.gitignore Initial commit: Users can join! 2022-09-07 20:08:27 +02:00
.woodpecker.yml CI: try moving clippy in testing stage 2022-12-27 09:19:46 +01:00
Cargo.toml Update xmpp (tokio-xmpp, jid) deps 2023-10-26 00:48:24 +02:00
LICENSE Add README.md and LICENSE 2022-09-12 23:06:15 +02:00
README.md README: Add note about MUC/Companion burner JID 2023-06-06 23:56:40 +02:00
rustfmt.toml Set hard_tabs = true in rustfmt 2022-12-28 10:13:30 +01:00

README.md

Muchrooms

This is a MUC component implementation in Rust.

The primary goal was to be able to write gaming chat rooms for the online (board) games, but it is growing into a more complete implementation.

The name is pronounced “mushrooms”.

License

This project is available under the AGPL-3.0-or-later license. See the LICENSE file.

Checklist

XMPP

  • Join
    • Normal sessions
    • MSN
  • [-] Presence
    • Resync
    • Updates
    • [-] Probes (storing updates to answer probes)
      • Storing presences but not answering when they're being queried, yet.
    • Nick changes
  • [-] Iq
    • [-] Ping answers
      • Ping component (always succeeds)
      • [-] Ping room (always fails. Awaiting affiliation support)
      • Ping participant (0410)
    • Ping probes?
    • Routing Public PEP?
    • Default "service-unavailable"
  • Messages
    • Broadcast
    • History?
    • MAM?
  • [?] Leave
  • Affiliations / roles
  • Configuration
    • Modes
      • Non-anon
      • Semi-anon
      • Full-anon? (with some kind of occupant-id (0421)?)
  • Mediated invites
  • Room state
    • Locked
    • Destroyed / Tombstoned?
  • Private Messages?
  • Possible optimisations
    • Presence versioning (0436)
    • Room Activity Indicator (0437)
    • Affiliation versioning (0463)
    • Caching participant caps

Storage

  • Persistent storage of room data

Component Configuration

  • Interface
    • File?
    • Adhoc?
  • Options?
    • Host
    • Secret
    • Admins?
    • ...?

To Think About

https://logs.xmpp.org/xsf/2023-01-05?p=h#2023-01-05-fe0286ff34b3de39

A MUC could pretend to be non-anon and give out burner JIDs at a companion service