Barista now has two stunning new features: You can edit commands and Barista will apply them! How cool!
Barista can also quote things now and let you reply to them.
Run sudo help in the bots channel to see!
There was also a lot of tidying in the backend, making commands easier to write.
Cafétera looks like a single bot from a first glance, but in reality, it's actually multiple bots.
The reason why we use multiple bots instead of a single bot is because one bot cannot be the best at everything. The saying goes: “Jack of all trades, master of none.”
So, here are the bots bringing work to you in the background.
This bot provides most of the Linux Cafe-specific functionality. They'll run bash commands, search distro packages, manage profiles and screenshots, and some other things. You can find their source at linux-cafe/unnamed-bot on GitHub.
Red, they're a pretty cool bot. They have a very extensible system, but the only extension they have active is one to provide swingin' tunes in the nightclub. Their source is at Cog-Creators/Red-DiscordBot on GitHub.
Discord.RSS is a busybee. They don't look up from their job of sifting through hundreds of RSS posts a day (mostly Arch Linux package updates). They keep on posting. You'll find their source here at synzen/Discord.RSS on GitHub.
YAGPDB loves helping the moderation team. It's all they really do. They'll keep the modlog working to keep that transparency at 100%. They also offer rolemenus, but that's super trivial for them compared to their job of moderation. Their source is at jonas747/yagpdb on GitHub.
Maiden Voyage spends most of her time carrying messages between different services. She allows people to communicate on a fully free platform with a community backed by fully free bots. She's an instance of 42wim/matterbridge on GitHub.
These bots are 100% open source. And 100% means 100%. They also did whatever job they were supposed to the best.
Transparency helps allow a Discord guild to gain trust with everyone.
Transparency shows the history of your guild's leadership and allows users to see what they're dealing with.
Transparency allows users to become more comfortable about sharing useful criticism.
Transparency helps users become more aware of what will and what won't get them in trouble.
Transparency provides timely feedback about the state of the guild.
These should offer feedback to users about current moderation actions. Deleted messages, nickname changes, etc. are not moderation actions and should not be logged in a moderation log.
Make these public. There's no reason not to. They were created for the sole purpose of being public. They can't be spoofed.
The community should be able to see the brains of the server. Ask yourself what good reason is there to hide leadership discussion from the community. Controversial decisions they won't like? Just kicking the can down til later. Boring? So is the modlog. Whatever reason you have, it's probably invalid.
You should poll the community's thoughts on the server from time to time. Member counts are useless, retention and opinion are useful.
This is the first post on here, so welcome I guess. This is basically where I'll make random posts related to running a Discord server.
Channels should be: – Distinct. Do not make multiple channels that are close or identical in topic. – Purposeful. Do not make channels just because you feel like it. They should serve a purpose of conversation. Do not be afraid to trim unused channels. – Topical, but not overly specific.
Channel names should be:
– Related to their topic. Good: #linux-customization. Bad: #channel-7
– Self explanatory. Good: #linux-customization. Bad: #unix-porn.
– Concise. Good: #sysadmin. Bad: #system-administration-chat
– Non-thematic. Good: #support. Bad: #man-pages. Note: you can tweak word choice to add a bit of flair, but you should retain the self explanatory aspect.
A good format is a single noun, plus a second word to clarify if needed. For example: #support, #support-type.
Category names should be: – Short. One word at the most. Any more is excess. – Nouns. Good: Contribution. Bad: Contributing. – Emoji-free. – Non-thematic. Good: Chat. Bad: /var/.
Channels should be organized in this order: