Releases: MujyKun/Weverse
V1.1.3 Release Notes
V1.1.2
V1.1 Release
- Fixed Videos so that they now post.
- Added automatic followings to asynchronous client (this is optional)
- Added 4 hour checks to check for a new community before following them
Thanks to @mina9999 for helping.
V1.0.7.4 Release
- Added Username and Password Login
- Added the option to add a hook method ( can be passed into the client ) that will be called whenever there are new notifications.
- Added refresh tokens.
- Added automatic reloading of a login or refresh token when a token no longer works.
- Removed Weverse as a self requirement and pushed it to examples.
- Added missing Crypto req.
- Removed outdated package.
- Hook no longer checks has-new and does a manual check on the notifications.
- has-new method is no longer recommended.
V1.0.6 Release
-
Weverse will no longer create old posts/media by default unless specified in the start method.
-
Weverse now has support for announcements.
-
Can directly fetch an announcement from the client using a community id and an announcement id
-
Client will now contain all announcements, BUT will never load up PAST announcements. It will only load present and future ones if being checked in a loop.
-
Magic/Dunder methods added for majority objects. It is now possible to check objects equal to each other, not equal to each other, getting some of their strings and having it return the body of the object, or the length would show the amount of images/video in that object. It may also show the duration if it is a Video object.
-
Docs theme has been updated.
-
Docs now has containers under the main objects with magic/dunder methods.
V1.0.6 (This Release), V1.0.5.1, and V1.0.5 were all released within a 24 hour window. Make sure you are caught up with previous updates.
V1.0.5.1 Release
- Added Type Support for several objects.
V1.0.5 Release
-
The client start method now takes a parameter
create_media
which is set toFalse
by default. When set toTrue
, it will create all past media. -
If a media post contains photos, the media object will now store those photos. This was an important feature that was missing by lack of research. If you are a user that keeps tracks of notifications, it would be advised to rework your media section if you specifically post photos.
V1.0.4 Release
-
client.determine_notification_type can now either take the notification body OR the notification itself.
-
If a weverse account is set to KOREAN, the output comes back as korean on the bot. This is fixed by adding korean triggers if the bot still wants the account to be korean. This was also a fix for determining the notification type accurately. It is possible some triggers may be missing, but majority of the Korean and English ones should have been added.
V1.0.3 Release
This was an update to prevent new posts being lost in the void.
Since it is possible for several posts to happen at the exact same time, there is now a method that will get ONLY THE NEW user notifications AFTER the client has checked for new notifications. The example usages can be found below.
Asynchronous Example
Synchronous Example
The examples have been updated and there has been added type-support.
Notifications are also now comparable with the equal operator by differentiating IDs.
V1.0.2.2 Release
Added Proper Type Support for Posts