Suspicious users

Some accounts arrive with a history. Twitch runs its own ban-evasion detection and will tell a channel it moderates when it thinks a returning account belongs to someone you already banned. Pyre surfaces that where you are actually looking, which is the chat line itself, and keeps it so the next person to look has the history rather than a blank card.

One line governs the whole feature, and it is printed on the card:

A flag is a note to your mods, never a claim about a person.

The two badges

A flagged message carries a coloured edge and a small label. There are two, and Restricted outranks Monitored:

Badge	What it means
Monitored · possible ban evader	Twitch is watching this account and thinks it is worth your attention. The tail changes with Twitch’s own confidence: likely ban evader, possible ban evader, or nothing at all when it will not say
Restricted · only mods see this	The account is under restriction. Your viewers never saw this message

Badges appear in two places: the merged feed in Pyre.Chat, and the My chat card in Stream Manager. They are for moderators, and the server strips them before a message reaches anything else. Your overlays, the public chat relay and any viewer facing surface get an ordinary, un-annotated copy of the same line. There is no setting for this and it is not something you can turn on.

A restricted account's messages exist nowhere else

When Twitch restricts an account, its messages stop arriving in normal chat entirely. Nobody sees them: not your viewers, not you, not another bot. Pyre injects them into the moderator view as their own rows, so the moderator view is the only place those messages are readable at all. Close it and they are gone again.

The user card

Click the name on a flagged message and the card carries a block the ordinary card does not:

• The treatment as a fact, in plain words: Monitored. Watches quietly. or Restricted. Hidden from your viewers until a mod clears them.
• What Twitch says, one line each: Likely ban evader., Possible ban evader., Banned in 3 channels you share bans with., or, when Twitch offers no verdict at all, Flagged for review.
• Flag history, every earlier flag Pyre recorded for this identity, newest first, with the date and what raised it.

Because the flags are stored rather than held in memory, the history survives a reconnect, a restart and a new browser. A card you open three weeks later still shows what happened three weeks ago.

The card does not say who set the treatment

Twitch’s data carries the status but not the moderator who applied it, and Pyre does not invent one. The card tells you what the treatment is and when each flag was recorded, and stops there.

Twitch’s verdicts and Pyre’s own flags

Two things write to the same history, and the labels tell you which is which:

In the history	Where it came from
Twitch flagged a ban evader	Twitch’s ban-evasion detection
Twitch: banned in a channel you share bans with	Your shared ban list
Twitch: added by a moderator	Somebody on your team marked them by hand
Twitch flagged this account	Twitch flagged it without saying why
Pyre: matched a follow-bot pattern	Pyre’s own follow-bot ladder, not Twitch

Everything on the first four rows is Twitch’s judgement, passed through. The last row is Pyre’s, and it comes from the same ladder described in Protection: an account that was young or arrived in a follow burst, but not both, is flagged rather than blocked, and the flag lands here.

Monitor, restrict and clear

The card carries three buttons, and they do what Twitch’s own tools do:

1. Monitor puts the account under active monitoring. Nothing changes for your viewers. Their messages arrive as normal and carry the badge for your mods.

2. Restrict hides them. From that point their messages reach the moderator view and nowhere else, until somebody clears it.

3. Clear removes whichever of the two is in force.

The same three exist as chat commands, for the mod who is already typing:

Command	What it does
!monitor <user>	Puts a viewer under monitoring so their messages are flagged for mods
!restrict <user>	Restricts a viewer so only mods see their messages
!unrestrict <user>	Clears the monitoring or restriction

All three are moderators and above, and they are silent for anyone below rather than answering with a refusal. The bot confirms what happened, because a mod who typed !restrict cannot tell from silence whether it worked:

petra is now restricted.

Twitch only, and the owner's channel only

The whole feature rides Twitch APIs, so a flagged account on Kick or YouTube is not a thing that can exist. On a non-Twitch message the card says so: Monitor and Restrict are available on Twitch only.

The buttons also act on your own channel. A moderator using Pyre.Chat sees the flags on the channels they are entitled to see, but the monitor and restrict actions are not yet wired to a delegated channel, so the buttons are the channel owner’s in this version. The chat commands are the route for a moderator today.

Related

• The viewer card and chat history for everything else the card shows, and who is allowed to read it.
• Protection for the follow-bot ladder that writes the Pyre flags.
• Moderate from the feed for the ordinary delete, timeout and ban actions.