The first hour decides

Mass Reactions

Put reactions on new posts or on the first comments under them, spread out over time like a real audience. Setup, the limits that matter, and dry run.

01What it does

Mass Reactions watches your target channels. When a new post appears, accounts from the reactions pool put reactions on it, or on the first comments under it, spread over the next minutes and hours the way a real audience reacts.

By default it reacts to comments, not to the post: a lively comment section makes a post look read.

Mass Reactions Module control: Running, the Dry run switch, and Stop. — Module control with the Dry run switch.

Dry run is on for a new setup. In dry run the module does everything except the send: it catches posts and plans which account reacts with what and when. Nothing reaches Telegram until you switch Dry run off.

02Set it up

Add accounts to the Reactions Pool. An account works in one module at a time. Accounts younger than 3 days never react.
Channels: paste @channel or t.me links, one per line, and press Add. Your own channels are the safest targets.
Check each tile. Not checked yet, no comments (no discussion group) or reactions off means comment mode cannot work there. Check discussion groups runs the check again.
What to react to: Comments (default, the first 3 comments under each post) or Channel posts.
Emoji: keep the default four (👍 ❤ 🔥 👏) unless you know the targets allow others.
Leave Limits and Pacing at their defaults.
Keep Dry run on, press Start, and read the engine log for a while. If the plan looks natural, switch Dry run off.

Mass Reactions Channels: 9 targets configured, buttons Check discussion groups, Clear all and Save preset, a paste box with Add, target tiles each showing “0/6 joined”, and saved Presets with Load buttons. — Targets. Each tile shows how many pool accounts have joined its discussion group.

Presets save the target list under a name; Load puts it back.

03Limits

Mass Reactions Limits: Per hour, Per day, Per channel per day, Per account per run fields, the “Chance a message gets reacted to at all” slider at 50%, the “Share of the pool per covered message” sliders at 35–65% with the number of accounts, and the “Skip messages that already have reactions” switch. — Limits. The line next to the share shows how many accounts that means for your pool.

Setting	Default	What it does
Per hour	4	Most reactions one account places in an hour, across all targets.
Per day	20	Most reactions one account places in a day.
Per channel, per day	8	Most reactions one account places on one channel in a day.
Per account, per run	200	Hard ceiling for one account in one run.
Chance a message gets reacted to at all	50%	Some messages get nothing, as with a real audience.
Share of the pool per covered message	35–65%	How much of the pool reacts to a message that is covered. A new value is drawn for each message.
Skip messages that already have reactions	Off	Leaves alone messages that already have more reactions than the number you set.

On a channel you do not administer, at most 35% of the pool reacts to one message, whatever the share is set to: that channel’s admins can see exactly which accounts reacted.

04Pacing

Mass Reactions Pacing: First reaction after a post appears 60–600 seconds, Spread window 90 minutes, Arrival curve Human — front-loaded, Gap between one account’s reactions 30–120 seconds, Pause after a FloodWait 120 seconds, FloodWaits before quarantine 3, and Fast, Recommended and Slow presets. — Pacing with the recommended values.

Setting	Default	What it does
First reaction after a post appears	60–600 s	The earliest a reaction may land. Never instant.
Spread window	90 min	How long all reactions for one message are spread over.
Arrival curve	Human — front-loaded	Most reactions early, fewer later, like real posts. Uniform spreads them evenly, which looks mechanical.
Gap between one account’s reactions	30–120 s	Minimum time between two reactions of the same account.
Pause after a FloodWait	120 s	How long an account waits when Telegram asks it to slow down.
FloodWaits before quarantine	3	After this many FloodWaits in a row the account stops until you clear it.

The Fast, Recommended and Slow buttons fill the timing fields; Save applies them. A reaction that would land on a post older than 4 hours (after a delay or restart) is cancelled instead of sent late.

05Joining

To react to comments, an account must be a member of the channel’s discussion group, so accounts join first. The engine joins one account at a time and then waits 3 to 10 minutes before the next. With many accounts, joining a new target takes hours, and reactions in comment mode ramp up as the joins finish. The tile shows the progress (for example, 4/6 joined).

React without joining cannot be switched on: Telegram does not allow reactions in a discussion group from a non-member. Reacting to channel posts needs no joining.

06AI Protection

The AI Protection block under Control. Here the level is the chance that an account browses a little on the same connection before it reacts: Low about 1 in 4 reactions, Medium every other one (default), High almost every one. Off: accounts only react.

More: AI Protection across the modules.

07Statistics

Statistics shows accounts, targets, posts and reactions queued, then Total Attempts, Successful, Unsuccessful and Success Rate, and one row per account. A cancelled reaction (for example, for a deleted post) is not an attempt and does not lower the success rate.

08Common mistakes

Switching Dry run off before reading the plan.
Using emoji a target does not allow. Every such reaction fails; keep the default four or check the targets.
Targets with no comments or reactions off in comment mode. Nothing can land there.
Expecting all accounts to react right away on a new target. They join one by one, over hours.
Raising Per hour to get more reactions. Add accounts instead; a fast account looks like a script.

Start of the chain: buying accounts →