v0.9.0

General:

• Renamed to FediAct to better describe the extension's use and prevent a naming issue with an existing Fedi account

Features:

• Now showing a hint for toots that could not be resolved

Under the hood:

• Completely changed the way the extension detects toots dynamically. It is now a) more reliable b) more efficient and easier to maintain and c) at the same time prevents that more API calls are made than needed when an already processed toot is reinserted into the DOM (now cached data will be used until the page context changes)
• Many small bug fixes

v0.8.4.1

Fixed a bug where extracting a toot author would not work

v0.8.4

• Simplified some functions
• Improved performance
• Removed unrequired code

v0.8.3.3

fix dblclick triggering if another button is clicked

v0.8.3.2

• Added reply support for v3 instances

v0.8.3.1

• Added support for replying
• Fixed support for replying from initial release 0.8.3
• Fixed a bug where a variable was not reset for every resolve

v0.8.2

• Added support for bookmarking / unbookmarking

v0.8.1

• Quality of life: Instantly update token in background script after updating settings
• Remove unused code
• Use minified version of .js and .css files in release

v0.8.0

Biggest update so far!
Basically, everything is new.

• Single click to execute action, double click to redirect
• Toot status is now shown (favourited, reblogged)
• No longer uses periodic fetching of following list but API call to check when needed
• Use background script to allow using Mastodon 302 redirects for toot resolving
• Use runtime messages to communicate between background / content script
• Use a custom implementation to detect inserted nodes (better reliability than MutationObserver)
• General optimizations/improvements
• Use delay to prevent API error 429
• Use accounts API to resolve handles
• Code restructuring

v0.6.0

• The extension can now show if you are already following a user when viewing the profile on an external instance
• You can therefore also unfollow on external instances
• Extension now utilized background script to gain API token
• It therefore no longer needs the redirect page - API calls to the home instance are now made while still on the ext. instance, then you are directly redirected to the resolved content on your home instance
• General performance and structural optimizations
• Added new settings

Please report any bugs. Webstore releases will take 2-3 days.

Note that it can take 1 or 2 minutes after the update to gain the API token and sync your following list. Your home instance has to be set first!