Things people have made.

Bots

A bot joins a server the way any other client does: its own key, its own certificate, and whatever an admin agreed to let it do. Nothing special happens on the server side.

• pingGrytOne file. A bot that joins, waits to be approved, and answers one command.→
• Support botGrytAnswers questions out of a JSON file and waves at people when they arrive. Ships with a Dockerfile and a compose file.→

Client addons

A theme is CSS. A plugin is JavaScript in a worker of its own, and what it can call is what you ticked when you turned it on.

• PaperGrytA warmer light theme, and forty lines of CSS showing which variables a theme should touch.→
• PresenceGrytPuts what you are playing under your name, and tells servers running the other half. The client side of a pair.→

Server plugins

These run inside the server process, with the database and the filesystem, and nothing contains them. Whoever runs the server installs one, and everybody who joins is told it is there.

• PresenceGrytThe server side of the same pair: keeps the roster and sends it to everybody who has the client half.→
• Crosspost guardGrytDeletes the same message when it lands in three channels inside a minute, and bans whoever does it twice.→

Getting yours on here

The list is one file in this site’s repository. Open a pull request adding your entry.

1. Link to source somebody can read. Not a download, not a landing page.
2. Say who made it. A person or a project — your own name is fine.
3. One line on what it does. What it does, not how good it is.

It works the same way whether you wrote a theme or a plugin pair. If you built something and aren’t sure it belongs, open the pull request anyway and we’ll talk about it there.