Just a few bugfixes, honest! 😅

- Migrating frontend preferences from pre-2025.4.2 should be more reliable now.
- Parsing of incoming activities should be faster and use less memory.
- Many database queries are now faster.
- Blocking / silencing many instances will no longer slow down yours.
- Caches should be more correct.
- The "slow query" warning in the server logs can now be configured.
- S3 errors during media uploads are now correctly reported to the frontend.
- More consistent handling of note visibility and silenced instances / users.
- The MFM parser now accepts markdown image links like ![text](url), and those images are fetched like attachments (they're not yet rendered inline, though).
- Many privacy / security fixes.
- Improved notification grouping.
- Suspending a user no longer severs their follows, so they'll be restored when the user is un-suspended.
- On a note's detailed view, the "reactions" tab shows all the details of the first reaction group by default.
- API endpoints emit a X-Robots-Tag: noindex header to deter indexing.
- Videos will be optimized for streaming (not re-encoded, the metadata will just be modified slightly).
- The admin view of a user's profile now shows their sign-up reason.
- A few admin and moderation pages have been redesigned and should be more usable, especially on mobile.
- Server logging has been improved, it should now provide more details with less noise.
- Improved interoperability of quotes with Mastodon and other software that implements fep-e232 and/or fep-044f.
- Show attributions (fediverse:creator) in link previews, and allow users to set their "attribution domains".
- If enabled in the default policy, non-logged-in users can use translation features.
- Some frontend pages now retry API calls when they hit a rate limit.
- DeepLX works again.
- Fixed receiving poll votes.
- Users can again set their custom search engine for MFM's [search] feature.
- "Show muted words" works the right way around.
- Reworked the "trending polls" page.

Recommendations to admins:
- If your users had a broken migration, they can try re-importing via Settings → other → 🗘 Migrate old client settings, but we suggest backing up their current preferences first.
- The default policy now disables translation, you may want to create a conditional role matching all local users to re-enable it for them.
- We've added many new indexes to the database, we recommend running a vacuum (analyse, verbose) after the migrations have completed.
- If you do not use Docker, to avoid potential crashes when rendering some SVG images, you should make sure that your system has librsvg and some fonts (on Debian-style systems, that's librsvg2-2 and fonts-noto).