Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 07-Apr-2025 06:37:19 JST Haelwenn /элвэн/ :triskell:

   in reply to

   @phnt Urgh great, meanwhile vite means binary blobs and so a failure here: https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1364

   Could you send a patch? Either via attachment here, or emailed to contact@hacktivis.me, or PR on https://github.com/gentoo/guru with @lanodan mention so I don't miss it.

2. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Wednesday, 19-Mar-2025 00:14:00 JST silverpill

   in reply to

   @tadano I changed the way emoji reactions work in version v3.17.0. Now platforms that don't support emoji reactions (such as Mastodon) see them as likes, but, as I learned later, that broke interoperability with Pleroma.

   @lain has been very kind and started working on a solution - https://git.pleroma.social/pleroma/pleroma/-/issues/3364

   Meanwhile, I could add a configuration option that restores previous behavior. What do you think?

3. Embed this notice
   のえる (noellabo@fedibird.com)'s status on Tuesday, 26-Nov-2024 16:34:10 JST のえる

   現行のPleroma / Akkomaに、プロフィール補足情報（Misskeyだと追加情報）が多すぎるとアカウント情報の取得に失敗し、再取得を繰り返してしまうバグが存在します。

   これにより、CPUが使い尽くされたり、データベースが肥大したり、相手サーバへ過大な負荷をかけてしまいます。

   Pleroma / Akkoma全体でこれが発生するため、実質的にDDoSを仕掛けるような挙動となります。

   デフォルトが20なので、これを設定（Instance の Max remote account fields）で大きく引き上げる方法でまず対応し、

   指定数をオーバーしたら切り捨てて対応するパッチをあてる対応が必要です。
   https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4220

   Pleroma / Akkomaの新バージョンがリリースされたら速やかにアップデートしましょう。

   この不具合は、プロフィール補足情報の件数が多いActivityPub実装すべてで発生します。

   Mastodonの標準は4件、Misskeyは16件、Fedibirdは8件ですが、独自に数を増やしているサーバであれば該当する可能性があります。

   また、Misskey.ioのバナー機能はプロフィール補足情報で連合するので、こちらでも発生します。

4. Embed this notice
    (mint@ryona.agency)'s status on Friday, 23-Aug-2024 09:05:25 JST 

   in reply to
   @feld Something like that. Wonder if there's any further demand for preemptive activity filtering before ever resolving the pubkeys (resulting in actor getting fetched), if so it should be expanded into proper facility.
   https://git.pleroma.social/mint/pleroma/-/commit/1fbe696c011fea497828fb16f0fd73bc1cfeff6e
   Haven't made any tests yet, partially because I'm not sure how to handle them, partially because rebar throws some cryptic error on my workstation when compiling syslogger.
5. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Friday, 15-Dec-2023 07:54:42 JST NEETzsche

   in reply to

   I know I just said that I wouldn't work with them, but as a gesture of good will I will submit fixing their federation: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4000

   It lists where I got the information from, who wrote the original commit, and why it's important per ActivityPub standards. They can click merge or they can let their shit stay broken lol

6. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Friday, 01-Dec-2023 01:06:30 JST NEETzsche

   @hj I got rid of the favicon shit from this one: https://git.pleroma.social/pleroma/pleroma-fe/-/merge_requests/1872

   It just creates a link to externalLink when one is available. If you want it to behave in some other way when it comes to externalLinks, just tell me. I’m not going to argue with you at all on this topic and I’m just going to work toward your specification, so just make it clear what you want.