Publishing and moderation

New! Review mode

_{Direct or Expert tariffs}

A long-awaited feature that allows you to manually edit posts from the source before publishing them in the destination. It also allows you to manually approve posts for publication or skip them. We call this review mode or moderation mode. How does it work?

Create a new forwarding
Enable review mode on the source

Where to find

Menu → My forwards → Select source and destination → Publishing → Review mode → ON

3. Now, for each new post in the source, your connected account will send a copy of this post to a special bot @Junction_Review_Bot. Under such a post there will be information about the source and destination, and the buttons "Publish" and "Skip".

4. Since the post is published on behalf of your account, you can edit it directly in the chat with @Junction_Review_Bot.

5. If you want to publish the resulting post in the destination, click the "Publish" button.

To disable moderation mode, use the same menu section

‍

Moderation in the group

You can also send posts to the group for approval.

To do this, use the setting Menu → My forwards → Select source and destination → Publishing → Group review.

Note that @Junction_Review_Bot and your connected account must be admins in this group.
The group number must be specified in the TgID format. That is, it must be a negative number, sometimes starting with -100. For example, if your group number is 4019780662, then its TgID will be -4019780662 or -1004019780662.
If the above conditions are not met, you will receive a NO_ACCESS error.

‍

PLEASE NOTE:
‍
- You can still use any replacements and filters on the redirect. They will be applied before sending the post for moderation.

- You can use the "Publish" button as many times as you like. Each time, the system will publish the current version of the post in the destination.

- Enabling moderation mode automatically enables publishing on behalf of your account (copying). This means that the connected account must have publishing rights in the destination. It also means that the buttons from the original post will not be transferred.

- Editing from the source to the destination is not automatically transferred.

‍

Delivery modes

_{Direct or Expert rates}

Publishing on behalf of the bot / connected account

Junction Bot can publish messages both on behalf of the @junction_bot bot itself and on behalf of your connected account.

Publishing on behalf of an account may be relevant if you are forwarding to a group. Then messages will come not on behalf of the bot, but on behalf of your connected account (everyone will see your username and profile picture).

When you set up forwarding to users' personal chats and to other bots, messages will be automatically sent on behalf of your connected account. In this mode, you do not need to add the bot to the destination chat.

‍

Copying / forwarding

Also, when working through a connected account, two types of forwarding are possible - through the built-in Telegram forward mechanism, or copying the message.

PLEASE NOTE!
‍
- When using a forward, it is impossible to change the message in any way (add your own text, use replacements, etc.).
‍
- The views of a copied message are counted separately and do not affect views of the message from the source. Views of a forwarded message affect views of the message in the source.

‍

Where to find

Menu → My forwarding → Select source and destination → Publication → Delivery mode

Mode ^{Copy via bot} - messages will be copied and published via the @junction_bot bot. The bot must be an admin in the destination and have publishing rights there.

^{Copy via account} mode - messages will be copied and published via the connected account. The account must have publishing rights in the destination.

^{Copy via account, in case of flooding - via bot} mode - messages will be published via the connected account. The account must have publishing rights in the destination. If the Telegram limit on the number of published messages is exceeded, an attempt will be made to publish via the @junction_bot bot. For this to work, the bot must be an administrator in the destination and have publishing rights there.

^{Forward via account} mode - messages will be forwarded (using forward) through the connected account, while maintaining a link to the original message. The account must have publishing rights in the destination. The source must allow forwarding messages.

^{Forward via account, if disabled - copy via account} mode - the bot will try to forward messages on behalf of the connected account (while maintaining a link to the original message). If the source has a forward ban, the message will be copied and published on behalf of the account.

‍
In the ^{Copy via account} and ^{Forward via account} modes:
— There is no need to keep the bot in the destination chat.
— Adding buttons to the message is not supported. The buttons will not be displayed.

‍

Also, we remind you that Telegram allows you to publish messages ^{anonymously in a group}, if your account is the group administrator. So, if you select the forwarding or copying mode on behalf of an account, and then set the anonymity setting, messages forwarded by Junction Bot will be published anonymously on behalf of the entire group.

This can be configured via the Telegram client here: Group settings - Administrators - (Select administrator - your connected account) - Anonymity: On.

‍

Delayed publication

Junction Bot has two mechanisms that allow you to delay publication time - publication with a delay and scheduling publication using Telegram's internal scheduler.

‍When using the delay function , you cannot influence messages that have been queued for publication. When scheduling , you can view the list of scheduled messages, manually edit their content and publication time, and delete them.

‍

Publish with a delay

Where to find

