Now if you want to add something to the end of the description,
you can pass it via the addons parameter. Also moved a line
that was duplicated to reduce the function length.
Added min_length parameter, as well as an addon parameter that
might be used in the future to add extra text to the description
where needed.
Next up will be checking for media in the entry and adding a
second embed field or attachment so the media can be previewed
or listened to/watched right in the Discord post.
Hashing now takes the sha3_512 hash of both the title and
the published time, because some feeds (like weather alerts)
will have the same title all the time, for every entry.
The description cutoff now goes backwards until it finds a
space character, then it sets the cutoff there. Also, the
length can now be passed as a parameter, with default value
of 250. Might also add minimum length as a parameter too.
The HTML regex wasn't working because I was missing some
really obvious capture groups. The regex filter is really only
for the kernel.org Releases Feed, just to make it look a bit
cleaner. We don't actually need the direct links because the
post's title already links directly to the front page. We mostly
just want to know there's been a release.
Some logging parameters were changed to make the log less
cluttered by default. Going to write a logrotate config that
will be included in the README or something to help people with
rotating the logs automatically. Also added a few small
clarifying comments, as well as an IDEA!
app_config is global pending the next commit which will
separate out all the config file handling from main() as the
LSP was saying the main function had become too complex.
* Changed the preview length to 250 characters
* Changed the version in the user-agent string
* Cleaned up paths, switching to user paths
* Updated html regex filter to correctly remove : . /
* Various formatting changes from black
* Wrapped published_time in try/except
I figured out what the issue was. Discord was trying to tell
me there was a problem with the embed I was sending. The provider
value was removed, and with some other tweaks it all started
working. Heavy, heavy facepalm.
