Releases: Yuuzi261/Tweetcord
0.5.2
📌Strongly recommended to download or update to this version, as previous versions relied on tweety-ns 1.0.9.2
, which has been confirmed to have some issues!
📌If you want to upgrade from 0.5.1 to 0.5.2, please pull the code first and upgrade according to the upgrade guide.
feat & fix:
- In response to the
tweety-ns
version update, the relevant operation is changed to a coroutine. (d8b3344)
Important
If you are performing a fresh environment setup, upgrade, or deploying containers (e.g., Docker), the latest version of httpx
might be installed, which can cause compatibility issues with tweety-ns
. To avoid this, please temporarily add httpx[http2]~=0.27.0
to your requirements.txt or manually downgrade the package (#38).
Warning
We have identified an issue with version 2.0.4
of tweety-ns
that may cause certain accounts to be unfindable when adding a notifier. To avoid this issue, please update tweety-ns
to version 2.0.6
. However, it is important to note that both 2.0.5
and 2.0.6
versions may encounter issues related to the python-magic
package, particularly on Windows systems and some Linux hosts or containers lacking the libmagic
tool. This can result in failures when attempting to invoke libmagic
.
To address this, the following workarounds are available:
- Use version
2.0.4
and manually modify thetweety-ns
source code. (#37) - Use version
2.0.6
and manually installmagic-python-bin
(for Windows hosts). (mahrtayyab/tweety#229) - Use version
2.0.6
and manually installlibmagic
(for Unix-like hosts).
Note
This version has only undergone basic testing. If you encounter any issues during use, please contact me through an issue.
0.5.1
📌0.5.1 is a patched version of 0.5, it resolves two issues from version 0.5: the default value error for auto-completion when the client is not specified, and the problem with reactivating a monitored account in a disabled state using the same client (#33). If you have already upgraded to version 0.5, you can update to 0.5.1 by directly pulling the new code.
📌 If you want to upgrade from 0.4.1 to 0.5.1, please pull the code first and upgrade according to the upgrade guide.
feat:
- Settings now allow filtering by media type, enabling the option to forward or not forward pictures and videos. (#31) ← EXCELLENT😇
- Supports built-in multiple embedded pictures that can be replaced with fx combined pictures. (3209b94) ← FRIENDLY TO IOS SYSTEM🤗
- Multi client support, add multiple tokens and choose which account follow which user. (#31) ← MORE POWERFUL CUSTOMIZATION👏
- Autocomplete for some slash commands. (#31) ← CONVENIENT👍
- Customize bot activity type and message. (0051469, #31)
- Split listing to prevent cutoff. (#31)
- Optimized the update process. (f097793)
- Startup checks for environment variables, configs and database.
refactor:
- Convert all SQL operations to asynchronous. (dce6f8c) ← AVOID BLOCKING✌️
- Optimize the overall code
0.4.1
feat:
0.4-hotfix
📌 0.4-hotfix is a fix for the issue where the /sync
command is open to everyone by default in version 0.4. If you have already upgraded to version 0.4, you can update to 0.4-hotfix by directly pulling the new code
📌 If you want to upgrade from 0.3.5 to 0.4, please pull the code first and upgrade according to the upgrade guide
feat:
- Set up custom notification messages! Customize for different servers ← AMAZING👍👍👍
- When all notifications for an account are removed, the task will also be turned off ← SUPER SMART🤯
- Decide to disable notifications or unfollow a Twitter account after remove all notifications for an user ← CONVENIENT😎
- New permission checking method, each server can be overridden by itself, default is administrator
- After changing your twitter account, you can use
/sync
command to enable notifications in the new account
0.3.5
feat:
- new slash command
/list users
← CONVENIENT & INTUITIVE👍 - bot can work well if user tweet multiple tweets in 1 period ← VERY RELIABLE😎
fix:
0.3.4
feat:
- add remove notifier slash command ← VERY CONVENIENT👏👏👏
- download log file command for owner