Menu → My forwards → Select source and destination → Publishing → Delay and delayed filter

This setting allows you to deliver messages with an additional delay. In the From field, specify how much time after the message is published in the source the message should be published in the destination.

You can also delay the message for a random period of time. To do this, specify the delay range in the From and To fields.

‍

Publication scheduling

This function is similar to the delay, but works through the internal Telegram scheduler. It is used to set a delayed time for publishing messages (when instead of clicking the Send button, you right-click on it (or hold it on the mobile version) and select "Send Later" in the context menu).

For this feature to work, you must have publishing on behalf of an account enabled (copying or forwarding).

You can see scheduled messages by clicking on the calendar icon that appears in the bottom panel of the channel or destination chat in Telegram. Scheduled messages can be manually edited (including the publication time) and deleted.

Where to find

Menu → My forwards → Select source and destination → Publication → Schedule

Using this setting, in the From field, specify how long you want to delay the message.

You can also delay the message for a random period of time. To do this, specify the delay range in the From and To fields.

‍

Pinning messages (pin)

Where to find

Menu → My forwards → Select source and destination → Publication → Pin

Options

^off - do not pin

^pass - pin if original is pinned

^silent - pin all without notification

^notify - pin all with notification

‍

Delivery frequency

Where to find

Menu → My forwarding → Select source and destination → Publishing → Delivery frequency

This setting allows you to stretch the flow of messages from a given source over time. For example, if you set the period to 60 seconds, then messages from the source will arrive no more than once a minute. If a source publishes 3 messages at once at 16:30, the first one will arrive immediately (16:30), the second one in a minute (16:31), and the third one in two minutes (16:32). If a fourth message appears in the source at 16:31, it will be published in the destination at 16:33.

Please note that the period is always calculated for each source separately. If you want the period to be counted for the entire destination, you first need to set up forwarding to an intermediate channel, and then from the intermediate channel to the final channel with the ^rate setting.

It is important to note that this setting works through the internal Telegram scheduler, the one used to set the delayed time for publishing messages. Therefore, you must have publishing on behalf of an account enabled (copying or forwarding).

To reset the period timer, set ^rate to 0.

‍

Silent mode

Where to find

Menu → My forwards → Select source and destination → Publishing → Silent mode

Options

^pass - pass the silence setting

^never - do not pass

^always - make all messages quiet

‍

Preview

Where to find

Menu → My forwards → Select source and destination → Publishing → Preview

Options

^pass - pass the flag as in the source

^never - never show preview

^always - always show preview (if there is a link)

‍

Flood behavior

Flooding is a too large flow of published messages in a channel-destination. By default, Telegram allows you to publish no more than 20-30 messages per minute, and if this threshold is exceeded, it simply blocks the publication of new ones for a while. The bot will try to send the blocked message again, later. We are not aware of any cases when Telegram would ban bots or accounts for flooding, the penalty is limited to a temporary ban on publishing.

You can customize the system's response to blocking publications using the following setting:

Where to find

Menu → My forwards → Select source and destination → Publishing → Flood behavior

Options

^{Reschedule to deliver when possible} - If a message is to be published, but a ban due to flooding is active in the destination, the system will wait until the ban ends and try to publish the message again. This is the most convenient option and is selected by default.

However, please note that if you have a very large flood of messages, then the pending messages will cause a second lock when published, the number of pending messages will grow and at some point the system will have to ignore them.

‍^‍^{Ignore the message} - If you don't care much about the messages that arrive during a lockout, you can simply ignore them. Then they will not be published.

^{Disable the forwarding rule} - In some scenarios, it may be convenient to pause the forwarding rule completely if a publishing ban occurs. The forwarding rule will be paused until you turn it back on.‍

‍

^{Notify on flood ban} - If you receive a ban from Telegram, notify it in a private chat with the bot

‍

Also, to reduce the likelihood and consequences of flood-blocking, you can take the following steps:

Try setting up posting on behalf of your account. In this mode, the restrictions should be softer.
Use publishing mode on behalf of the account and in case of flooding on behalf of the bot. It is great for bypassing flood restrictions, allowing you to achieve a publishing rate of 40-60 posts per minute.
Try distributing publications over time.
Split the traffic between several connected accounts.
Consider splitting the destination channel into multiple channels.

Publishing and moderation

Read our blog

17.10.2024

Publishing and moderation

Read our blog

5 Ways to Save a Telegram Chat

8 Ways to Bypass the ‘Copying and Forwarding Forbidden’ Restriction

How to hide the original author of a message when forwarding in Telegram