logo
0
0
Login
TrendRadar Banner

🚀 Deploy in 30 seconds — Your Smart Trending News Assistant

sansan0%2FTrendRadar | Trendshift

302.AI logo FlashSpeak logo

GitHub Stars GitHub Forks License Version MCP

WeWork WeChat Telegram DingTalk Feishu Email ntfy Bark Slack

GitHub Actions GitHub Pages Docker MCP Support

中文 | English

This project is designed to be lightweight and easy to deploy


📑 Quick Navigation

  • Thanks to bug reporters, your feedback makes this project better 😉
  • Thanks to stargazers, your stars and forks are the best support for open source 😍
  • Thanks to followers, your interactions make the content more meaningful 😎
👉 Click to view Acknowledgments (Current 🔥73🔥 supporters)

Infrastructure Support

Thanks to GitHub for providing free infrastructure, which is the biggest prerequisite for this project to run conveniently with one-click fork.

Data Support

This project uses the API from newsnow to fetch multi-platform data. Special thanks to the author for providing this service.

After communication, the author indicated no concerns about server pressure, but this is based on their goodwill and trust. Please everyone:

  • Visit the newsnow project and give it a star
  • When deploying with Docker, please control the frequency reasonably and avoid being overly greedy

Promotion Support

Thanks to the following platforms and individuals for recommendations (in chronological order)

Community Support

Thanks to financial supporters. Your generosity has transformed into snacks and drinks beside my keyboard, accompanying every iteration of this project

"One-yuan appreciation" has been suspended. If you still want to support the author, please visit the official account article and click "Like Author" at the bottom.

SupporterAmount (CNY)DateNote
D*51.8 * 32025.11.24
*鬼12025.11.17
*超102025.11.17
R*w102025.11.17Great agent work!
J*o12025.11.17Thanks for open source
*晨8.882025.11.16Nice project
*海12025.11.15
*德1.992025.11.15
*疏8.82025.11.14Great project
M*e102025.11.14Open source is not easy
**柯12025.11.14
*云882025.11.13Good project
*W62025.11.13
*凯12025.11.13
对*.12025.11.13Thanks for TrendRadar
s*y12025.11.13
**翔102025.11.13Wish I found it earlier
*韦9.92025.11.13TrendRadar is awesome
h*p52025.11.12Support Chinese open source
c*r62025.11.12
a*n52025.11.12
。*c12025.11.12Thanks for sharing
.........(More 50+ supporters)

✨ Core Features

Multi-Platform Trending News Aggregation

  • Zhihu (知乎)
  • Douyin (抖音)
  • Bilibili Hot Search
  • Wallstreetcn (华尔街见闻)
  • Tieba (贴吧)
  • Baidu Hot Search
  • Yicai (财联社)
  • Thepaper (澎湃新闻)
  • Ifeng (凤凰网)
  • Toutiao (今日头条)
  • Weibo (微博)

Default monitoring of 11 mainstream platforms, with support for adding custom platforms.

💡 For detailed configuration, see Configuration Guide - Platform Configuration

Smart Push Strategies

Three Push Modes:

ModeTarget UsersPush Feature
Daily Summary (daily)Managers/Regular UsersPush all matched news of the day (includes previously pushed)
Current Rankings (current)Content CreatorsPush current ranking matches (continuously ranked news appear each time)
Incremental Monitor (incremental)Traders/InvestorsPush only new content, zero duplication

💡 Quick Selection Guide:

  • 🔄 Don't want duplicate news → Use incremental
  • 📊 Want complete ranking trends → Use current
  • 📝 Need daily summary reports → Use daily

For detailed comparison and configuration, see Configuration Guide - Push Mode Details

Additional Feature - Push Time Window Control (Optional):

  • Set push time range (e.g., 09:00-18:00), push only within specified time
  • Configure multiple pushes within window or once per day
  • Avoid notifications during non-work hours

💡 This feature is disabled by default, see Quick Start for configuration

Precise Content Filtering

Set personal keywords (e.g., AI, BYD, Education Policy) to receive only relevant trending news, filtering out noise.

Basic Syntax (4 types):

  • Normal words: Basic matching
  • Required words +: Narrow scope
  • Filter words !: Exclude noise
  • Count limit @: Control display count (v3.2.0 new)

Advanced Features (v3.2.0 new):

  • 🔢 Keyword Sorting Control: Sort by popularity or config order
  • 📊 Display Count Limit: Global config + individual override for flexible control

Group-based Management:

  • Separate with blank lines, independent statistics for different topics

💡 Basic Configuration: Keyword Configuration - Basic Syntax

💡 Advanced Configuration: Keyword Configuration - Advanced Settings

💡 You can also skip filtering and receive all trending news (leave frequency_words.txt empty)

Trending Analysis

Real-time tracking of news popularity changes helps you understand not just "what's trending" but "how trends evolve."

  • Timeline Tracking: Records complete time span from first to last appearance
  • Popularity Changes: Tracks ranking changes and appearance frequency across time periods
  • New Detection: Real-time identification of emerging topics, marked with 🆕
  • Continuity Analysis: Distinguishes between one-time hot topics and continuously developing news
  • Cross-Platform Comparison: Same news across different platforms, showing media attention differences

💡 Push format reference: Configuration Guide - Push Format Reference

Personalized Trending Algorithm

No longer controlled by platform algorithms, TrendRadar reorganizes all trending searches:

  • Prioritize High-Ranking News (60%): Top-ranked news from each platform appears first
  • Focus on Persistent Topics (30%): Repeatedly appearing news is more important
  • Consider Ranking Quality (10%): Not just frequent, but consistently top-ranked

💡 Weight adjustment guide: Configuration Guide - Advanced Configuration

Multi-Channel Real-Time Push

Supports WeWork (+ WeChat push solution), Feishu, DingTalk, Telegram, Email, ntfy, Bark, Slack — messages delivered directly to phone and email.

Multi-Platform Support

  • GitHub Pages: Auto-generate beautiful web reports, PC/mobile adapted
  • Docker Deployment: Supports multi-architecture containerized operation
  • Data Persistence: HTML/TXT multi-format history saving

AI Smart Analysis (v3.0.0 New)

AI conversational analysis system based on MCP (Model Context Protocol), enabling deep data mining with natural language.

  • Conversational Query: Ask in natural language, like "Query yesterday's Zhihu trending" or "Analyze recent Bitcoin popularity trends"
  • 14 Analysis Tools: Date parsing, basic query, smart search, trend analysis, data insights, sentiment analysis, etc.
  • Multi-Client Support: Cherry Studio (GUI config), Claude Desktop, Cursor, Cline, etc.
  • Deep Analysis Capabilities:
    • Topic trend tracking (popularity changes, lifecycle, viral detection, trend prediction)
    • Cross-platform data comparison (activity stats, keyword co-occurrence)
    • Smart summary generation, similar news finding, historical correlation search

💡 Usage Tip: AI features require local news data support

  • Project includes November 1-15 test data for immediate experience
  • Recommend deploying the project yourself to get more real-time data

See AI Analysis for details

Zero Technical Barrier Deployment

One-click GitHub Fork to use, no programming required.

30-second deployment: GitHub Pages (web browsing) supports one-click save as image for easy sharing

1-minute deployment: WeWork (mobile notification)

💡 Tip: Want a real-time updated web version? After forking, go to your repo Settings → Pages and enable GitHub Pages. Preview Effect.

Reduce APP Dependencies

Transform from "algorithm recommendation captivity" to "actively getting the information you want"

Target Users: Investors, content creators, PR professionals, news-conscious general users

Typical Scenarios: Stock investment monitoring, brand sentiment tracking, industry trend watching, lifestyle news gathering

Github Pages Effect (Mobile Adapted, Email Push)Feishu Push Effect
Github Pages EffectFeishu Push Effect

📝 Changelog

Upgrade Instructions:

  • 📌 Check Latest Updates: Original Repository Changelog
  • Tip: Do NOT update this project via Sync fork. Check [Changelog] to understand specific [Upgrade Methods] and [Features]
  • Minor Version Update: Upgrading from v2.x to v2.y, replace main.py in your forked repo with the latest version
  • Major Version Upgrade: Upgrading from v1.x to v2.y, recommend deleting existing fork and re-forking to save effort and avoid config conflicts

2025/11/28 - v3.4.1

🔧 Format Optimization

  1. Bark Push Enhancement

    • Bark now supports Markdown rendering
    • Enabled native Markdown format: bold, links, lists, code blocks, etc.
    • Removed plain text conversion to fully utilize Bark's native rendering capabilities
  2. Slack Format Precision

    • Use dedicated mrkdwn format for batch content processing
    • Improved byte size estimation accuracy (avoid message overflow)
    • Optimized link format: <url|text> and bold syntax: *text*
  3. Performance Improvement

    • Format conversion completed during batching process, avoiding secondary processing
    • Accurate message size estimation reduces send failure rate

