-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve mod commands #39
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concerns noted inline
Sanity checking myself: you meant prefix, right? |
nope. names are usually seen as "cblgh" or whatever. but suffix = after, prefix = before |
Oh, I see the confusion: you meant suffix with respect to the displayed name. I meant prefix with respect to how we're showing the beginning of the pubkey in the nick. Gotchya. 👍 |
fyi I'm working on this PR: bubbling up cabal-core state into |
also tests! and other misc spot improvements.
OK! So now Next up is listening to |
…rking yet, others TODO'd
updated to track the latest set of commands[1] with the cabal-core flags implementation[2] |
(and some race condition/state fixes)
The |
This now also depends on cabal-club/cabal-core#90 |
fixes a bunch of edge cases, including users with . in their name
this pr fixes a bunch of stuff from #38, and relies on cabal-club/cabal-core#80. it adds a lot of minor features like
/ban troll.b33f
or/mod add substack.1337
msg.value.content.banned
exists to see if you are processing a banned messagepeers that are banned, or hidden, also have their content purged. it's just a (temporary!!) hack inside cabal-client, but felt way nicer to actually use :) (the peer's name isn't affected though)