Dome/GTS-Federator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Dome
2026-04-19 19:14:18 +02:00
parent 96f7161ef0
commit 46ed0054a7
1 changed files with 12 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+12 -5
View File
@@ -58,11 +58,18 @@ The bot monitors a configurable list of RSS feeds. For every new entry found, it
### Efficient Resource Management ### Efficient Resource Management
Unlike many other fetchers, GTS-Federator is designed with a "Single User" philosophy. It uses a persistent HTTP session and a local JSON-based memory to ensure that your instance isn't hammered with redundant requests. Unlike many other fetchers, GTS-Federator is designed with a "Single User" philosophy. It uses a persistent HTTP session and a local JSON-based memory to ensure that your instance isn't hammered with redundant requests.
### Real-Time Analytics ### Activity Summary & Logs
After every run, the bot provides a clean summary of its activity:
- **Runtime:** How long the discovery took. #### Real-Time Analytics
- **New Posts:** Number of successfully federated statuses. After every fetch cycle, the bot provides a clean summary of its activity:
- **Instance Growth:** Tracking how many new Fediverse domains your instance has discovered through the process. - **Time:** Total duration of the discovery run.
- **New Posts:** Count of unique, previously unseen posts federated into your instance.
- **Instance Growth:** Total known Fediverse domains and the (+X) growth detected in this cycle.
#### Run Statistics
Between cycles, the bot summarizes the current status:
- 📊 **Fetched X Posts from Y RSS-Feeds:** Shows the number of new posts successfully added (Delta) vs. the total number of RSS sources monitored.
- ⏰ **Next scheduled run:** Displays the timestamp for the upcoming discovery cycle, ensuring you can monitor the bot’s uptime.
### Adaptive Pausing & Timezone Support ### Adaptive Pausing & Timezone Support
The bot calculates its next run based on your local time. With built-in timezone support, the logs will always show you exactly when the next discovery cycle starts, matching your local wall clock. The bot calculates its next run based on your local time. With built-in timezone support, the logs will always show you exactly when the next discovery cycle starts, matching your local wall clock.