🔧 Upgrade Instructions:

  • GitHub Fork Users: Update main.pyconfig.yaml

2025/11/26 - mcp-v1.0.3

MCP Module Update:

  • Added date parsing tool resolve_date_range to resolve AI model date calculation inconsistencies
  • Support natural language date expression parsing (this week, last 7 days, last month, etc.)
  • Tool count increased from 13 to 14
👉 Click to expand: Historical Updates

2025/11/25 - v3.4.0

🎉 Added Slack Push Support

  1. Team Collaboration Push Channel

    • Supports Slack Incoming Webhooks (globally popular team collaboration tool)
    • Centralized message management, suitable for team-shared trending news
    • Supports mrkdwn format (bold, links, etc.)
  2. Multiple Deployment Methods

    • GitHub Actions: Configure SLACK_WEBHOOK_URL Secret
    • Docker: Environment variable SLACK_WEBHOOK_URL
    • Local: config/config.yaml configuration file

📖 Detailed Configuration Tutorial: Quick Start - Slack Push

  • Optimized the one-click installation experience for setup-windows.bat and setup-windows-en.bat

🔧 Upgrade Instructions:

  • GitHub Fork Users: Update main.py, config/config.yaml, .github/workflows/crawler.yml

2025/11/24 - v3.3.0

🎉 Added Bark Push Support

  1. iOS Exclusive Push Channel

    • Supports Bark push (based on APNs, iOS platform)
    • Free, open-source, clean, efficient, ad-free
    • Supports both official server and self-hosted server
  2. Multiple Deployment Methods

    • GitHub Actions: Configure BARK_URL Secret
    • Docker: Environment variable BARK_URL
    • Local: config/config.yaml configuration file

📖 Detailed Configuration Tutorial: Quick Start - Bark Push

