Notices by Sovereign (sovereign@tsundere.love)

@ceo_of_monoeye_dating @weaf This was the plan the entire time. Now comes the rest of Europe. The US wants to make sure it has no competition regarding the treatment of its slaves.

@mischievoustomato Did a little AI assisted research. You might potentially find this interesting:

Pleroma theme editor has this message banner at the top. Can you research the differences between V2 and V3? What are the pros and cons (if any exist)? What is the motivation to transition to V3?

You’re seeing that banner because Themes V2 is officially on its way out—and Pleroma is being migrated to a new Themes V3 engine. Let me walk you through what that means, what changed, and why the transition matters.

With the Pleroma 2.0.0 release (March 2020), a major overhaul arrived under the hood: the theme engine was upgraded to version 3—internally called V2.1—which represented a significant architectural refactor and paved the way to the formal V3 engine.([GitLab][1], [pleroma.social][2])

• From spaghetti code to structured generation Instead of generating bits and pieces of CSS or theme assets in a scatter‑shot fashion, everything is now fed into a single generateTheme function—clearer, better organized, and maintainable. Theme slot inheritance is declared in a centralized file rather than spread across logic layers.([NixOS][3], [pleroma.social][2])

• Expanded theming capabilities The update also introduced:

  • Tons of new color slots, including states like hover, pressed, toggled, etc.
  • Experimental support for syntax like --variable[,mod], allowing automatic brightness adjustment (the mod parameter) to generate lighter or darker variants based on background colors.([pleroma.social][2])

1. More expressive theming options Richer color slot support and dynamic variable modifications enable deeper customization—think "hover color +10%" without manual tweaking.

2. Better code organization and maintainability A single theme generation pipeline makes it easier for developers to reason about, extend, and debug the system.

3. Improved consistency and inheriting behavior Centralized declaration of slot inheritance reduces duplication and risk of inconsistent behavior across themes.

• Learning curve for theme authors If you're used to V2's way of doing things—editing bits of CSS here and there—you may need to learn how the centralized engine handles variables, inheritance, and theming logic.

• Potential compatibility issues with older custom themes Since the way themes are generated changed fundamentally, themes built for V2 may require modifications or conversion to work properly under V3. This is likely why the V2 editor is being deprecated and labeled as “phased‑out”—to steer authors toward compatible, future‑proof tooling.

The migration is driven by a few clear motivations:

• Maintainability & scalability: Centralized, structured theming logic is easier to update and enhance than ad-hoc scattered code.
• Feature richness: Supporting advanced color manipulation and state-aware styling complexes provides a more powerful toolkit for designers and themers.
• Consistency: A unified pipeline ensures themes behave correctly and consistently across instances and updates.
• Future expansion: A solid foundation (V3) sets the stage for future theming improvements, perhaps including real variable-based theming, theme sharing/exporting, and better front-end styling controls.