Documentation
Source
API
Blog
News
Donation

PleromaFE Patch Release: 2.11.1

PleromaFE 2.11.1 is a minor release of PleromaFE (Frontend)

Highlights

Small but important changes

Settings & User Highlight synchronization

All (almost all) settings are now synchronized between different browser sessions. Same happens with user highlight. Synchronization uses our CRDT implementation, meaning that changes made on one session (i.e. on phone) won’t conflict with changes made on another (i.e. on desktop). Changes are timestamped and most recent change takes precedence. This is the same technology as one used for pinned navigation items and pinned status actions.

Please note that there is a migration process - when session is opened with “unmigrated” settings, it will override all synchronized settings with older, unsynchronized ones and mark them as “migrated”. Only settings that were ever changed would be affected, not the entire thing. This means that there will be some instability upon initial use until all settings are migrated.

Not every setting should be synchronized, however, so right now there’s a list of exceptions that don’t get synchronized. In future we might implement proper user-configurable “local overrides” instead of hard-coded list, underneath it already supports it - it’s just a matter of making a non-confusing UI.

Admin User Management

Admin Dashboard just got a small upgrade, there’s now “Users” tab, showing list of all users (default filtering to local accounts only but you can see all known users if need be), their status (i.e. suggested, confirmed, etc), registration reason and email. User moderation menu got a little upgrade, too, allowing more actions on user profile as well as bulk actions on admin tab. Admins are also now able to quickly change post’s scope and sensitivity. Separate page was also added for showing ALL user’s posts, i.e. a “godmode” view, with toggle to see DMs.

Another feature of AdminFE ported over to Admin Dashboard

MFM (Markup Language for Misskey)

Our HTML parser/renderer now supports MFM attributes, correctly rendering associated CSS effects. This requires backend support (Akkoma should work but untested, Pleroma develop commit 86dd9663fc onwards) to actually parse the markdown and turn it into a HTML with data-mfm attributes.

Extra work has been put to make sure complex MFM animations and “MFM Art” renders correctly, as a result MFM imposes extra changes to rendered content:

Despite this, MFM might still not render exactly as on Misskey, with some issues that might never get fixed:

As part of original implementation, there’s a setting to make MFM scale with user emoji size setting, but since MFM artists tend to pad post with empty newlines (without :blank: emojis) this causes MFM animations to be cut-off.

All MFM animations are play-on-hover by default, just like GIFs (uses separate setting).

Not really related but code blocks now have prettier styling and don’t have word-wrapping.

Load Optimization & Error Handling

A lot of work was done behind the scenes to improve code quality and to optimize loading times. As a result two user-facing changes have been made:

Sorta related; we’ve refactored ALL of our API code, making it much more consistent than before and improving capacity for proper error-handling. We’ve did extensive testing and test-driving of it but some things might have fallen through cracks, as it was the case with 2.11.1 patch release.

Changelog

Added

Changed

Fixed

Changelog for 2.11.1 patch release

2.11.1 release was made while I was writing this announcement, fixing a bug in 2.11.0

Fixed

— hj