v0.5.2

• Added support for Firefox for Android (via custom collection)
• Settings now also accessible from extension settings page

v0.5.1

• Added support for follow buttons in /explore view on some v3 instances (account-cards)
• Add workaround for raw redirect if url resolve did not succeed
• General optimizations / code changes

v0.5.0

Now supports auto-actions for...

• follow
• boost
• favourite
  on external Mastodon instances v3 and v4 (not sure if v3 works as your home instance).

Configurable in addon popup.

v0.4.5

• Fix some handle domains not resolving when there are multiple results from the instance search API

v0.4.4

You guessed it, another edge case was fixed.

Some instances do not include any data-id at all in reply view. So we now generally prefer grabbing the post URL directly using the "a" element sibling of the buttons, which fixes such instances. This is actually easier than the API method and just as accurate. If this does not work, the API method, method for detailed post view and method for old Mastodon take over to determine the post URL.

v0.4.3

And another edge case fixed.

Apparently, some instance APIs return a different URL format. Also, some instances do not put the toot ID in the data-id attribute of div.status but in the article element instead.

v0.4.2

Okay, there was another edge case where the redirect was not working for a detailed post view if the user handle included subdomains.

Fixed the according regex.

v0.4.1

• Fixed and improved support for older Mastodon instances (I guess v3)

v0.4.0

Now all posts and users should redirect correctly. The extension now mimics the way that mastodon itself is resolving contents

Edge cases should now work too.

v0.3.1

• Fix two bugs with post interactions

There still is a situation where a user/post cannot be resolved:

• The user is from another external instance than the external instance the post is viewed in AND
• The user's home instance has disabled external resolving (guessed)