Bok Bok (200 bpm (HYper JOhn webCoRE Edit) 🕊
супер_смурф_presents:
Kerloed — «Bass Carnage»
featuring remixes by HYper JOhn, Dpcld and Corbina Telecom
По мере того, как создавался этот альбом, в воздухе витал вихрь соседской напряженности, заряженный эмоциональными искрами. Когда гнев пожилой соседки достиг своего апогея, ее яростные выпады эхом прокатились по всему подъезду:
“Дропай уже!” — пронзительный голос бабки доносился до ее соседа-хулигана сверху…
Kerloed представляет свой дебютный альбом — долгожданную работу, в которую вошли его оригинальные миксы, а также ремиксы от близких друзей и мастеров жанра.
Мастеринг: HYper JOhn
супер смурф рекордз, 2025
#tracks#release
🎧Погружение в историю Башкирии через джаз-рок
Исполнитель
«Фирма Мелодия» переиздает пластинку, впервые вышедшую во времена позднего СССР, в 1990-м году. Альбом «Ансамбль “Орлан”» стал дебютной и самой известной записью уфимского коллектива под управлением Олега Киреева.
История «Орлана» связана с разными периодами в жизни страны. После ограничений для джазовых музыкантов в середине XX века последовали осторожные разрешения на исполнения и фестивали. По словам историка джаза Алексея Баташёва, коллективы почти принуждали работать с народными мелодиями и вплетать их в произведения. Как только контроль ослаб, многие ансамбли избавились от этого приема, а джаз, смешанный с народными мотивами, двинулся из центральных городов на восток. Где, например, в Уфе и появился ансамбль «Орлан».
Музыка
Олег Киреев, не чувствовал давления и свободно экспериментировал: «Джаз – ближайший родственник фольклора, а потому нас интересуют народные традиции, то, что живо вокруг нас, хотя и от джазовой классики мы ни в коем случае не отрекаемся». Свой основной инструмент, саксофон, Киреев обрел почти случайно: в предперестроечные годы в музыкальном училище был высокий конкурс на все специальности, кроме саксофона. Первый собственный коллектив Киреев собрал в 1984-м, а сделавший его известным в СССР и за его пределами «Орлан» – в 1986-м.
Мысль остановиться на джаз-фьюжне, пропитанном национальными мелодиями, пришла сама собой. «На праздниках была традиция, которой сейчас уже нет: родственники […] начинали петь – башкирские, татарские, русские песни, всё вперемешку. Народная музыка окружала нас повсюду», – позже говорил музыкант.
Мнение
«Башкирские легенды», родившиеся из одноименной концертной программы, не только звучат непривычно – тут есть, например, микс горлового пения и саксофона, – но и имеют небанальную историю. «Легенды» ездили по фестивалям, и в Днепропетровске ансамбль познакомился с Алексеем Баташёвым, историком и популяризатором джаза. Тот позвал музыкантов в Москву, где они записали весь материал всего за два дня в студии «Мелодии». Киреев называл процесс «мини-спектаклем, погружением в историю Башкирии через джаз-рок» и считал, что на записи им «каким-то чудом удалось воссоздать атмосферу, которая была на концертах». Эта запись стала их единственной студийной работой.
Денис Бояринов
Спустя почти 35 лет «Мелодия» вновь издает «Башкирские легенды» на виниле.
→ Слушать
#release
#Releasev2.9.0: Telegraph-related revert, skip cert verification, and more
BREAKING CHANGES
Media (image and video) are no longer uploaded when generating Telegraph posts due to Telegraph disabling media upload. (first introduced in v2.6.0)
Addition
● Disable TLS certificate verification: The environment variable VERIFY_TLS has been added to disable (when set to 0) or enable (when set to 1, default) TLS certificate verification. This is useful when subscribing to feeds with their TLS misconfigured. Note: Disabling TLS certificate verification is not recommended and should only be used as a last resort.
Enhancements
● Sanitize post title and author: The title and author of a post (RSS item or Atom entry) are now sanitized to prevent unexpected formatting issues. In particular, unexpected whitespaces and linebreaks are removed, and any HTML elements are stripped. This helps display them correctly in Telegram messages as well as Telegraph posts.
● Improve robustness on Railway.app: Some Railway-specific environment variables are recognized to improve robustness on Railway.app. In particular, DATABASE_PRIVATE_URL and DATABASE_PUBLIC_URL will be used when DATABASE_URL is unavailable or invalid. This should solve most database connection issues on Railway.app.
● Minor refactor: Some internal functions have been refactored to improve readability and maintainability.
Bug fixes
● /version not working: When installed from PyPI (e.g. pip install rsstt), the /version command might cause an error. This was a regression introduced in v2.7.0.
● Bot managers can set monitoring intervals shorter than limit: Due to the breaking change introduced in v2.8.0, the privilege of bot managers to set intervals shorter than the minimal monitoring interval became useless. While v2.8.0 only applied this limitation when monitoring the updates of feeds, this release also applies it to the attempts by bot managers to change the monitoring interval for a subscription. Note: bot managers can always lower the minimal monitoring interval by adjusting minimal_interval in /set_option (see also Advanced Settings), but doing so will also permit anyone who is able to use the bot to set shorter intervals.
● Minor bug fixes
Bot | Channel | Group | GitHub repo | Patreon | Ko-fi
#Releasev2.9.0: 与 Telegraph 相关的 revert、跳过证书校验和更多
重大变更
由于 Telegraph 禁用了媒体上传，生成 Telegraph 文章时不再上传媒体 (图片与视频) 。(在 v2.6.0 中首次引入)
新增功能
● 关闭 TLS 证书验证: 环境变量 VERIFY_TLS 已被添加以禁用 (设置为 0 时) 或启用 (设置为 1 时，默认) TLS 证书验证。当订阅 TLS 被错误配置的 feed 时，这很有用。注意：不建议禁用 TLS 证书验证，只应用作最后手段。
增强
● 净化文章标题和作者: 文章 (RSS item 或 Atom entry) 的标题和作者现在被净化以防止意外的格式问题。特别是，预期外的空格和换行符被移除，任何 HTML 元素都被剥离。这有助于在 Telegram 消息以及 Telegraph 文章中正确显示它们。
● 改善在 Railway.app 上的稳健性: 一些特定于 Railway 的环境变量被识别以提高在 Railway.app 上的稳健性。特别是，当 DATABASE_URL 不可用或无效时，将使用 DATABASE_PRIVATE_URL 和 DATABASE_PUBLIC_URL。这应该解决在 Railway.app 上的大多数数据库连接问题。
● 次要的重构: 重构了一些内部函数以提高可读性和可维护性。
Bug 修复
● /version 不工作: 当从 PyPI 安装时 (例如 pip install rsstt), /version 命令可能会导致错误。这是在 v2.7.0 中引入的一个回归 (regression)。
● Bot 管理员可以设置比限制更短的监控间隔: 由于 v2.8.0 中引入的一个重大变更，bot 管理员可以设置比最小监控间隔更短的间隔的特权变得毫无意义。虽然 v2.8.0 只在监控 feed 的更新时应用了这个限制，但这个版本也将它应用于 bot 管理员的更改订阅监控间隔的尝试。注意: bot 管理员总是可以通过调整 /set_option 中的 minimal_interval 来降低最小监控间隔 (另请参阅 高级设置)，但这样做也会允许任何能够使用 bot 的人设置更短的间隔。
● 次要的 bug 修复
官方 bot 实例 | 加入频道 | 加入群组 | GitHub 仓库 | 捐赠支持
#Releasev2.8.0: Retain post order, rewritten monitor, and more
Highlights
● Retain post order: Retain the order of posts in a feed when sending them. Previously, all new posts were sent simultaneously, losing their order within the feed. Note: Posts from different feeds are still sent simultaneously, so it is expected to see them interlaced.
● Rewritten monitor: The feed monitor has been rewritten for flexibility and robustness. It is now more memory-efficient and can smooth out spikes in CPU usage.
Enhancements
● Print Telegram user info of bot: Print the bot's Telegram user info when the bot is started. This is to help bot managers to find the bot's username and user ID when deploying the bot.
● Minor refactor: Some internal functions have been refactored to improve performance and maintainability.
Bug fixes
● Exit with 0 when disconnected: If the bot was logged out due to a network error or Telegram DC degradation, it would exit with exit-code 0. This led to confusion when the bot was running in a container or as a service. Now the bot will exit with exit-code 100 when disconnected.
● Unable to handle completely empty posts: Fix AttributeError caused by completely empty posts. They are ignored now.
● Minor bug fixes
Bot | Channel | Group | GitHub repo | Patreon | Ko-fi
#Releasev2.8.0: 保留文章顺序，重写的监视器和更多
亮点
● 保留文章顺序: 在发送文章时保留文章在 feed 中的顺序。先前，所有新文章都被同时发送，失去了它们在 feed 中的顺序。注意：来自不同 feed 的文章仍然同时发送，因此预计会看到它们交错。
● 重写的监视器: Feed 监视器已被重写，以提高灵活性和稳健性。它现在更节省内存，并且可以平滑 CPU 使用率的波动。
增强
● 打印 bot 的 Telegram 用户信息: 在 bot 启动时打印 bot 的 Telegram 用户信息。这是为了帮助 bot 管理员在部署 bot 时找到 bot 的用户名和用户 ID。
● 次要的重构: 重构了一些内部函数以提高性能和可维护性。
Bug 修复
● 断开连接后以 0 退出: 过去，如果 bot 由于网络错误或 Telegram DC 降级而被登出，它将以退出码 0 退出。当 bot 在容器中或作为服务运行时，这会导致混乱。现在，当断开连接时，机器人将以退出码 100 退出。
● 无法处理完全空白的文章: 修复由完全空白的文章引起的 AttributeError。它们现在会被忽略。
● 次要的 bug 修复
官方 bot 实例 | 加入频道 | 加入群组 | GitHub 仓库 | 捐赠支持
#Releasev2.6.0: Upload media to Telegraph, management enhancements
Highlights
● Upload media to Telegraph: When generating Telegraph posts, images as well as videos will be uploaded to Telegraph. This is to solve anti-hotlinking issues and improve the load performance of posts. This feature depends on the latest version of the media relay server (Rongronggg9/rsstt-img-relay). Those images and videos that are too large to be uploaded will still be proxied by wsrv.nl (environment variable IMAGES_WESERV_NL) or media relay server (environment variable IMG_RELAY_SERVER). Thanks #431 for inspiration.
Addition
● Multiple managers: The environment variable MANAGER now accepts a single user ID as well as a list separated by ;, ,, (space), (linebreak), or (tab). Each user in the list will be able to manage the bot equally.
● Customizable error logging chat: Previously, some error logs were always sent to the bot manager. To make it more flexible, a new environment variable ERROR_LOGGING_CHAT, accepting a single user/channel/group ID, has been added. If set, these error logs will be sent to the specified chat. Otherwise, the first user ID in MANAGER will be selected as default.
Enhancements
● Strip whitespaces in <li>: Strip whitespaces (including linebreaks) in <li> (list item) to improve readability. Only the leading and trailing whitespaces (including linebreaks) are stripped.
● Only set "force reply" in groups: Only set ReplyKeyboardForceReply to True in groups. Previously, it was also set in private chats. See also "Bug fixes" below.
● Minor refactor: Some internal functions have been refactored to improve readability and maintainability.
Bug fixes
● (/sub) "force reply" not cleared: Both /sub and /import set ReplyKeyboardForceReply to True to force the user to reply to the bot. However, due to a bug of Telegram, it keeps effective even if the user has made a reply, making the reply bar always reappear. Previously, a workaround has been applied to /import by deleting the prompt message containing ReplyKeyboardForceReply after the user has made a reply (see also #170). But /sub was forgotten at that time. Now the workaround has been applied to /sub too.
● "Remote" /lang unavailable: Fix a bug preventing users from using the /lang command "remotely".
Bot | Channel | Group | GitHub repo | Patreon
#Releasev2.4.1: Minor enhancements, bug fixes, and Happy New Year! 🎉
Enhancements
● wsrv.nl via relay: Try to use wsrv.nl (environment variable IMAGES_WESERV_NL) via the media relay server (environment variable IMG_RELAY_SERVER). This is a workaround for images from domains/TLDs banned by wsrv.nl or CDNs that ban wsrv.nl. It can hopefully reduce the frequency of seeing "invalid media" in messages since RSStT uses wsrv.nl heavily to convert images into formats accepted by Telegram DCs. See also #369.
● Append enclosures to Telegraph post: Append enclosures (if any) to Telegraph post if any. Previously, enclosures can only be sent in Telegram messages, but not in Telegraph posts.
● Dependencies update: Bumped most outdated dependencies to the latest version. An optional dependency isal has been added to slightly improve the performance of entry hashing.
● L10n update: Localizations have been updated.
● Misc refactoring: Some code has been refactored to improve readability and maintainability.
Bug fixes
● "Remote" /test unavailable: Fix a bug preventing the bot manager from using the /test command "remotely".
● Resized images still too big: Fix a bug causing images resized by wsrv.nl to be sometimes too big (exceed the 5MiB limitation of Telegram DC) to send.
● Sinaimg images not parsed properly: Fix the URL regex of Sinaimg images. It can hopefully reduce the frequency of seeing "invalid media" in messages.
● WEBP fully fetched regardless of fetch limit: Fix a bug causing WEBP without Content-Length header to be fully fetched regardless of the fetch limit.
● Entry hashing for monitor and sub not unified: Unify the entry hashing for monitor and sub. Previously, the entry hashing for monitor and sub is not unified, which may cause the bot to send persisting entries (posts) after a feed is subscribed for the first time.
Bot | Channel | Group | GitHub repo | Patreon
#Releasev2.4.1: 次要的增强和 bug 修复，以及新年快乐！🎉
增强
● 经反代的 wsrv.nl: 尝试通过媒体反代服务器 (环境变量 IMG_RELAY_SERVER) 使用 wsrv.nl (环境变量 IMAGES_WESERV_NL)。这是对那些来自被 wsrv.nl 封禁的域名或将 wsrv.nl 封禁的 CDN 的图片的变通解决方案。考虑到 RSStT 大量使用 wsrv.nl 将图片转换为 Telegram DC 所接受的格式，这有望减少在消息中见到 "Invalid media" 的频率。另请参阅 #369。
● 将 enclosure 附加到 Telegraph 文章: 如果有的话，将 enclosure (附件) 附加到 Telegraph 文章。先前，enclosure 只能在 Telegram 消息中发送，而无法在 Telegraph 文章中发送。
● 依赖项更新： 将大部分过时的依赖项更新到了最新版本。引入可一个可选依赖 isal 用于稍微提升条目散列的性能。
● 本地化更新: 本地化已被更新。
● 杂项重构: 重构了一些代码以提高可读性和可维护性。
Bug 修复
● “远程” /test 不可用：修复阻止 bot 管理员“远程”使用 /test 命令的错误。
● 调节尺寸后的图像仍然太大: 修复了一个错误，这个错误导致经过 wsrv.nl 调节尺寸后的图像有时候仍然太大（超过 Telegram DC 的 5MiB 限制）以至于无法发送。
● Sinaimg 图片未被正确解析: 修复了针对 Sinaimg (微博图床) 图片的正则表达式。这有望减少在消息中见到 "Invalid media" 的频率。
● WEBP 被完全获取，而没有考虑获取限制: 修复了一个导致不带有 Content-Length 标头的 WEBP 被完全获取，而没有考虑获取限制的错误。
● 监视器和订阅的条目散列不统一: 统一监视器和订阅的条目散列。先前，监视器和订阅的条目散列不统一，这可能导致 bot 在一个 RSS 源被首次订阅后发送已经存在的条目 (文章)。
官方 bot 实例 | 加入频道 | 加入群组 | GitHub 仓库 | 捐赠支持
#Releasev2.4.0: Significant performance improvement, native blockquote and syntax highlighting
BREAKING CHANGES
● Drop Python 3.7 & 3.8 support: The minimum Python version requirement is now 3.9.
Highlights
Performance enhancements
● Reuse SSL context: Reuse SSL context as aiohttp does. This improves performance (reduce load average by ~40%) and reduces memory usage.
● Lazy CookieJar: Lazy creating CookieJar until there is really a Cookie. This improves performance (reduce load average by ~15%) and reduces memory usage.
Additions
● Native blockquote: <blockquote> is now rendered as a native Telegram blockquote rather than a text block wrapped with horizontal rules.
● Syntax highlighting: <pre> is now rendered as a native Telegram code block with syntax highlighting, as long as the language is specified in the class attribute.
Enhancements
● Custom-title-aware OPML: When importing and exporting OPML, the bot will try to distinguish if a feed is of a custom title, and preserve it if so.
● /lang and /test as "remote" commands: /lang and /test are now recognized as "remote" commands, which means you can use them in the private chat to make the operation actually apply to the channel/group you've specified in the command. Note: /test is only available to the bot manager.
● /user_info UX enhancement: /user_info now has a better UX. Note: /user_info is only available to the bot manager.
● Minor enhancements: The Docker image is now based on Debian bookworm.
Bug fixes
● Unexpected feed migration: Fix a bug causing the bot to migrate feeds to a new URL unexpectedly. More specifically, the bot will now only migrate a feed if a redirection is considered permanent (HTTP status code 301 or 308).
● WEBP sent with wrong color space: Fix a bug causing WEBP images sent with a wrong color space.
● Incorrect OPML format: Fix incorrect OPML format making some RSS readers unable to import the OPML file exported by the bot.
● Mistaken watchdog feed timing: Fix a bug causing the watchdog to be feed at the wrong time.
● Uncaught errors: Fix some uncaught errors causing messages failed to be sent.
Bot | Channel | Group | GitHub repo | Patreon
#Releasev2.4.0: 显著提高性能、原生块状引用和语法高亮
重大变更
● 取消对 Python 3.7 和 3.8 的支持：最低的 Python 版本要求现在是 3.9。
亮点
性能增强
● SSL 上下文重用：像 aiohttp 那样重用 SSL 上下文。这将提高性能（将平均负载降低约 40%）并减少内存使用量。
● 懒惰 CookieJar：懒惰创建 CookieJar，直到真正有 Cookie。这将提高性能（将平均负载降低约 15%）并减少内存使用量。
新增功能
● 原生块状引用：<blockquote> 现在被渲染为原生的 Telegram 块状引用，取代用横线包裹的文本块。
● 语法高亮显示：只要在 class 属性中指定了语言，<pre> 现在会呈现为带有语法高亮的 Telegram 原生代码块。
增强
● 可感知自定义标题的 OPML：在导入和导出 OPML 时，bot 会尝试判断订阅源是否具有自定义标题，如果是，则会保留它。
● 将 /lang 和 /test 作为“远程”命令：/lang 和 /test 现在被认定为“远程”命令，这意味着您可以在私聊中使用它们，但使操作实际应用于您在命令中指定的频道/群组。注意：/test 仅适用于 bot 管理员。
● /user_info UX 增强： /user_info 现在有了更好的 UX。注意：/user_info 仅对 bot 管理员有效。
● 次要的增强： Docker 映像现在基于 Debian bookworm。
Bug 修复
● 意外迁移订阅源：修复一个导致 bot 意外将订阅源迁移到新 URL 的错误。更具体地说，bot 现在只会在重定向被视为永久性（HTTP 状态码为 301 或 308）的情况下迁移订阅源。
● 以错误的色彩空间发送 WEBP：修复导致 WEBP 图像以错误色彩空间发送的错误。
● 不正确的 OPML 格式：修正不正确的 OPML 格式，这导致某些 RSS 阅读器无法导入 bot 导出的 OPML 文件。
● 错误的看门狗饲喂时序：修复导致看门狗在不正确的时间被饲喂的错误。
● 未捕获的错误：修复一些导致消息发送失败的未捕获错误。
官方 bot 实例 | 加入频道 | 加入群组 | GitHub 仓库 | 捐赠支持
#Release v2.3.0: Improved performance, subscription quantity limit, and more
This is a long-awaited release. Nice to meet you again in the changelog! This is the last release that supports Python 3.7, and there will not be any patch version for the v2.3.x series. Any fixes will only be applied to the next release, which will bump the minimum Python version requirement to 3.9.
See https://github.com/Rongronggg9/RSS-to-Telegram-Bot/releases/tag/v2.3.0 for more details.
The dev branch has made some progress since v2.3.0 too. Including the support of quote and syntax highlighting (require a recent Telegram client to view, otherwise you will see "unsupported message"). More performance tuning is done, too, making the load average of the public demo @RSStT_Bot 40% lower than before. I will make a new release in a few days or weeks.
However, since there are more than 28,000 subscriptions on the public demo, though its responsiveness was improved, please always give the it more patience. I've not received enough donation yet to upgrade the server hosting the public demo. Please deploy your own bot if you desire a better experience.
Bot | Channel | Group | GitHub repo | Patreon
#Release v2.3.0: 改进的性能、订阅数量限制等
这是一个期待已久的版本。很高兴在变更日志中再次相遇！这是支持 Python 3.7 的最后一个版本，v2.3.x 系列不会有任何补丁版本。任何修复都将只应用于下一个版本，且下一个版本将使 Python 的最低版本要求提高到 3.9。
参阅 https://github.com/Rongronggg9/RSS-to-Telegram-Bot/releases/tag/v2.3.0 以了解更多详细信息。
dev 分支自 v2.3.0 以来也取得了一些进展。包括对引用和语法高亮的支持（需要较新的 Telegram 客户端才能查看，否则将会看到“不支持的消息”）。还进行了更多的性能调优，使公共实例 @RSStT_Bot 的平均负载比以前降低了 40%。我将在几天或几周后发布一个新版本。
然而，由于公共实例有 28000 多个订阅，尽管它的响应能力有所提高，但请始终给它更多的耐心。我还没有收到足够的捐款来升级托管着公共实例的服务器。如果您希望获得更好的体验，请部署您自己的机器人。
官方 bot 实例 | 加入频道 | 加入群组 | GitHub 仓库 | 捐赠支持
#ReleasePublished to PyPI, HTML table converter, and more (v2.2.1)
Additions
Highlights
● Published to PyPI: RSStT is now available on PyPI. You may install it with pip install rsstt. For more details, refer to the Deployment Guide.
● HTML table converter: An HTML table converter has been implemented to convert HTML tables to images. It requires the environment variable TABLE_TO_IMAGE to be set to 1, and CJK fonts to be installed. Please do note that the converter is not perfect, cannot handle rich-text formatting, may not work for all HTML tables, and can potentially lead to a higher performance cost and longer processing time.
Other additions
● New l10n: The Indonesian (id, Bahasa Indonesia) translation has been added.
● Add .env.sample: A sample .env file has been added.
Enhancements
● Natural sorting: Send posts from the oldest to the newest.
● Timed GC: Perform a GC (garbage collection) every 10 minutes to clean up the memory.
● Update l10n: The Turkish (tr, Türkçe) translation has been updated.
● Security: Execute git outside of the shell.
● Minor enhancements
Bug fixes
● Misfired monitor job: Increased the misfire_grace_time to 10s to avoid monitor jobs being misfired because of high load.
● Deps bump: Fixed an upstream bug preventing users from resetting all subscriptions to the user's default settings on a PostgreSQL-based instance.
● Minor bug fixes
Bot | Channel | Group | GitHub repo | Patreon
#ReleaseChannel remote management, more formatting options, and more (v2.2.0)
Additions
Highlights
● Channel/group remote management: Now you can manage the subscription of your channel/group in the private chat with the bot. Most commands are supported. Just send commands like /sub @username https://exmaple.com or /sub -10010000000000 https://exmaple.com. (@username is the channel/group's username, @ is required; -10010000000000 is the channel/group's ID, it must start with -100)
● More custom formatting options:
● Media: You can make Telegram messages come with no media (just text) if you want (by default, they always come with media if any media is attached to the post). Also, you can make Telegram messages come with only media and metadata (no content) if you want, only when any media is attached to the post, otherwise, they will still come with the content.
● Link Preview: Now you can force disable link preview for Telegram messages.
● Source: More sourcing formats available. Read the detailed description in the Formatting Settings Guidebook.
● Deployment to Heroku: The bot can now be deployed to Heroku. Read the detailed description in the Deployment Guide.
● User permission management: The bot manager can now manage the permissions of the bot users by using the /user_info command. In this way, the bot manager can set who (user/channel/group) can use the bot, even if the multi-user mode is disabled.
Other additions
● Single-column table support: Formerly, all HTML tables were dropped from the output. Now those tables with only one column are rendered as multi-line text. Note that multi-column tables will still be dropped from the output.
● Audio fallback for lizhi.fm: Automatically fallback to the less-quality version of the audio if the higher-quality version exceeds the file size limit. Only for lizhi.fm.
Enhancements
● Prettified Telegraph post: The format of Telegraph posts is prettified. In addition, all images and videos are using the media relay server to avoid anti-hotlinking.
● Non-HTTP hyperlinks: Non-HTTP hyperlinks are not supported by Telegram. The bot will automatically convert them to bare URLs.
● Enclosure cleaning: If an enclosure with a non-HTTP URL is already included in a link in the post, it will be removed.
● Lazy media validator: The media validator is now lazy. It will only run if a post will be probably sent as Telegram messages. This will reduce CPU usage and network traffic.
● Enhanced image dimension extraction: Image dimension extraction is now faster and more flexible. If failed, the bot will try to extract the dimension using images.weserv.nl.
● L10n update: Turkish (Türkçe) l10n file updated. (English, Simplified Chinese / 简体中文, Traditional Chinese / 正體中文, Cantonese / 廣東話 are always up-to-date.)
● Improved Docker build caching: If the dependencies are not changed, no need to fetch the whole Docker image again. Just use the cached dependencies and fetch the latest source code.
● Extract git info from Railway.app env variables: Deployment on Railway.app can now recognize the git info.
● Minor enhancements
Bug fixes
● Python 3.7 compatibility: The previous version of the bot broke the compatibility with Python 3.7. Now it has been fixed. Please note that only x86 and amd64 architectures are supported. For arm64, the minimum Python version requirement is 3.8.
● EntitiesTooLongError: Posts with tons of text hyperlinks could cause Telegram API to throw this error. Now the bot will try to fix this error by more aggressive post splitting.
● <div>: The bot will now ensure that each <div> tag takes up a whole line.
There is too much in this release, read more on GitHub...
[Did you know? The release note above is fetched and generated by RSStT.]
Bot | Channel | Group | GitHub repo | Patreon