Release v1.7.1 · MbinOrg/mbin
github.com
Welcome to version 1.7.1 of Mbin. A very packed Mbin release once again! This version includes tons of fixes (too many to mention here, look at "What's Changed") and introduces also new features li...

We focused on fixing bugs this release and there were quite a few

For Users:

  • If you try to upload an image that is too large you will now get a proper error message. Additionally the maximum allowed file size is now displayed in the upload form
  • We changed our hashtag matching. What this does is match content (mostly from mastodon) to magazines by the hashtags the content uses. You can define such hashtags in the magazine panel. However previously each magazine had its own named predefined as a hashtag to match content against. We removed this behavior, since it was not intuitive and there was no way to turn it off. This meant a magazine like kbinMeta which had the magazine name meta would have matched every mastodon posts it gets containing the hashtag meta to this magazine
  • Fix a problem with editing content. If a magazine was hosted on an mbin server it would not allow a user to edit it’s own content, because of some faulty conditions. This is now fixed
  • Fix a wrong like/dislike/boost count on peertube videos
  • If you delete your account (but do not select the “instant” option) you can just login to your account to restore it

For Admins:

  • There was an error when saving the admin settings, that should be fixed by now (if you’re not jumping from release to release then you might have a MAX_IMAGE_BYTES setting of 0 right now (just be aware of it in case of image upload problems)
  • In the user panel you now have a view for banned and suspended accounts
  • there is now a command for setting a users password: mbin:user:password <user> <password>
  • you can now activate/verify accounts in the UI
  • you can now configure the trusted proxies via TRUSTED_PROXIES
  • You should not get any content of the banned instances anymore. Previously you could get the content anyways for example if a user from another instance liked content from a banned instances.
  • Fix messenger deadlocks caused by cache locks. For an explanation have a look at the fixing PR #1066
  • We now log the error message of an invalid register form for debugging

API

  • magazines now have a property isPostingRestrictedToMods
  • Add isAdmin and isGlobalModerator fields to user api response
  • Add field to all content response DTOs: canAuthUserModerate