Skip to main content

Signals and Autopublish

Overview​

Signals are Signailist's hot-event notification mechanism. Autopublish extends that flow by subscribing to an existing signal and turning the event into a generated, moderated, and published piece of content.

Signals​

How signals work​

Processed news -> event clustering -> hotness evaluation -> threshold check -> Telegram alert
  1. Clustering groups related news into events.
  2. Hotness evaluates each event using factors such as source count, velocity, freshness, and AI relevance.
  3. Triggers compare the event against each subscription rule.
  4. Delivery sends the alert to Telegram when the rule is satisfied.

Signal subscription​

A user creates a subscription for a theme with conditions such as:

  • Theme: which topic of interest the subscription watches.
  • Minimum hotness: the threshold required for an alert.
  • Minimum sources: how many distinct sources must confirm the event.
  • Cooldown: the pause between alerts.
  • Telegram chat: where alerts should be delivered.

Follow-up alerts​

Signailist can issue a follow-up alert if the same event grows meaningfully after the first alert, for example through a higher score or more confirming sources.

DND (Do Not Disturb)​

  • Configurable quiet hours with start, end, and time zone.
  • Alerts that fall inside the DND window can be deferred until the quiet period ends.
  • Deferred alerts can be sent later or marked as read without sending.

Autopublish​

Principle​

Autopublish does not define its own signal thresholds. It subscribes to an existing signal and reacts when that signal fires.

Flow​

Signal fires
    -> publication draft is created
    -> text and or image generation runs
    -> moderation card is sent
    -> moderator approves or rejects
    -> approved content is published to the target channel

Autopublish rule​

An autopublish rule defines:

  • Which signal triggers it.
  • Which template is used.
  • Which target channel receives the publication.
  • Which moderation path is enabled: Telegram, web UI, or both.
  • Which outputs are generated: text, image, or both.
  • Whether the rule is currently enabled.

Moderation​

  • Moderation cards are sent to assigned reviewers.
  • Reviewers can approve or reject through Telegram or the web UI.
  • All moderation actions are tracked in the product workflow.
  • Web moderation uses the same editor as digests, including synced Telegram custom emoji. See Premium emoji.

Limitations​

  • The supported automated publication scenario is single_news.
  • Automatic publication of full digests is not implemented in this flow.