村上さん: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.

  • Pamasich@kbin.earth
    5·
    1 day ago

    I saw a separate post linked in the Reddit thread on this, where it was said.

    https://misskey.io/notes/af5udbqosfca05lo

    Via machine translation:

    I won’t be leaving the federation immediately, but I will be migrating to the low-overhead federation system MisskeyHQ is developing. Servers incompatible with that system may eventually lose connectivity.

    The full transition will likely take several years, so it should be fine until then.

    Source for the full quote of link + translation (Reddit alert)

    Don’t know more information than this. But the wording there suggests to me that what they’re switching to isn’t fundamentally incompatible with the fediverse. They seem to be treating loss of compatibility as an allowed risk, not a guarantee. So they’re probably still using ActivityPub as a foundation for what they’re building.