Janet's Shenanigans

Cafétera

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.

Unnamed Bot

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

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

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

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

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.

Why These Bots?

These bots are 100% open source. And 100% means 100%. They also did whatever job they were supposed to the best.

Why Not These Bots?

  • Valkyrja. I personally think YAGPDB has nicer configuration for a lot of things Valkyrja does. Mostly open source, but Valkyrja.secure is kept in a private repository, and it contains bot functions such as antispam. Not 100% open source. Additionally, the licenses can be somewhat conflicting. The website identifies itself as Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License, while the README for the website identifies the website as Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License, while the LICENSE file says the website is MIT. Pick a license, yo.
  • Mee6. Modern version is not open source, and barebones in useful features. Also the levels thing is annoying and a huge mistake. It serves no useful function to chat other than to get people to post messages to post messages rather than to actually chat.
  • Blargbot. BBTAG is what would happen if someone learned Lisp in a day, got lobotomized, and tried to recreate Lisp from scratch. Code is often unreadable and it cannot do many things.

Transparency helps allow a Discord guild to gain trust with everyone.

Principles

Informative

Transparency shows the history of your guild's leadership and allows users to see what they're dealing with.

Two-Way

Transparency allows users to become more comfortable about sharing useful criticism.

Usage

Moderation Actions

Transparency helps users become more aware of what will and what won't get them in trouble.

Status

Transparency provides timely feedback about the state of the guild.

Setup

Moderation Logs

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.

Audit Logs

Make these public. There's no reason not to. They were created for the sole purpose of being public. They can't be spoofed.

Community Involvement

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

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

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

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/.

Channel Organization

Channels should be organized in this order:

  • Welcome
  • Information, modlog, etc.
  • Webhook channels (news, github updates, etc)
  • Chat channels
  • Private channels