This is also a smaller bug fix release, but we have been working on new features for v1.8.0 for a while now and we are excited to share them with you. A very big thing with v1.7.4 is something that you will not notice unless you are a developer: we got the automated testing working (not again, for the first time). This will help us to identify issues easier and it should prevent regressions in the future. Here is what changed:

For Users

• The search experience was improved a whole lot when searching for URLs from other servers. You will now see the result directly when the page is loaded
• You will now get push notifications for reports
• The magazine description and rules fields no longer have a minimum length
• Our html to markdown parser now supports strikethrough tags. That was mainly a problem with mastodon, but also other software that does not send out the source markdown.

For App Developers

• the local subsciber count is now exposed in the API

For Admins

• The nginx and postgresql docs were updated
• Most CLI commands are documented now
• When a deliver to another server fails with a 4xx response code (other than 429) we will not do a retry anymore
• Limit the federation of the random magazine even further so remote instances cannot find it anymore
• Add a check for banned instances in more places so no requests will be made to the banned instances
• If we receive an activity from an instance we consider to be dead it will be “revived”
• removed the default url that was attached to all threads (there is also a command to remove it from existing entries: mbin:update:local-domain). It is mainly a performance consideration as the domain the url belongs to has to be updated for each created entry.
• A newly created remote magazine could throw exceptions in the frontend rendering for admins, that is now fixed
• Most logger calls now have their origin as a prefix for easier debugging
• Added a command to create a magazine