It's time for a brand new Sharkey release!
-
It's time for a brand new Sharkey release! This marks the first of the 2025.4 series (the .2 is to prevent conflicting tags with upstream for our merge workflows), and with it comes a lot of new features and bugfixes!
- Mfm now handles some punctuation inside bold/italic blocks.
- Users mentioned in DMs they can't see are no longer sent notifications.
- Optional WebSocket compression.
- Hopefully a fix for the bug of your own reactions not being marked on posts.
- Blocks and mutes should now be more effective.
- When a note is muted, the reason is shown.
- Fixed editing of scheduled posts.
- Additional moderation logs.
- Numerous fixes to the Mastodon API.
- Users can now delete their own avatars.
- Users are now warned when editing a poll, as it can lose all votes.
- Libretranslate is now supported in addition to DeepL.
- Showing linked notes as quotes is no longer automatic (you have to click a button), and it works in more cases.
- Admins can change the level of "authorized fetch" via the frontend ("never", "always", and the new "essential" that serves a reduced amount of data to non-signed requests), and users can override this for their own data.
- The notification dot on the favicon should work in more cases, and be more visible.
- The "replies" collection is now exposed on all notes (we still don't fetch remote replies, but we enable other software to do so).
- Improved compatibility with Lemmy and other ActivityPub implementations thatAnnounceactivities other thanNote.
- Numerous translation improvements (Daniel Ares for German, Ahri for Thai and Vietnamese).
- Support for BunnyCDN in addition to S3-like object stores.
- Sensitive/content-warned content is not served to the Discordbot (Discord uses the mastodon api to fetch notes for their previews, and they've decided to ignore CWs in favour of their own||spoiler||markers-- we don't agree with that decision).
- Admins can now inject custom HTML in every page's<head>(e.g. custom CSS).
- Admin set MOTDs can now use HTML.
- Links in profile fields are now verified for remote users.
- Fixed signature verification for paginated AP requests.
- Admins can now remove a role's color.
- Admins can disable the use of the "proxy account" (although this will break some lists!).
- Disabling the local timeline also disables the "featured" timeline on the logged-out front page.
- Drive cleaner now shows all files, even those inside folders.
- Delivery of activities has been re-ordered a bit, this should mitigate the infamous "Yaseen bug".
- URL previews once again follow redirects.
- Config file(s) can now be placed in any directory.
- You can now configure the directory for drive files (when not using S3 or similar).
- Improvements to the admin UI.
- Improved "delete account" process with better reliability.
- New role setting "can trend".
- new role conditions "is from bubble instance", "is from instance X", "has more/fewer than X local/remote followers", "follows more/fewer than X local/remote accounts".
- The config optionallowPrivateNetworkscan now specify ports for each network.
- New "pattern checker" tool to test your word mutes.
- The web frontend passes the user's authorization token in a header instead of the request body-- this should prevent accidentally leaking the token via logs.
- Improved interoperability with Akkoma and Wafrn "invisible mentions"
From Upstream:
- Brand-new job queue dashboard
- All-new settings/preferences system that enables searching of settings!
- Admins can now limit the max file size for users, via roles-- if this is applied to remote users, it applies to caching.
Potential Gotchas:
- If your browser is logged into more than one account, you may need to log in again, due to an upstream change.