v0.9.6.1

Hotfix: There was an issue with the toot caching process, leading to some toots not reflecting the changed state

v0.9.6

• Add missing animation for fav button
• Remove no longer required code
• Update icon

This is the first recommended release.

v0.9.5.3

• Attempt to fix elements not being detected on v3 sometimes
  • There were (/are?) cases, where elements got cached by the browser and were not detected by DOMNodeAppear...
  • ... as well as cases, where a page was visited for the first time
  • Now, in addition to DOMNodeAppear, a $(docuement).find(...).each(...) is used to try and detect these cases
  • To prevent the same element from being processed twice, an additional check was added

Not sure if its done with that. But also, there arent many v3 instances anymore...

v0.9.5.2

Prevent uncatched error if tabs query in background script returns no tabs

v0.9.5.1

• Fixed site views with multiple follow buttons (v3 explore page) - follow button status was not correctly set per element
• Fixed follow buttons not correctly initialized if follow is already requested (but not yet accepted)

v0.9.5

• Hide Mutes feature changes
  • Now blocked users are treated like muted users for this extension
  • Now all their boosted toots, toots and toots with mentions of them are hidden if enabled
  • Now domain blocks are applied as well
  • Moved sync to background script
    • They are now fetched each minute
    • This is to prevent needing multiple requests in the content script if Hide Mutes is enabled (since v3 instances would not work this way)
• Try to reload settings on page URL changes (to keep mutes/blocks in sync with local storage)

v0.9.4

• Fixed a bug where redirection would not work if auto-action is disabled
• New feature: Hide boosts and toots from users you have muted and also toots that mention muted users
  • This feature can fail if a mention/boost is from an external handle that uses a different hostname from the handle domain (rarely the case - won't fix because this would require additional API calls)
  • This is disabled by default because it can lead to decreased performance or rendering issues - I still wanted to include the feature in case some users REALLY want to hide muted users
  • This is only active for MUTED users, not for blocked users

v0.9.3.2

• Moved all home instance actions to one generalized function, less code for same functionality
• Always add fallback resolve URL to resolve array, even if the toot was already externally resolved
• Removed unrequired code
• General improvements

v0.9.3

• Sites now auto-reload when settings are updated or the extension is updated/reloaded
• Better resolve probability due to new logic
• "Unresolved" indicator now correctly displays for all unresolved toots
• Small bug fixes

v0.9.1

Hotfix for follow buttons not processed when first page page browsed was. An old portion of code was accidentally left in prior to the v0.9.0 release