We are developers and designers making user-friendly apps. We take pride in our craft and work hard to make sure our applications are a great experience for people.

Unfortunately, there are increasing efforts on the current market to disallow or discourage customization. This worsens user experience for a lot of software.

Kirigami colour sets allow developers to easily make their UI work with any colour schemes.

Icon Themes allow users to have a unified view across different applications.

Application styles allows users to decide how a button is represented, how wide a scroll bar should be, etc.

All these not only give users the freedom to decide how the applications should behave, but also make room for accessibility considerations like larger buttons, more visible focus indication, and more contrastive colours and shades.

This is why we believe application developers should be aware of the possibility to customize its appearance.

If you are an application developer, we kindly ask that you do not hard-code any colour or size, but rather follow the system styles.

On a platform level, we should implement a colour set editor that informs users about what colours might be put where, and advises about how contrastive the foreground and the background are in different places.

If you are a user or distribution maintainer that ships our apps, and you are having issues with our apps on your customized colour set or application style, please do tell us, and we can figure out the cause of the problem.

Signed, tusooa, maintainer of kazv.

This document is inspired by https://stopthemingmy.app/ .

As you may have noticed, some current developers of Pleroma went for a new fork on codeburg.
估计大家可能听说过了，有的现任 Pleroma 开发者在 codeburg 高头搞了个新的复刻。

At this time, I am not sure which way kazv.moe would go for. But it is certain that, until at least the next major release of either one:
现在我还不晓得 kazv.moe 会走到哪块去。但是呢，至少在任意一个释出下个大版本之前：

(0) No database migrations would be performed on the released branch of Lily Islands.
(0) 百合岛高头的 released 分支不会发生数据库迁移。

(1) I will no longer be picking up any non-security-fix changes from the develop branch of either repo into released or servant.
(1) 我不会再从这两个仓库的 develop 分支拿来不是安全修复的更改放到 released 或者 servant 高头。

In addition, I will always support docker (image at reg.lily.kazv.moe/infra/pleroma:released) no matter whether it is still supported by the two upstreams.
另外，我会一直支持docker（镜像在 reg.lily.kazv.moe/infra/pleroma:released），不管两个上游还支持不支持。

It seems that they do not intend to fork Pleroma-FE at this time.
现在伊们似乎不打算复刻 Pleroma-FE。

cc @suica