Tube Archivist v0.4.0 release notes

Project updates, potentially Breaking Changes

After trying and repeatedly failing to correctly handle Title and Channel Names for media files, we have decided to standardize that to <channel-id>/<video-id>.mp4.
- Before updating, make sure Tube Archivist has all media files at the expected file system location.
- There is a migration at startup that will reorganize all your files.
- Only the default naming convention is supported for the migration. If you made changes there, this will likely fail and require you to migrate your files manually.
- Monitor your startup logs for a progress message. Any errors will log there. If you see messages similar to did not find expected video/subtitle at ..., rename that manually to the expected path and restart for the migration to complete.
- Also see FAQ.
There is now a Jellyfin integration released: tubearchivist/tubearchivist-jf
- This repos is renamed from tubearchivist/jellyfin to avoid confusion, that this is not a fork of jellyfin…
- Shoutout to @jonasrosland for taking the initiative for the docker build
The Docs now got a dedicated URLs page to document how TA treats URLs from YouTube, docs.
As mentioned previously, Redis now publishes ARM builds for all it’s extensions, including RedisJSON. To avoid confusion, I’ll delete our now outdated custom build bbilly1/rejson, use redis/redis-stack-server instead.

Changed file system organization to <channel-id>/<video-id>.mp4.
Changed trusted host configuration to add localhost and tubearchivist to defaults.
Changed comment extraction to ignore errors by default, so the rest of comments can continue.
[API] Date strings are now formatted in ISO format for consistency.