村上さん:nullcatchan_cry: (@AureoleArk)
misskey.io
そもそもActivityPubという仕組みがMisskeyみたいに爆速で流れるものに向いてなさ過ぎる これ元々ブログとか小規模SNSとかWikiを連合させるための仕組みで ✕ 1秒間に何万リクエスト飛び交うTL地獄をどうさばくか ○ いろんな小さなサービス同士が、お互いの更新を配信しあえればいいよね に割と寄ってるのでかなりコストがかかる

Google Translate:

First of all, the ActivityPub system is not suited to something like Misskey, which flows at lightning speed.

It was originally designed to connect blogs, small-scale SNSs, and wikis.

How can it handle the TL hell where tens of thousands of requests fly in per second?

It’s based on the idea that it would be nice if various small services could send each other updates, so it’s quite costly.

  • Die4Ever@retrolemmy.comOPEnglish
    2·
    1 day ago

    if a client side action (clearing cache) affects the issue, then it’s not related to the ActivityPub protocol

    • LibertyLizard@slrpnk.net
      1·
      1 day ago

      Maybe not. I just don’t think saying threadiverse works fine is completely true. We have lots of issues here and there.