Releases: Qolors/FeedCord
v3.0.4
v3.0.3
v3.0.3
Bug Fixes
- Corrected Successful Url Count
- Gracefully Handles timeout exceptions when hanging on a url feed
- Increased Http Request Timeout to 30 seconds
- Dumps Critical Error stack trace on Crash. This was hid in previous versions. Not sure why. Will help with critical error debugging
- Posting to Discord now properly releases from our SemaphoreSlim resource when it fails
- Timeout/Bad requests will now properly release from our SemaphoreSlim resource. Before it did not handle the exception, and would never release
Additions
- Implemented Concurrent Batch Logger for ordered logs. We are working with asynchronous processes and without the Batch Logger the printed logs are scattered and unordered
Batch Logger is still a WIP. It currently has the following functionality:
- Tells Time Started & Stopped for the Instance
- Will display each Feed's most recent post (to help investigate issues and confirm it's running correctly)
- Will call out feed urls that are causing issues
For Warning & Error messages in logs, those are still printed real time when they happen and not aggregated by our Batch Logger
v3.0.2
v3.0.2 - Bug Patch
Fixes #48
- This is a fix for misconfigured servers and/or feeds in their encoding. It will always trust the feed's encoding rule.
Fixes #51
- Github feeds lack the Published field for feed items - it will now fallback to Updated field.
Fixes #50
- For this issue, there are too many variables for parsing the XML YouTube url programmatically.. This patch support directly feeding the xml link in to your Youtube section to be more reliable
Other
- Added outputting the latest Post found in the feed when there aren't any new posts found to help with debugging. More to come with improved logging
v3.0.1
v3.0.0
v3.0.0 Release is here!
FeedCord is back in active development!
This release is focused on stability, performance, and user flexibility.
Highlights
- Refactoring & Improved Architecture
- Major portions of the codebase have been revamped for better readability and maintainability. This sets the stage for future feature development. Special thanks to @xavier-hernandez for the pull request and paving the start of it!
Enhanced Request Handling & Retries
- User-Agent Cycling for failed GET requests, reducing the chance of being blocked by certain RSS or web endpoints.
- Multiple Retry Attempts on retrieving images or RSS items, ensuring more reliable fetching even under poor network conditions.
- Better Parsing of RSS Items to handle diverse RSS feed formats with improved error tolerance.
Additional Properties
For those upgrading from 2.x, please check the new file structure. in v3, a bare bones config file looks like this:
{
"Instances": [
{
"Id": "My First News Feed",
"YoutubeUrls": [
""
],
"RssUrls": [
""
],
"Forum": false,
"DiscordWebhookUrl": "...",
"RssCheckIntervalMinutes": 25,
"EnableAutoRemove": false,
"Color": 8411391,
"DescriptionLimit": 250,
"MarkdownFormat": false,
"PersistenceOnShutdown": true
}
],
"ConcurrentRequests": 40
}- ConcurrentRequests - How many concurrent HTTP requests all FeedCord instances can have going at one time.
- MarkdownFormat - markdown styled posts if set to true
- PersistenceOnShutdown - local file write on restart/stop to save last run dates. This allows for posting any missed items while FeedCord was stopped or restarted if set to true
You can reference it here
Docker
For Docker images, whether you are arm64 or amd64, everyone now pulls from qolors/feedcord:latest
Cheers!
Contributors
Assets 2
v2.1.1 - GZip Support & Author Sourcing from Feed Items
Update Changelog
v2.1.0 - README Updates & Multiple New Post Handling
This version will now handle grabbing multiple posts from each feed if the posts are newer than the last check's date.
For reference - previous versions would behave like so:
- Fetch RSS Feed Content
- --> Check if newest post is newer than the last check's Date/Time stamp
- --> If newest post is newer, post.
2.1.0 version now behaves like so:
- Fetch RSS Feed Content
- --> Grab all items in feed
- --> For each item, if it is newer than the last check's Date/Time stamp post it
- --> Sets the check Date/Time stamp to be the newest from the group of items
2.1.0 version now has a hard-coded 10 second pause between posts to
- This will respect Discord's Rate Limiting for a large amount of posts between checks
- 10 seconds is to see if pausing between posts will help rid of the
Original message was deleted"bug" in Forums
v2.0.1 - Atom Parsing Improvements
This is a small patch to add better supporting of atom feed parsing
v2.0.0 - Discord Forums & Multiple Webhooks Support
This is a new Major Release that adds some great features for scaling multiple instances as well as utilizing Discord's 'newer' channel types Forums
- Multiple Webhooks Support
- Discord Forums Support
- Configuration Properties more streamlined making a good amount of properties only optional
You can check more of the updates and newly added requirements here in the guide
Appreciate the support & feature requests coming in - enjoy!
v1.3.0 - More Robust Feed Parsing & Description Length Configuration
This release utilizes a more reliable parsing library & added a configuration property to choose the description word length for new posts.
{
... Rest of properties
"Color": 8411391,
"DescriptionLimit": 200 <------ If this is set to 0, it will print to the maximum length Discord allows
}
Parsing Library Implemented - FeedReader