🐛 Bug Fix

  • Fixed issue where ntfy_server_url in config.yaml was ignored (#345)

🔧 Upgrade Instructions:

  • GitHub Fork Users: Update main.py, config/config.yaml, .github/workflows/crawler.yml

2025/11/23 - v3.2.0

🎯 New Advanced Customization Features

  1. Keyword Sorting Priority Configuration

    • Two sorting strategies: Popularity first vs Config order first
    • For different use cases: Hot topic tracking or personalized focus
  2. Display Count Precise Control

    • Global config: Unified limit for all keywords
    • Individual config: Use @number syntax to set specific limits
    • Effectively control push length, highlight key content

📖 Detailed Tutorial: Keyword Configuration - Advanced Settings

🔧 Upgrade Instructions:

  • GitHub Fork Users: Update main.py, config/config.yaml

2025/11/22 - v3.1.1

  • Fixed data anomaly crash issue: Resolved 'float' object has no attribute 'lower' error encountered by some users in GitHub Actions environment
  • Added dual protection mechanism: Filter invalid titles (None, float, empty strings) at data acquisition stage, with type checking at function call sites
  • Enhanced system stability to ensure normal operation even when data sources return abnormal formats

Upgrade Instructions (GitHub Fork Users):

  • Required update: main.py
  • Recommended: Use minor version upgrade method - copy and replace the file above

2025/11/18 - mcp-v1.0.2

MCP Module Update:

  • Fix issue where today's news query may return articles from past dates

2025/11/20 - v3.1.0

  • Added Personal WeChat Push Support: WeWork application can push to personal WeChat without installing WeWork APP
  • Supports two message formats: markdown (WeWork group bot) and text (personal WeChat app)
  • Added WEWORK_MSG_TYPE environment variable configuration, supporting GitHub Actions, Docker, docker-compose and other deployment methods
  • text mode automatically strips Markdown syntax for clean plain text push
  • See "Personal WeChat Push" configuration in Quick Start

Upgrade Instructions (GitHub Fork Users):

  • Required updates: main.py, config/config.yaml
  • Optional update: .github/workflows/crawler.yml (if using GitHub Actions)
  • Recommended: Use minor version upgrade method - copy and replace the files above

2025/11/12 - v3.0.5

  • Fixed email sending SSL/TLS port configuration logic error
  • Optimized email service providers (QQ/163/126) to default use port 465 (SSL)
  • Added Docker environment variable support: Core config items (enable_crawler, report_mode, push_window, etc.) support override via environment variables, solving config file modification issues for NAS users (see 🐳 Docker Deployment chapter)

2025/10/26 - mcp-v1.0.1

MCP Module Update:

  • Fixed date query parameter passing error
  • Unified time parameter format for all tools

2025/10/31 - v3.0.4

  • Solved Feishu error due to overly long push content, implemented batch pushing

2025/10/23 - v3.0.3

  • Expanded ntfy error message display range

2025/10/21 - v3.0.2

  • Fixed ntfy push encoding issue

2025/10/20 - v3.0.0

Major Update - AI Analysis Feature Launched 🤖

  • Core Features:

    • New MCP (Model Context Protocol) based AI analysis server
    • 13 smart analysis tools: basic query, smart search, advanced analysis, system management
    • Natural language interaction: Query and analyze news data through conversation
    • Multi-client support: Claude Desktop, Cherry Studio, Cursor, Cline, etc.
  • Analysis Capabilities:

    • Topic trend analysis (popularity tracking, lifecycle, viral detection, trend prediction)
    • Data insights (platform comparison, activity stats, keyword co-occurrence)
    • Sentiment analysis, similar news finding, smart summary generation
    • Historical related news search, multi-mode search
  • Update Note:

    • This is an independent AI analysis feature, does not affect existing push functionality
    • Optional use, no need to upgrade existing deployment

2025/10/15 - v2.4.4

  • Updates:

    • Fixed ntfy push encoding issue + 1
    • Fixed push time window judgment issue
  • Upgrade Note:

    • Recommended minor version upgrade

2025/10/10 - v2.4.3

Thanks to nidaye996 for discovering the UX issue

  • Updates:

    • Refactored "Silent Push Mode" naming to "Push Time Window Control", improving feature comprehension
    • Clarified push time window as optional additional feature, can work with three push modes
    • Improved comments and documentation, making feature positioning clearer
  • Upgrade Note:

    • This is just refactoring, upgrade optional

2025/10/8 - v2.4.2

  • Updates:

    • Fixed ntfy push encoding issue
    • Fixed missing config file issue
    • Optimized ntfy push effect
    • Added GitHub Pages image segmented export feature
  • Upgrade Note:

    • Recommend major version update

2025/10/2 - v2.4.0

Added ntfy Push Notification

  • Core Features:

    • Supports ntfy.sh public service and self-hosted servers
  • Use Cases:

    • Suitable for privacy-conscious users (supports self-hosting)
    • Cross-platform push (iOS, Android, Desktop, Web)
    • No account registration needed (public servers)
    • Open-source and free (MIT License)
  • Upgrade Note:

    • Recommend major version update

2025/09/26 - v2.3.2

  • Fixed email notification config check being missed (#88)

Fix Description:

  • Solved the issue where system still prompted "No webhook configured" even with correct email notification setup

2025/09/22 - v2.3.1

  • Added email push feature, supports sending trending news reports to email
  • Smart SMTP Recognition: Auto-detects Gmail, QQ Mail, Outlook, NetEase Mail and 10+ email service providers
  • Beautiful HTML Format: Email content uses same HTML format as web version, well-formatted, mobile-adapted
  • Batch Sending Support: Supports multiple recipients, separated by commas
  • Custom SMTP: Can customize SMTP server and port
  • Fixed Docker build network connection issue

Usage Notes:

  • Use cases: Suitable for users needing email archiving, team sharing, scheduled reports
  • Supported emails: Gmail, QQ Mail, Outlook/Hotmail, 163/126 Mail, Sina Mail, Sohu Mail, etc.

Upgrade Note:

  • This update has many changes, if upgrading, recommend major version upgrade

2025/09/17 - v2.2.0

  • Added one-click save news as image feature, easily share trending topics you care about

Usage Notes:

  • Use case: After enabling web version feature (GitHub Pages)
  • How to use: Open webpage on phone or PC, click "Save as Image" button at top
  • Actual effect: System auto-creates beautiful image of current news report, saves to phone album or desktop
  • Sharing convenience: Directly send this image to friends, Moments, or work groups, letting others see your discovered important info

2025/09/13 - v2.1.2

  • Solved DingTalk push capacity limit causing news push failure (using batch push)

2025/09/04 - v2.1.1

  • Fixed Docker unable to run properly on certain architectures
  • Officially released official Docker image wantcat/trendradar, supports multi-architecture
  • Optimized Docker deployment process, can use quickly without local build

2025/08/30 - v2.1.0

Core Improvements:

  • Push Logic Optimization: Changed from "push every execution" to "controllable push within time window"
  • Time Window Control: Can set push time range, avoid non-work hour disturbance
  • Push Frequency Options: Supports single push or multiple pushes within time window

Upgrade Note:

  • This feature is disabled by default, need to manually enable push time window control in config.yaml
  • Upgrade requires updating both main.py and config.yaml files

2025/08/27 - v2.0.4

  • This version is not a bug fix, but an important reminder
  • Please keep webhooks properly, do not make public, do not make public, do not make public
  • If you deployed this project on GitHub via fork, please put webhooks in GitHub Secret, not config.yaml
  • If you already exposed webhooks or put them in config.yaml, suggest deleting and regenerating

2025/08/06 - v2.0.3

  • Optimized GitHub Pages web version effect, convenient for mobile use

2025/07/28 - v2.0.2

  • Refactored code
  • Solved version number easily being missed for modification

2025/07/27 - v2.0.1

Fixed Issues:

  1. Docker shell script line ending as CRLF causing execution exception issue
  2. frequency_words.txt being empty causing news sending also empty logic issue
  • After fix, when you choose frequency_words.txt empty, will push all news, but limited by message push size, please adjust as follows
    • Option 1: Turn off mobile push, only choose GitHub Pages deployment (this is the way to get most complete info, will re-sort all platform trending by your custom trending algorithm)
    • Option 2: Reduce push platforms, prioritize WeWork or Telegram, these two pushes I made batch push feature (because batch push affects push experience, and only these two platforms give very little push capacity, so had to make batch push feature, but at least can ensure complete info)
    • Option 3: Can combine with Option 2, mode choose current or incremental can effectively reduce one-time push content

2025/07/17 - v2.0.0

Major Refactoring:

  • Config management refactoring: All configs now managed through config/config.yaml file (main.py I still didn't split, convenient for you to copy and upgrade)
  • Run mode upgrade: Supports three modes - daily (daily summary), current (current rankings), incremental (incremental monitoring)
  • Docker support: Complete Docker deployment solution, supports containerized operation

Config File Description:

  • config/config.yaml - Main config file (application settings, crawler config, notification config, platform config, etc.)
  • config/frequency_words.txt - Keyword config (monitoring vocabulary settings)

2025/07/09 - v1.4.1

New Feature: Added incremental push (configure FOCUS_NEW_ONLY at top of main.py), this switch only cares about new topics not sustained heat, only sends notification when new content appears.

Fixed Issue: Under certain circumstances, some news containing special symbols caused occasional formatting exceptions.

2025/06/23 - v1.3.0

WeWork and Telegram push messages have length limits, I adopted splitting messages for pushing. Development docs see WeWork and Telegram

2025/06/21 - v1.2.1

Before this version, not only main.py needs copy replacement, crawler.yml also needs you to copy replacement https://github.com/sansan0/TrendRadar/blob/master/.github/workflows/crawler.yml

2025/06/19 - v1.2.0

Thanks to Claude Research for organizing various platform APIs, helping me quickly complete platform adaptation (although code is more redundant~

  1. Supports Telegram, WeWork, DingTalk push channels, supports multi-channel config and simultaneous push

2025/06/18 - v1.1.0

200 stars⭐ reached, continue celebrating with everyone~

  1. Important update, added weight, news you see now is hottest most concerned appearing at top
  2. Updated documentation usage, because recently updated many features, and previous usage docs I was lazy wrote simple (see ⚙️ frequency_words.txt complete configuration tutorial below)

2025/06/16 - v1.0.0

  1. Added project new version update reminder, default on, if want to turn off, can change "FEISHU_SHOW_VERSION_UPDATE": True to False in main.py

2025/06/13+14

  1. Removed compatibility code, students who forked before, directly copying code will show exception on same day (will recover normal next day)
  2. Feishu and html bottom added new news display

2025/06/09

100 stars⭐ reached, writing small feature to celebrate

frequency_words.txt file added required word feature, using + sign

  1. Required word syntax as follows: Tang Monk or Pig must both appear in title, will be included in push news
+Tang Monk +Pig
  1. Filter word priority higher: If title filter word matches Tang Monk reciting sutras, then even if required word has Tang Monk, also not display
+Tang Monk !Tang Monk reciting sutras

2025/06/02

  1. Webpage and Feishu messages support phone directly jumping to detailed news
  2. Optimized display effect + 1

2025/05/26

  1. Feishu message display effect optimized

🚀 Quick Start

📖 Reminder: Fork users should first check the latest official documentation to ensure the configuration steps are up to date.

  1. Fork this project to your GitHub account

    • Click the "Fork" button at the top right of this page
  2. Setup GitHub Secrets (Choose your needed platforms):

    In your forked repo, go to Settings > Secrets and variables > Actions > New repository secret

    📌 Important Instructions (Please Read Carefully):

    • One Name for One Secret: For each configuration item, click the "New repository secret" button once and fill in a pair of "Name" and "Secret"
    • Cannot See Value After Saving is Normal: For security reasons, after saving, you can only see the Name when re-editing, but not the Secret value
    • ⚠️ DO NOT Create Custom Names: The Secret Name must strictly use the names listed below (e.g., WEWORK_WEBHOOK_URL, FEISHU_WEBHOOK_URL, etc.). Do not modify or create new names arbitrarily, or the system will not recognize them
    • 💡 Can Configure Multiple Platforms: The system will send notifications to all configured platforms

    Configuration Example:

    GitHub Secrets Configuration Example

    As shown above, each row is a configuration item:

    • Name: Must use the fixed names listed in the expanded sections below (e.g., WEWORK_WEBHOOK_URL)
    • Secret (Value): Fill in the actual content obtained from the corresponding platform (e.g., Webhook URL, Token, etc.)

    👉 Click to expand: WeWork Bot (Simplest and fastest configuration)

    GitHub Secret Configuration (⚠️ Name must match exactly):

    • Name: WEWORK_WEBHOOK_URL (Please copy and paste this name, do not type manually to avoid typos)
    • Secret (Value): Your WeWork bot Webhook address

    Bot Setup Steps:

    Mobile Setup:

    1. Open WeWork App → Enter target internal group chat
    2. Click "…" button at top right → Select "Message Push"
    3. Click "Add" → Name input "TrendRadar"
    4. Copy Webhook address, click save, paste the copied content into GitHub Secret above

    PC Setup Process Similar

    👉 Click to expand: Personal WeChat Push (Based on WeWork app, push to personal WeChat)

    This solution is based on WeWork's plugin mechanism. The push style is plain text (no markdown format), but it can push directly to personal WeChat without installing WeWork App.

    GitHub Secret Configuration (⚠️ Name must match exactly):

    • Name: WEWORK_WEBHOOK_URL (Please copy and paste this name, do not type manually)

    • Secret (Value): Your WeWork app Webhook address

    • Name: WEWORK_MSG_TYPE (Please copy and paste this name, do not type manually)

    • Secret (Value): text


    Setup Steps:

    1. Complete the WeWork bot Webhook setup above
    2. Add WEWORK_MSG_TYPE Secret with value text
    3. Follow the image below to link personal WeChat
    4. After configuration, WeWork App can be deleted from phone

    Notes:

    • Uses the same Webhook address as WeWork bot
    • Difference is message format: text for plain text, markdown for rich text (default)
    • Plain text format will automatically remove all markdown syntax (bold, links, etc.)
    👉 Click to expand: Feishu Bot (Most user-friendly message display)

    GitHub Secret Configuration (⚠️ Name must match exactly):

    Two methods available, Method 1 is simpler, Method 2 is more complex (but stable push)

    Method 1 discovered and suggested by ziventian, thanks to them. Default is personal push, group push can be configured via #97

    Method 1:

    For some users, additional operations needed to avoid "System Error". Need to search for the bot on mobile and enable Feishu bot application (suggestion from community, can refer)

    1. Open in PC browser https://botbuilder.feishu.cn/home/my-command

    2. Click "New Bot Command"

    3. Click "Select Trigger", scroll down, click "Webhook Trigger"

    4. Now you'll see "Webhook Address", copy this link to local notepad temporarily, continue with next steps

    5. In "Parameters" put the following content, then click "Done"

    { "message_type": "text", "content": { "total_titles": "{{Content}}", "timestamp": "{{Content}}", "report_type": "{{Content}}", "text": "{{Content}}" } }
    1. Click "Select Action" > "Send via Official Bot"

    2. Message title fill "TrendRadar Trending Monitor"

    3. Most critical part, click + button, select "Webhook Trigger", then arrange as shown in image

    Feishu Bot Config Example

    1. After configuration, put Webhook address from step 4 into GitHub Secrets FEISHU_WEBHOOK_URL

    Method 2:

    1. Open in PC browser https://botbuilder.feishu.cn/home/my-app

    2. Click "New Bot Application"

    3. After entering the created application, click "Process Design" > "Create Process" > "Select Trigger"

    4. Scroll down, click "Webhook Trigger"

    5. Now you'll see "Webhook Address", copy this link to local notepad temporarily, continue with next steps

    6. In "Parameters" put the following content, then click "Done"

    { "message_type": "text", "content": { "total_titles": "{{Content}}", "timestamp": "{{Content}}", "report_type": "{{Content}}", "text": "{{Content}}" } }
    1. Click "Select Action" > "Send Feishu Message", check "Group Message", then click the input box below, click "Groups I Manage" (if no group, you can create one in Feishu app)

    2. Message title fill "TrendRadar Trending Monitor"

    3. Most critical part, click + button, select "Webhook Trigger", then arrange as shown in image

    Feishu Bot Config Example

    1. After configuration, put Webhook address from step 5 into GitHub Secrets FEISHU_WEBHOOK_URL
    👉 Click to expand: DingTalk Bot

    GitHub Secret Configuration (⚠️ Name must match exactly):

    • Name: DINGTALK_WEBHOOK_URL (Please copy and paste this name, do not type manually)
    • Secret (Value): Your DingTalk bot Webhook address

    Bot Setup Steps:

    1. Create Bot (PC Only):

      • Open DingTalk PC client, enter target group chat
      • Click group settings icon (⚙️) → Scroll down to find "Bot" and click
      • Select "Add Bot" → "Custom"
    2. Configure Bot:

      • Set bot name
      • Security Settings:
        • Custom Keywords: Set "Trending" or "热点"
    3. Complete Setup:

      • Check service terms agreement → Click "Done"
      • Copy the obtained Webhook URL
      • Put URL into GitHub Secrets DINGTALK_WEBHOOK_URL

    Note: Mobile can only receive messages, cannot create new bots.

    👉 Click to expand: Telegram Bot

    GitHub Secret Configuration (⚠️ Name must match exactly):

    • Name: TELEGRAM_BOT_TOKEN (Please copy and paste this name, do not type manually)

    • Secret (Value): Your Telegram Bot Token

    • Name: TELEGRAM_CHAT_ID (Please copy and paste this name, do not type manually)

    • Secret (Value): Your Telegram Chat ID

    Note: Telegram requires two Secrets, please click "New repository secret" button twice to add them separately


    Bot Setup Steps:

    1. Create Bot:

      • Search @BotFather in Telegram (note case, has blue verification checkmark, shows ~37849827 monthly users, this is official, beware of fake accounts)
      • Send /newbot command to create new bot
      • Set bot name (must end with "bot", easily runs into duplicate names, so think creatively)
      • Get Bot Token (format like: 123456789:AAHfiqksKZ8WmR2zSjiQ7_v4TMAKdiHm9T0)
    2. Get Chat ID:

      Method 1: Via Official API

      • First send a message to your bot
      • Visit: https://api.telegram.org/bot<Your Bot Token>/getUpdates
      • Find the number in "chat":{"id":number} in returned JSON

      Method 2: Using Third-Party Tool

      • Search @userinfobot and send /start
      • Get your user ID as Chat ID
    3. Configure to GitHub:

      • TELEGRAM_BOT_TOKEN: Fill in Bot Token from step 1
      • TELEGRAM_CHAT_ID: Fill in Chat ID from step 2
    👉 Click to expand: Email Push (Supports all mainstream email providers)
    • Note: To prevent email bulk sending abuse, current bulk sending allows all recipients to see each other's email addresses.
    • If you haven't configured email sending before, not recommended to try

    GitHub Secret Configuration (⚠️ Name must match exactly):

    • Name: EMAIL_FROM (Please copy and paste this name, do not type manually)

    • Secret (Value): Sender email address

    • Name: EMAIL_PASSWORD (Please copy and paste this name, do not type manually)

    • Secret (Value): Email password or authorization code

    • Name: EMAIL_TO (Please copy and paste this name, do not type manually)

    • Secret (Value): Recipient email address (multiple separated by comma, or can be same as EMAIL_FROM to send to yourself)

    • Name: EMAIL_SMTP_SERVER (Optional, please copy and paste this name)

    • Secret (Value): SMTP server address (leave empty for auto-detection)

    • Name: EMAIL_SMTP_PORT (Optional, please copy and paste this name)

    • Secret (Value): SMTP port (leave empty for auto-detection)

    Note: Email push requires at least 3 required Secrets (EMAIL_FROM, EMAIL_PASSWORD, EMAIL_TO), the last two are optional


    Supported Email Providers (Auto-detect SMTP config):

    ProviderDomainSMTP ServerPortEncryption
    Gmailgmail.comsmtp.gmail.com587TLS
    QQ Mailqq.comsmtp.qq.com465SSL
    Outlookoutlook.comsmtp-mail.outlook.com587TLS
    Hotmailhotmail.comsmtp-mail.outlook.com587TLS
    Livelive.comsmtp-mail.outlook.com587TLS
    163 Mail163.comsmtp.163.com465SSL
    126 Mail126.comsmtp.126.com465SSL
    Sina Mailsina.comsmtp.sina.com465SSL
    Sohu Mailsohu.comsmtp.sohu.com465SSL
    189 Mail189.cnsmtp.189.cn465SSL
    Aliyun Mailaliyun.comsmtp.aliyun.com465TLS

    Auto-detect: When using above emails, no need to manually configure EMAIL_SMTP_SERVER and EMAIL_SMTP_PORT, system auto-detects.

    Feedback Notice:

    • If you successfully test with other email providers, please open an Issue to let us know, we'll add to support list
    • If above email configurations are incorrect or unusable, please also open an Issue for feedback to help improve the project

    Special Thanks:

    • Thanks to @DYZYD for contributing 189 Mail (189.cn) configuration and completing self-send-receive testing (#291)
    • Thanks to @longzhenren for contributing Aliyun Mail (aliyun.com) configuration and completing testing (#344)

    Common Email Settings:

    QQ Mail:

    1. Login QQ Mail web version → Settings → Account
    2. Enable POP3/SMTP service
    3. Generate authorization code (16-letter code)
    4. EMAIL_PASSWORD fill authorization code, not QQ password

    Gmail:

    1. Enable two-step verification
    2. Generate app-specific password
    3. EMAIL_PASSWORD fill app-specific password

    163/126 Mail:

    1. Login web version → Settings → POP3/SMTP/IMAP
    2. Enable SMTP service
    3. Set client authorization code
    4. EMAIL_PASSWORD fill authorization code

    Advanced Configuration: If auto-detect fails, manually configure SMTP:

    • EMAIL_SMTP_SERVER: Like smtp.gmail.com
    • EMAIL_SMTP_PORT: Like 587 (TLS) or 465 (SSL)

    Multiple Recipients (note: English comma separator):

    👉 Click to expand: ntfy Push (Open-source, free, self-hostable)

    Two Usage Methods:

    Method 1: Free Use (Recommended for Beginners) 🆓

    Features:

    • ✅ No account registration, use immediately
    • ✅ 250 messages/day (enough for 90% users)
    • ✅ Topic name is "password" (need to choose hard-to-guess name)
    • ⚠️ Messages unencrypted, not for sensitive info, but suitable for our non-sensitive project info

    Quick Start:

    1. Download ntfy App:

    2. Subscribe to Topic (choose a hard-to-guess name):

      Suggested format: trendradar-{your initials}-{random numbers} Cannot use Chinese ✅ Good example: trendradar-zs-8492 ❌ Bad example: news, alerts (too easy to guess)
    3. Configure GitHub Secret (⚠️ Name must match exactly):

      • Name: NTFY_TOPIC (Please copy and paste this name, do not type manually)

      • Secret (Value): Fill in your subscribed topic name

      • Name: NTFY_SERVER_URL (Optional, please copy and paste this name)

      • Secret (Value): Leave empty (default uses ntfy.sh)

      • Name: NTFY_TOKEN (Optional, please copy and paste this name)

      • Secret (Value): Leave empty

      Note: ntfy requires at least 1 required Secret (NTFY_TOPIC), the last two are optional

    4. Test:

      curl -d "Test message" ntfy.sh/your-topic-name

    Method 2: Self-Hosting (Complete Privacy Control) 🔒

    Target Users: Have server, pursue complete privacy, strong technical ability

    Advantages:

    • ✅ Completely open-source (Apache 2.0 + GPLv2)
    • ✅ Complete data self-control
    • ✅ No restrictions
    • ✅ Zero cost

    Docker One-Click Deploy:

    docker run -d \ --name ntfy \ -p 80:80 \ -v /var/cache/ntfy:/var/cache/ntfy \ binwiederhier/ntfy \ serve --cache-file /var/cache/ntfy/cache.db

    Configure TrendRadar:

    NTFY_SERVER_URL: https://ntfy.yourdomain.com NTFY_TOPIC: trendradar-alerts # Self-hosting can use simple name NTFY_TOKEN: tk_your_token # Optional: Enable access control

    Subscribe in App:

    • Click "Use another server"
    • Enter your server address
    • Enter topic name
    • (Optional) Enter login credentials

    FAQ:

    Q1: Is the free version enough?

    250 messages/day is enough for most users. With 30-minute crawl intervals, about 48 pushes/day, completely sufficient.

    Q2: Is the Topic name really secure?

    If you choose a random, sufficiently long name (like trendradar-zs-8492-news), brute force is nearly impossible:

    • ntfy has strict rate limiting (1 request/second)
    • 64 character choices (A-Z, a-z, 0-9, _, -)
    • 10 random characters have 64^10 possibilities (would take years to crack)

    Recommended Choice:

    User TypeRecommendedReason
    Regular UsersMethod 1 (Free)Simple, fast, enough
    Technical UsersMethod 2 (Self-Host)Complete control, unlimited
    High-Frequency UsersMethod 3 (Paid)Check official website

    Related Links:

    👉 Click to expand: Bark Push (iOS exclusive, clean & efficient)

    GitHub Secret Configuration (⚠️ Name must be exact):

    • Name: BARK_URL (copy and paste this name, don't type manually)
    • Secret: Your Bark push URL

    Bark Introduction:

    Bark is a free open-source push tool for iOS platform, featuring simplicity, speed, and no ads.

    Usage Methods:

    Method 1: Use Official Server (Recommended for beginners) 🆓

    1. Download Bark App:

    2. Get Push URL:

      • Open Bark App
      • Copy the push URL displayed on the home page (format: https://api.day.app/your_device_key)
      • Configure the URL to GitHub Secrets as BARK_URL

    Method 2: Self-Hosted Server (Complete Privacy Control) 🔒

    Suitable for: Users with servers, pursuing complete privacy, strong technical skills

    Docker One-Click Deployment:

    docker run -d \ --name bark-server \ -p 8080:8080 \ finab/bark-server

    Configure TrendRadar:

    BARK_URL: http://your-server-ip:8080/your_device_key

    Notes:

    • ✅ Bark uses APNs push, max 4KB per message
    • ✅ Supports automatic batch sending, no worry about long messages
    • ✅ Push format is plain text (automatically removes Markdown syntax)
    • ⚠️ Only supports iOS platform

    Related Links:

    👉 Click to expand: Slack Push

    GitHub Secret Configuration (⚠️ Name must be exact):

    • Name: SLACK_WEBHOOK_URL (copy and paste this name, don't type manually)
    • Secret: Your Slack Incoming Webhook URL

    Slack Introduction:

    Slack is a team collaboration tool, Incoming Webhooks can push messages to Slack channels.

    Setup Steps:

    Step 1: Create Slack App

    1. Visit Slack API Page:

    2. Choose Creation Method:

      • Click "From scratch"
    3. Fill in App Information:

      • App Name: Enter app name (e.g., TrendRadar or Hot News Monitor)
      • Workspace: Select your workspace from dropdown
      • Click "Create App" button

    Step 2: Enable Incoming Webhooks

    1. Navigate to Incoming Webhooks:

      • Find and click "Incoming Webhooks" in left menu
    2. Enable Feature:

      • Find "Activate Incoming Webhooks" toggle
      • Switch from OFF to ON
      • Page will auto-refresh showing new configuration options

    Step 3: Generate Webhook URL

    1. Add New Webhook:

      • Scroll to page bottom
      • Click "Add New Webhook to Workspace" button
    2. Select Target Channel:

      • System will show authorization page
      • Select channel to receive messages from dropdown (e.g., #hot-news)
      • ⚠️ For private channels, must join the channel first
    3. Authorize App:

      • Click "Allow" button to complete authorization
      • System will auto-redirect back to config page

    Step 4: Copy and Save Webhook URL

    1. View Generated URL:

      • In "Webhook URLs for Your Workspace" section
      • You'll see the newly generated Webhook URL
      • Format: https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
    2. Copy URL:

      • Click "Copy" button on the right of URL
      • Or manually select and copy URL
    3. Configure to TrendRadar:

      • GitHub Actions: Add URL to GitHub Secrets as SLACK_WEBHOOK_URL
      • Local Testing: Fill URL in config/config.yaml slack_webhook_url field
      • Docker Deployment: Add URL to docker/.env file as SLACK_WEBHOOK_URL variable

    Notes:

    • ✅ Supports Markdown format (auto-converts to Slack mrkdwn)
    • ✅ Supports automatic batch sending (4KB per batch)
    • ✅ Suitable for team collaboration, centralized message management
    • ⚠️ Webhook URL contains secret key, never make it public

    Message Format Preview:

    *[Batch 1/2]* 📊 *Trending Topics Statistics* 🔥 *[1/3] AI ChatGPT* : 2 articles 1. [Baidu Hot] 🆕 ChatGPT-5 Official Release *[1]* - 09:15 (1 time) 2. [Toutiao] AI Chip Stocks Surge *[3]* - [08:30 ~ 10:45] (3 times)

    Related Links:

    💡 Beginner Quick Start Tip:

    For first deployment, suggest completing GitHub Secrets configuration first (choose one push platform), then jump to [Step 3] to test push success.

    Don't modify config/config.yaml and frequency_words.txt temporarily, adjust these configs after push test succeeds as needed.

  3. Manual Test News Push:

    💡 Complete Step 1-2 first, then test immediately! Test success first, then adjust configuration (Step 4) as needed.

    ⚠️ IMPORTANT: Enter your own forked project, not this project!

    How to find your Actions page:

    • Method 1: Open your forked project homepage, click the Actions tab at the top
    • Method 2: Direct access https://github.com/YourUsername/TrendRadar/actions

    Example comparison:

    • ❌ Author's project: https://github.com/sansan0/TrendRadar/actions
    • ✅ Your project: https://github.com/YourUsername/TrendRadar/actions

    Testing steps:

    1. Enter your project's Actions page
    2. Find "Hot News Crawler" and click in
      • If you don't see this text, refer to #109 to solve
    3. Click "Run workflow" button on the right to run
    4. Wait about 1 minute, messages will be pushed to your configured platform
  4. Configuration Notes (Optional):

    💡 Default configuration works normally, only adjust if you need personalization

    Note: Suggest only adjusting explicitly documented config items, other options mainly for author's development testing

  5. 🎉 Deployment Success! Share Your Experience

    Congratulations on completing TrendRadar configuration! You can now start tracking trending news.

    💬 Join our community to share your experience~

    • Want to learn more tips and advanced techniques?
    • Need quick help with issues?
    • Have great ideas to share?

    👉 Follow our WeChat Official Account「硅基茶水间」(Silicon Tea Room), your likes and comments are the driving force for continuous updates!

    For detailed communication methods, please check → FAQ & Support

  6. 🤖 Want Smarter Analysis? Try AI-Enhanced Features (Optional)

    Basic configuration already meets daily needs, but if you want:

    • 📊 Let AI automatically analyze trending topics and data insights
    • 🔍 Search and query news using natural language
    • 💡 Get sentiment analysis, topic prediction, and deep analytics
    • ⚡ Directly access data in AI tools like Claude, Cursor, etc.

    👉 Learn More: AI Analysis — Unlock hidden capabilities and make trend tracking more efficient!


⚙️ Configuration Guide

📖 Reminder: This chapter provides detailed configuration explanations. Suggest completing Quick Start basic configuration first, then refer to detailed options here as needed.

1. Platform Configuration

👉 Click to expand: Custom Monitoring Platforms

This project's news data comes from newsnow. You can click the website, click [More], to see if there are platforms you want.

For specific additions, visit project source code, based on the file names there, modify the platforms configuration in config/config.yaml file:

platforms: - id: "toutiao" name: "Toutiao" - id: "baidu" name: "Baidu Hot Search" - id: "wallstreetcn-hot" name: "Wallstreetcn" # Add more platforms...

If you don't know how to look, you can directly copy the partially organized Platform Configuration

2. Keyword Configuration

Configure monitoring keywords in frequency_words.txt with four syntax types and grouping features.

Syntax TypeSymbolPurposeExampleMatching Logic
NormalNoneBasic matchingHuaweiMatch any one
Required+Scope limiting+phoneMust include both
Filter!Noise exclusion!adExclude if included
Count Limit@Control display count@10Max 10 news (v3.2.0 new)

2.1 Basic Syntax

👉 Click to expand: Basic Syntax Tutorial
1. Normal Keywords - Basic Matching
Huawei OPPO Apple

Effect: News containing any one of these words will be captured

2. Required Words +word - Scope Limiting
Huawei OPPO +phone

Effect: Must include both normal word and required word to be captured

3. Filter Words !word - Noise Exclusion
Apple Huawei !fruit !price

Effect: News containing filter words will be excluded, even if it contains keywords

4. Count Limit @number - Control Display Count (v3.2.0 new)
Tesla Musk @5

Effect: Limit maximum news count for this keyword group

Priority: @number > Global config > Unlimited


🔗 Group Feature - Importance of Empty Lines

Core Rule: Use empty lines to separate different groups, each group is independently counted

Example Configuration:
iPhone Huawei OPPO +launch A-shares Shanghai Index Shenzhen Index +fluctuation !prediction World Cup Euro Cup Asian Cup +match
Group Explanation and Matching Effects:

Group 1 - Phone Launches:

  • Keywords: iPhone, Huawei, OPPO
  • Required: launch
  • Effect: Must include phone brand name and "launch"

Matching Examples:

  • ✅ "iPhone 15 officially launched with pricing" ← Has "iPhone" + "launch"
  • ✅ "Huawei Mate60 series launch livestream" ← Has "Huawei" + "launch"
  • ✅ "OPPO Find X7 launch date confirmed" ← Has "OPPO" + "launch"
  • ❌ "iPhone sales hit record high" ← Has "iPhone" but missing "launch"

Group 2 - Stock Market:

  • Keywords: A-shares, Shanghai Index, Shenzhen Index
  • Required: fluctuation
  • Filter: prediction
  • Effect: Include stock-related words and "fluctuation", but exclude "prediction"

Matching Examples:

  • ✅ "A-shares major fluctuation analysis today" ← Has "A-shares" + "fluctuation"
  • ✅ "Shanghai Index fluctuation reasons explained" ← Has "Shanghai Index" + "fluctuation"
  • ❌ "Experts predict A-shares fluctuation trends" ← Has "A-shares" + "fluctuation" but contains "prediction"
  • ❌ "A-shares trading volume hits new high" ← Has "A-shares" but missing "fluctuation"

Group 3 - Football Events:

  • Keywords: World Cup, Euro Cup, Asian Cup
  • Required: match
  • Effect: Must include cup name and "match"

Matching Examples:

  • ✅ "World Cup group stage match results" ← Has "World Cup" + "match"
  • ✅ "Euro Cup final match time" ← Has "Euro Cup" + "match"
  • ❌ "World Cup tickets on sale" ← Has "World Cup" but missing "match"

🎯 Configuration Tips

1. From Broad to Strict Strategy
# Step 1: Start with broad keywords for testing Artificial Intelligence AI ChatGPT # Step 2: After finding mismatches, add required words Artificial Intelligence AI ChatGPT +technology # Step 3: After finding noise, add filter words Artificial Intelligence AI ChatGPT +technology !advertisement !training
2. Avoid Over-Complexity

Not Recommended: Too many words in one group

Huawei OPPO Apple Samsung vivo OnePlus Meizu +phone +launch +sales !fake !repair !second-hand

Recommended: Split into precise groups

Huawei OPPO +new product Apple Samsung +launch phone sales +market

2.2 Advanced Settings (v3.2.0 new)

👉 Click to expand: Advanced Settings Tutorial
Keyword Sorting Priority

Config Location: config/config.yaml

report: sort_by_position_first: false # Sorting priority config
ValueSorting RuleUse Case
false (default)News count ↓ → Config position ↑Focus on popularity trends
trueConfig position ↑ → News count ↓Focus on personal priority

Example: Config order A, B, C, news count A(3), B(10), C(5)

  • false: B(10) → C(5) → A(3)
  • true: A(3) → B(10) → C(5)
Global Display Count Limit
report: max_news_per_keyword: 10 # Max 10 per keyword (0=unlimited)

Docker Environment Variables:

SORT_BY_POSITION_FIRST=true MAX_NEWS_PER_KEYWORD=10

Combined Example:

# config.yaml report: sort_by_position_first: true # Config order priority max_news_per_keyword: 10 # Global default max 10 per keyword
# frequency_words.txt Tesla Musk @20 # Key focus, show 20 (override global) Huawei # Use global config, show 10 BYD @5 # Limit to 5

Final Effect: Display in config order: Tesla(20) → Huawei(10) → BYD(5)

3. Push Mode Details

👉 Click to expand: Three Push Modes Detailed Comparison

Detailed Comparison Table

ModeTarget UsersPush TimingDisplay ContentTypical Use Case
Daily Summary
daily
📋 Managers/Regular UsersScheduled push (default hourly)All matched news of the day
+ New news section
Example: Check all important news of the day at 6 PM
Feature: See full-day trend, don't miss any hot topic
Note: Will include previously pushed news
Current Rankings
current
📰 Content CreatorsScheduled push (default hourly)Current ranking matches
+ New news section
Example: Track "which topics are hottest now" hourly
Feature: Real-time understanding of current popularity ranking changes
Note: Continuously ranked news appear each time
Incremental Monitor
incremental
📈 Traders/InvestorsPush only when newNewly appeared frequency word matchesExample: Monitor "Tesla", only notify when new news appears
Feature: Zero duplication, only see first-time news
Suitable for: High-frequency monitoring, avoid information disturbance

Actual Push Effect Example

Assume you monitor "Apple" keyword, execute once per hour:

Timedaily Mode Pushcurrent Mode Pushincremental Mode Push
10:00News A, News BNews A, News BNews A, News B
11:00News A, News B, News CNews B, News C, News DOnly News C
12:00News A, News B, News CNews C, News D, News EOnly News D, News E

Explanation:

  • daily: Cumulative display of all news of the day (A, B, C all retained)
  • current: Display current ranking news (ranking changed, News D on list, News A off list)
  • incremental: Only push newly appeared news (avoid duplicate disturbance)

Common Questions

💡 Encountered this problem? 👉 "Execute once per hour, news output in first execution still appears in next hour execution"

  • Reason: You might have selected daily (Daily Summary) or current (Current Rankings) mode
  • Solution: Change to incremental (Incremental Monitor) mode, only push new content

⚠️ Incremental Mode Important Notice

Users who selected incremental (Incremental Monitor) mode, please note:

📌 Incremental mode only pushes when there are new matching news

If you haven't received push notifications for a long time, it may be because:

  1. No new hot topics matching your keywords in current time period
  2. Keyword configuration is too strict or too broad
  3. Too few monitoring platforms

Solutions:

  • Solution 1: 👉 Optimize Keyword Configuration - Adjust keyword precision, add or modify monitoring keywords
  • Solution 2: Switch push mode - Change to current or daily mode for scheduled push notifications
  • Solution 3: 👉 Add More Platforms - Add more news platforms to expand information sources

4. Advanced Configuration - Hotspot Weight Adjustment

👉 Click to expand: Hotspot Weight Adjustment

Current default configuration is balanced.

Two Core Scenarios

Real-Time Trending Type:

weight: rank_weight: 0.8 # Mainly focus on ranking frequency_weight: 0.1 # Less concern about continuity hotness_weight: 0.1

Target Users: Content creators, marketers, users wanting to quickly understand current hot topics

In-Depth Topic Type:

weight: rank_weight: 0.4 # Moderate ranking focus frequency_weight: 0.5 # Emphasize sustained heat within the day hotness_weight: 0.1

Target Users: Investors, researchers, journalists, users needing deep trend analysis

Adjustment Method

  1. Three numbers must sum to 1.0
  2. Increase what's important: Increase rank_weight for rankings, frequency_weight for continuity
  3. Suggest adjusting 0.1-0.2 at a time, observe effects

Core idea: Users pursuing speed and timeliness increase ranking weight, users pursuing depth and stability increase frequency weight.

5. Push Format Reference

👉 Click to expand: Push Format Explanation

Push Example

📊 Trending Keywords Stats

🔥 [1/3] AI ChatGPT : 2 items

  1. [Baidu Hot] 🆕 ChatGPT-5 officially launched [1] - 09:15 (1 time)

  2. [Toutiao] AI chip concept stocks surge [3] - [08:30 ~ 10:45] (3 times)

━━━━━━━━━━━━━━━━━━━

📈 [2/3] BYD Tesla : 2 items

  1. [Weibo] 🆕 BYD monthly sales break record [2] - 10:20 (1 time)

  2. [Douyin] Tesla price reduction promotion [4] - [07:45 ~ 09:15] (2 times)

━━━━━━━━━━━━━━━━━━━

📌 [3/3] A-shares Stock Market : 1 item

  1. [Wallstreetcn] A-shares midday review [5] - [11:30 ~ 12:00] (2 times)

🆕 New Trending News (Total 2 items)

Baidu Hot (1 item):

  1. ChatGPT-5 officially launched [1]

Weibo (1 item):

  1. BYD monthly sales break record [2]

Updated: 2025-01-15 12:30:15

Message Format Explanation

Format ElementExampleMeaningDescription
🔥📈📌🔥 [1/3] AI ChatGPTPopularity Level🔥 High (≥10) 📈 Medium (5-9) 📌 Normal (<5)
[Number/Total][1/3]Rank PositionCurrent group rank among all matches
Keyword GroupAI ChatGPTKeyword GroupGroup from config, title must contain words
: N items: 2 itemsMatch CountTotal news matching this group
[Platform][Baidu Hot]Source PlatformPlatform name of the news
🆕🆕 ChatGPT-5 officially launchedNew MarkFirst appearance in this round
[number][1]High RankRank ≤ threshold, bold red display
[number][7]Normal RankRank > threshold, normal display
- time- 09:15First TimeTime when news was first discovered
[time~time][08:30 ~ 10:45]DurationTime range from first to last appearance
(N times)(3 times)FrequencyTotal appearances during monitoring
New Section🆕 New Trending NewsNew Topic SummarySeparately shows newly appeared topics

6. Docker Deployment

👉 Click to expand: Complete Docker Deployment Guide

Method 1: Quick Experience (One-Line Command)

Linux/macOS System:

# Create config directory and download config files mkdir -p config output wget https://raw.githubusercontent.com/sansan0/TrendRadar/master/config/config.yaml -P config/ wget https://raw.githubusercontent.com/sansan0/TrendRadar/master/config/frequency_words.txt -P config/

Or Manual Creation:

  1. Create config folder in current directory
  2. Download config files:

Final directory structure should be:

current directory/ └── config/ ├── config.yaml └── frequency_words.txt
docker run -d --name trend-radar \ -v ./config:/app/config:ro \ -v ./output:/app/output \ -e FEISHU_WEBHOOK_URL="your feishu webhook" \ -e DINGTALK_WEBHOOK_URL="your dingtalk webhook" \ -e WEWORK_WEBHOOK_URL="your wework webhook" \ -e TELEGRAM_BOT_TOKEN="your telegram_bot_token" \ -e TELEGRAM_CHAT_ID="your telegram_chat_id" \ -e EMAIL_FROM="your sender email" \ -e EMAIL_PASSWORD="your email password or auth code" \ -e EMAIL_TO="recipient email" \ -e CRON_SCHEDULE="*/30 * * * *" \ -e RUN_MODE="cron" \ -e IMMEDIATE_RUN="true" \ wantcat/trendradar:latest

Method 2: Using docker-compose (Recommended)

  1. Create Project Directory and Config:
    # Create directory structure mkdir -p trendradar/{config,docker} cd trendradar # Download config file templates wget https://raw.githubusercontent.com/sansan0/TrendRadar/master/config/config.yaml -P config/ wget https://raw.githubusercontent.com/sansan0/TrendRadar/master/config/frequency_words.txt -P config/ # Download docker-compose config wget https://raw.githubusercontent.com/sansan0/TrendRadar/master/docker/.env wget https://raw.githubusercontent.com/sansan0/TrendRadar/master/docker/docker-compose.yml

Final directory structure should be:

current directory/ ├── config/ │ ├── config.yaml │ └── frequency_words.txt └── docker/ ├── .env └── docker-compose.yml
  1. Config File Description:

    • config/config.yaml - Application main config (report mode, push settings, etc.)
    • config/frequency_words.txt - Keyword config (set your interested trending keywords)
    • .env - Environment variable config (webhook URLs and scheduled tasks)

    ⚙️ Environment Variable Override Mechanism (v3.0.5+)

    If you encounter config.yaml modifications not taking effect in NAS or other Docker environments, you can directly override configs via environment variables:

    Environment VariableCorresponding ConfigExample ValueDescription
    ENABLE_CRAWLERcrawler.enable_crawlertrue / falseEnable crawler
    ENABLE_NOTIFICATIONnotification.enable_notificationtrue / falseEnable notification
    REPORT_MODEreport.modedaily / incremental / currentReport mode
    PUSH_WINDOW_ENABLEDnotification.push_window.enabledtrue / falsePush time window switch
    PUSH_WINDOW_STARTnotification.push_window.time_range.start08:00Push start time
    PUSH_WINDOW_ENDnotification.push_window.time_range.end22:00Push end time
    FEISHU_WEBHOOK_URLnotification.webhooks.feishu_urlhttps://...Feishu Webhook

    Config Priority: Environment Variables > config.yaml

    Usage Method:

    • Modify .env file, uncomment and fill in needed configs
    • Or add directly in NAS/Synology Docker management interface's "Environment Variables"
    • Restart container to take effect: docker-compose up -d
  2. Start Service:

    # Pull latest image and start docker-compose pull docker-compose up -d
  3. Check Running Status:

    # View logs docker logs -f trend-radar # View container status docker ps | grep trend-radar

Method 3: Local Build (Developer Option)

If you need custom code modifications or build your own image:

# Clone project git clone https://github.com/sansan0/TrendRadar.git cd TrendRadar # Modify config files vim config/config.yaml vim config/frequency_words.txt # Use build version docker-compose cd docker cp docker-compose-build.yml docker-compose.yml # Build and start docker-compose build docker-compose up -d

Image Update

# Method 1: Manual update docker pull wantcat/trendradar:latest docker-compose down docker-compose up -d # Method 2: Using docker-compose update docker-compose pull docker-compose up -d

Service Management Commands

# View running status docker exec -it trend-radar python manage.py status # Manually execute crawler once docker exec -it trend-radar python manage.py run # View real-time logs docker exec -it trend-radar python manage.py logs # Display current config docker exec -it trend-radar python manage.py config # Display output files docker exec -it trend-radar python manage.py files # View help info docker exec -it trend-radar python manage.py help # Restart container docker restart trend-radar # Stop container docker stop trend-radar # Remove container (keep data) docker rm trend-radar

Data Persistence

Generated reports and data are saved in ./output directory by default. Data persists even if container is restarted or removed.

Troubleshooting

# Check container status docker inspect trend-radar # View container logs docker logs --tail 100 trend-radar # Enter container for debugging docker exec -it trend-radar /bin/bash # Verify config files docker exec -it trend-radar ls -la /app/config/

🤖 AI Analysis

TrendRadar v3.0.0 added MCP (Model Context Protocol) based AI analysis feature, allowing natural language conversations with news data for deep analysis.

⚠️ Important Notice Before Use

Critical: AI features require local news data support

AI analysis does not query real-time online data directly, but analyzes locally accumulated news data (stored in the output folder)

Usage Instructions:

  1. Built-in Test Data: The output directory includes news data from November 1-15, 2025 by default for quick feature testing

  2. Query Limitations:

    • ✅ Only query data within available date range (Nov 1-15)
    • ❌ Cannot query real-time news or future dates
  3. Getting Latest Data:

    • Test data is for quick experience only, recommend deploying the project yourself to get real-time data
    • Follow Quick Start to deploy and run the project
    • After accumulating news data for at least 1 day, you can query the latest trending topics

1. Quick Deployment

Cherry Studio provides GUI config interface, 5-minute quick deployment, complex parts are one-click install.

Illustrated Deployment Tutorial: Now updated to my WeChat Official Account (see FAQ & Support), reply "mcp" to get

Detailed Deployment Tutorial: README-Cherry-Studio.md

Deployment Mode Description:

  • STDIO Mode (Recommended): One-time configuration, no need to reconfigure later. The illustrated deployment tutorial only demonstrates this mode's configuration.
  • HTTP Mode (Alternative): If STDIO mode configuration encounters issues, you can use HTTP mode. This mode's configuration is basically the same as STDIO, but only requires copy-pasting one line, less error-prone. The only thing to note is that you need to manually start the service before each use. For details, refer to the HTTP mode section at the bottom of README-Cherry-Studio.md.

2. Learning to Talk with AI

Detailed Conversation Tutorial: README-MCP-FAQ.md

Question Effect:

👉 Click to expand: View AI Conversation Example

💡 Tip: Actually not recommended to ask multiple questions at once. If your chosen AI model cannot even sequentially call as shown below, suggest switching models.

MCP usage effect

🔌 MCP Clients

TrendRadar MCP service supports standard Model Context Protocol (MCP), can connect to various AI clients supporting MCP for smart analysis.

Supported Clients

Note:

  • Replace /path/to/TrendRadar with your actual project path
  • Windows paths use double backslashes: C:\\Users\\YourName\\TrendRadar
  • Remember to restart after saving
👉 Click to expand: Claude Desktop

Config File Method

Edit Claude Desktop's MCP config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json

Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

Config Content:

{ "mcpServers": { "trendradar": { "command": "uv", "args": [ "--directory", "/path/to/TrendRadar", "run", "python", "-m", "mcp_server.server" ], "env": {}, "disabled": false, "alwaysAllow": [] } } }
👉 Click to expand: Cursor

Method 1: HTTP Mode

  1. Start HTTP Service:

    # Windows start-http.bat # Mac/Linux ./start-http.sh
  2. Configure Cursor:

    Project Level Config (Recommended): Create .cursor/mcp.json in project root:

    { "mcpServers": { "trendradar": { "url": "http://localhost:3333/mcp", "description": "TrendRadar News Trending Aggregation Analysis" } } }

    Global Config: Create ~/.cursor/mcp.json in user directory (same content)

  3. Usage Steps:

    • Restart Cursor after saving config
    • Check connected tools in chat interface "Available Tools"
    • Start using: Search today's "AI" related news

Method 2: STDIO Mode (Recommended)

Create .cursor/mcp.json:

{ "mcpServers": { "trendradar": { "command": "uv", "args": [ "--directory", "/path/to/TrendRadar", "run", "python", "-m", "mcp_server.server" ] } } }
👉 Click to expand: VSCode (Cline/Continue)

Cline Configuration

Add in Cline's MCP settings:

HTTP Mode:

{ "trendradar": { "url": "http://localhost:3333/mcp", "type": "streamableHttp", "autoApprove": [], "disabled": false } }

STDIO Mode (Recommended):

{ "trendradar": { "command": "uv", "args": [ "--directory", "/path/to/TrendRadar", "run", "python", "-m", "mcp_server.server" ], "type": "stdio", "disabled": false } }

Continue Configuration

Edit ~/.continue/config.json:

{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "uv", "args": [ "--directory", "/path/to/TrendRadar", "run", "python", "-m", "mcp_server.server" ] } } ] } }

Usage Examples:

Analyze recent 7 days "Tesla" popularity trend Generate today's trending summary report Search "Bitcoin" related news and analyze sentiment
👉 Click to expand: Claude Code CLI

HTTP Mode Configuration

# 1. Start HTTP service # Windows: start-http.bat # Mac/Linux: ./start-http.sh # 2. Add MCP server claude mcp add --transport http trendradar http://localhost:3333/mcp # 3. Verify connection (ensure service started) claude mcp list

Usage Examples

# Query news claude "Search today's Zhihu trending news, top 10" # Trend analysis claude "Analyze 'artificial intelligence' topic popularity trend for the past week" # Data comparison claude "Compare Zhihu and Weibo platform attention on 'Bitcoin'"
👉 Click to expand: MCP Inspector (Debug Tool)

MCP Inspector is the official debug tool for testing MCP connections:

Usage Steps

  1. Start TrendRadar HTTP Service:

    # Windows start-http.bat # Mac/Linux ./start-http.sh
  2. Start MCP Inspector:

    npx @modelcontextprotocol/inspector
  3. Connect in Browser:

    • Visit: http://localhost:3333/mcp
    • Test "Ping Server" function to verify connection
    • Check "List Tools" returns 14 tools:
      • Date Parsing: resolve_date_range
      • Basic Query: get_latest_news, get_news_by_date, get_trending_topics
      • Smart Search: search_news, search_related_news_history
      • Advanced Analysis: analyze_topic_trend, analyze_data_insights, analyze_sentiment, find_similar_news, generate_summary_report
      • System Management: get_current_config, get_system_status, trigger_crawl
👉 Click to expand: Other MCP-Compatible Clients

Any client supporting Model Context Protocol can connect to TrendRadar:

HTTP Mode

Service Address: http://localhost:3333/mcp

Basic Config Template:

{ "name": "trendradar", "url": "http://localhost:3333/mcp", "type": "http", "description": "News Trending Aggregation Analysis" }

STDIO Mode (Recommended)

Basic Config Template:

{ "name": "trendradar", "command": "uv", "args": [ "--directory", "/path/to/TrendRadar", "run", "python", "-m", "mcp_server.server" ], "type": "stdio" }

Notes:

  • Replace /path/to/TrendRadar with actual project path
  • Windows paths use backslash escape: C:\\Users\\...
  • Ensure project dependencies installed (ran setup script)

☕ FAQ & Support

If you want to support this project, you can search Tencent Charity on WeChat and donate to Education Support Programs as you wish

Thanks to those who participated in the one-yuan donation! You are listed in the Acknowledgments at the top. Your support gives more motivation to open source maintenance. Personal donation QR code has been removed.

  • GitHub Issues: Suitable for targeted answers. Please provide complete info when asking (screenshots, error logs, system environment, etc.)
  • WeChat Official Account: Suitable for quick consultation. Suggest priority to communicate in public comment area of related articles. If private message, please use polite language 😉
  • 💡 Deployment successful? Come to our official account to share your experience! Your likes and suggestions are the driving force for continuous updates~
WeChat Official Account


🪄 Sponsors

🤖 302.AI - Enterprise AI Resource Platform

302.AI is a pay-as-you-go enterprise-level AI resource platform Providing the latest and most comprehensive AI models and APIs on the market, plus various ready-to-use online AI applications

👉 Click to expand: 302.AI Usage Tutorial

Step 1: Get API Key

  1. After registration, go to Management Dashboard at top right
  2. Click API Keys on the left
  3. Find default API KEY at page bottom, click eye icon to view, then copy (⚠️ Note: Don't click the copy button on the far right)

Step 2: Configure in Cherry Studio

  1. Open Cherry Studio, go to settings
  2. Select "302.AI" as model provider
  3. Paste the API Key you just copied
  4. Click Manage, now you can use all supported AI models

Tip: Cherry Studio has natively integrated 302.AI, you can see the complete model list after configuration.

Q: How long does $1 free credit last? A: Depends on usage frequency and model selection, can run multiple test sessions.

Q: What after free credit runs out? A: You can top up as needed, pay-as-you-go. Major AI model prices are now relatively affordable.

Tracking so many trending topics daily, writing reports, replying messages making your wrists tired?

Try「FlashSpeak」AI Voice Input - Speak instead of type, 4x faster ⚡

On-device Model • Lightning Fast • Absolute Privacy • Mac/Win Support

From reading trends to content output, double your efficiency 👇


Common Questions

👉 Click to expand: Q1: HTTP Service Cannot Start?

Check Steps:

  1. Confirm port 3333 is not occupied:

    # Windows netstat -ano | findstr :3333 # Mac/Linux lsof -i :3333
  2. Check if project dependencies installed:

    # Re-run install script # Windows: setup-windows.bat or setup-windows-en.bat # Mac/Linux: ./setup-mac.sh
  3. View detailed error logs:

    uv run python -m mcp_server.server --transport http --port 3333
  4. Try custom port:

    uv run python -m mcp_server.server --transport http --port 33333
👉 Click to expand: Q2: Client Cannot Connect to MCP Service?

Solutions:

  1. STDIO Mode:

    • Confirm UV path correct (run which uv or where uv)
    • Confirm project path correct and no Chinese characters
    • Check client error logs
  2. HTTP Mode:

    • Confirm service started (visit http://localhost:3333/mcp)
    • Check firewall settings
    • Try using 127.0.0.1 instead of localhost
  3. General Checks:

    • Restart client application
    • Check MCP service logs
    • Use MCP Inspector to test connection
👉 Click to expand: Q3: Tool Call Failed or Returns Error?

Possible Reasons:

  1. Data Does Not Exist:

    • Confirm crawler has run (have output directory data)
    • Check query date range has data
    • Check available dates in output directory
  2. Parameter Error:

    • Check date format: YYYY-MM-DD
    • Confirm correct platform ID: zhihu, weibo, etc.
    • See parameter descriptions in tool docs
  3. Config Issues:

    • Confirm config/config.yaml exists
    • Confirm config/frequency_words.txt exists
    • Check config file format is correct

📚 Related Projects

4 Related Articles (Chinese):

AI Development:

  • If you have niche requirements, you can develop based on my project yourself, even with zero programming experience
  • All my open-source projects use my own AI-assisted software to improve development efficiency, this tool is now open-source
  • Core Function: Quickly filter project code to feed AI, you just need to add personal requirements
  • Project Address: https://github.com/sansan0/ai-code-context-helper

Other Projects

📍 Chairman Mao's Footprint Map - Interactive dynamic display of complete trajectory 1893-1976. Welcome comrades to contribute data

Bilibili Comment Data Visualization Analysis Software

Project Workflow Diagram

Star History Chart


📄 License

GPL-3.0 License


About

https://github.com/sansan0/TrendRadar.git 🎯 告别信息过载,AI 助你看懂新闻资讯热点,简单的舆情监控分析 - 多平台热点聚合+基于 MCP 的AI分析工具。监控35个平台(抖音、知乎、B站、华尔街见闻、财联社等),智能筛选+自动推送+AI对话分析(用自然语言深度挖掘新闻:趋势追踪、情感分析、相似检索等13种工具)。支持企业微信/个人微信/飞书/钉钉/Telegram/邮件/ntfy/bar

25.12 MiB
0 forks0 stars1 branches23 TagREADMEGPL-3.0 license
Language
Python90.7%
HTML5.6%
Shell1.2%
Dockerfile0.5%
Others2%