tldr: chapo.chat isn't ready yet.

Don't worry, you'll get to be called libs by the users from lemmygrad.ml Soon™.

[chapo.chat is] running a heavily modified version of lemmy forked months ago, for not just the front end, but the back end as well. Once they’re up to date with the most recent lemmy versions that have federation working, then we can try federation, on the back end at least. Their back end devs are great, but their front end devs contribute nothing upstream, and will have to re-create all the federation-related parts of the lemmy-ui code for their own fork.

Source

EDIT: See @Beatnik's comment

    • eiknat [comrade/them]
      1·
      4 years ago

      also i wanna be clear. just because we're rewriting in node does not mean we stop contributing to the rust codebase. i plan to continue contributing :)

        • eiknat [comrade/them]
          ·
          4 years ago

          yep. we're almost assuredly going to have to maintain our own fork to keep up with different demands. the simplest thing to do is maintain it in a language that is going to have a much larger pool of developers.

          i am also of the opinion that supporting the spec in more than one language makes the lemmy ecosystem more approachable in general.

            • eiknat [comrade/them]
              ·
              4 years ago

              not as far along as i'd like. but i plan to have all the routes stubbed with tests this week.

              the websocket implementation is complete. just the handlers as each endpoint is written are left.

    • fx8690gii [he/him, he/him]
      2·
      4 years ago

      We’re in the middle of completely rewriting the backend, but the v1 API’s will be completely cross-compatible, so Lemmy apps will still work and federation will still be possible.

      Good, good.