A slack bot designed to make the lives of plural systems easier
Find a file
2025-07-17 22:06:42 +02:00
migrations feat(members): add the ability to delete/re-enable members 2025-06-23 17:12:12 +02:00
src feat: add ability to change base_url 2025-07-17 22:06:42 +02:00
.env.example feat: add ability to change base_url 2025-07-17 22:06:42 +02:00
.gitignore feat: initial commit 2025-06-08 21:12:07 +02:00
build.rs feat: initial commit 2025-06-08 21:12:07 +02:00
Cargo.lock docs: rename to plura 2025-06-23 18:20:24 +02:00
Cargo.toml docs: rename to plura 2025-06-23 18:20:24 +02:00
LICENSE chore: add LICENSE 2025-06-18 14:25:43 +02:00
README.md docs: update README 2025-07-01 11:22:42 +02:00
rust-toolchain.toml feat: initial commit 2025-06-08 21:12:07 +02:00

Plura

A slack bot designed to make the lives of plural systems easier. Inspired by PluralKit.

I'm not plural myself, but I do know a lot of Hack Club members that are plural and do want an easier way to differentiate between alters. Thus, I made this. It works similarly to PluralKit, by basically rewriting sent messages under different members using Slack's API.

Features

  • Manage members and profiles
    • Add, delete, edit, and get member information
    • Manage member aliases so your members are easier to refer to.
  • Send messages under different members
    • Triggers
      • E.g. Hi ~J to send a message under a user who is associated with the suffix ~J
  • Message actions for managing messages sent by members
    • Message editing
    • Message deletion
    • Message info (i.e. the profile of the member that sent it)
    • Message reproxying (i.e. sending a message under a different user after it's been sent)
  • Set and view information about a member

AI Usage in this project

(Required for Summer Of Making by Hack Club)

  • General autocompletion tooling (i.e. Zed edit predictions)
  • Initial draft of the merge_trigger_fields migration was done by AI
    • This also included editing matching structs
    • This has been refactored and edited by Suya1671
  • Initial draft of trigger commands was done by AI
    • Note that this has been completely redone and nearly no AI-generated code remains. Suya1671 remade triggers to have an entirely command based interface.
  • General code analysis was done by AI to make sure it's easier to understand and maintain the project
    • No code edits by an agent was done. Only suggestions which were implemented if seen fit by Suya1671