Bots that live in your channels

The smallest bot there is: it joins a chat room with its own key and answers !ping with pong. Twenty lines to start from.

1. member: !ping
2. hello bot
3. pong

The hello bot, with its code

Sits in your chat rooms, counts the members' messages, never a bot's, and every 5 seconds pushes the total to a public status channel, which any page can listen to without a token.

1. members
2. counter bot
3. status
4. every page

client_events although it never speaks: only members who may speak get the list that says who is a bot.

The counter, with its code Build it, step by step

The hero above: it counts each room's messages and celebrates the 1 000th, the 5 000th, the 10 000th, naming who sent it from the signed member data, with confetti on every member's page.

1. members
2. milestones bot
3. message 5000!
4. confetti

Milestones, with its code

Only numbers? Then no bot at all: no room, no connection, nothing for members to see. The server counts the messages in each channel, and a script on your backend with a stats key asks for them all at once with GET /channels?info=message_count, a page of up to 1 000 channels at a time. Works on Free.

1. GET /channels
2. your script
3. stats

Numbers without a bot, in the docs

Pikoman keeps no messages. This bot does, in your own storage, and when a member comes back it sends them what they missed, to them alone. The server tells it who the member is from the user id your backend signed.

1. room
2. history bot
3. your database
4. one member

The history bot, with its code

Runs the game: sends each question, takes answers sealed so no player can read another's, opens them when the time is up and keeps the score by its own clock. Pling, our live quiz on a TV with phones as buzzers, is built exactly this way, one bot per room, and opens on quiz.pikoman.se soon.

1. host
2. quiz bot
3. players

A simple quiz master, with its code Pling, on quiz.pikoman.se

Reads every message, filters words you choose and warns the sender alone. Someone who keeps on is removed from that room (kick), or removed and kept out for a while (ban, at most a day); the rest of their app keeps working. Each removal is told to your backend in a signed webhook, with the reason.

1. room
2. moderator
3. warning, kick or ban

kick and ban work only in the key's channels: this bot can do nothing in presence-admin. It needs no disconnect, which closes a whole connection, app-wide.

The moderator, with its code Moderation in the docs

A language model on your own server translates each message and the bot posts the translation beside it, so a room can talk across languages. Ten client events a second per connection: a busy room gets its translations in batches.

1. room
2. translator
3. your LLM
4. room

The translator, with its code

Speech to text while someone talks: the audio goes to Transcribe Today, and the bot publishes each line of text to a captions channel that the viewers' pages show. It never joins: it only publishes.

1. microphone
2. Transcribe Today
3. caption bot
4. captions-talk-7

The caption script, with its code Transcribe Today

Sits in your rooms and welcomes each person who joins, to them alone, with the names your backend signed: "Welcome, Ada! Bo and Cy are here." Someone who was there before gets "Welcome back". The example is ready and tested.

1. member_joined
2. greeter
3. the new member

Not in the room: a member_added webhook and a publish key do the same from your backend.

The greeter, with its code

Deals the cards and keeps the moves hidden: each player gets their own hand, sent to them alone, and the bot decides what everyone sees. Players see that the dealer is a bot, and with which key, from the server, not from anything a player could write.

1. player's move
2. game bot
3. each player alone

Presence in the docs

!poll Pizza or tacos? and the room votes: one vote per person, however many tabs they have open, and the result when the time is up.

1. !poll …
2. poll bot
3. votes
4. result

The poll bot, with its code

!timer 5m Coffee, and the room hears it when the time is up. Stand-ups, breaks and game rounds, kept by the bot's own clock.

1. !timer 5m
2. timer bot
3. ⏰ Coffee

The timer bot, with its code

Each push to GitHub on your team's page as it happens. A small server checks GitHub's signature and publishes; a request without a valid one publishes nothing.

1. GitHub
2. relay
3. updates
4. team page

The relay, with its code

One message to everyone at once: maintenance tonight, a new release, the stream starting. Every page listens to one public channel, and a key that may publish there and nowhere else sends it.

1. your script
2. announcements
3. every page

The script, with its code