Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

PuddingBot/pudding-bot

Open more actions menu

Repository files navigation

Version

Activity Level Stability

Lines of Code Maintainability Rating Hits-of-Code

Maintainer time: Maintainer Hours

Contributor man hours: Contributor Hours

Pudding

Welcome to @PuddingBot, my AGPL3 licensed group management bot.

More information and a Docusaurus powered manual will be added at a later date.

Why not just use Rose?

There are certain things bothering me about the design philosophy of Rose that I seek to avoid.

  • It's closed source.

  • Rose never warns that a filter has already been set, instead replacing it silently.

  • Rose's anti-flooding is broken. It doesn't allow an admin to set the time frame between messages that are considered flooding, and the default setting isn't sensible.

  • "Disables" are non-admin only. There should be a functionality to disable parts of the bot entirely.

  • No way to query the reason a user was banned/muted. Rose support suggests running a log channel for that, which is additional hassle.

  • Some other gimmicks like conveniently displaying a chat's basic information (title, description, ID, @ and invite link) or querying the bot's uptime are absent.

About

Version 1 of my Rose Bot replacement (AGPL3)

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

Morty Proxy This is a proxified and sanitized view of the page, visit original site.