The Threadiverse is growing again, this time offering an effort to build a new Lemmy replacement from scratch, with API compatibility.

Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy’s Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps of choice.

  • Blaze@discuss.onlineEnglish
    5·
    10 months ago

    whether it would make much more sense to stick with the same DB unless there’s a good reason for divergence.

    SL Dev said they reengineered the database schema and didn’t want to use the Lemmy one. Based on the summer performance issues, I guess it makes sense.

    However unlikely that is … trying not to fragment the fediverse too much would be awesome and its pleasant to see some dedication here to that end.

    At the end of the day, it’s still Activitypub. The compatibility between Lemmy and Kbin works pretty well, most of the issues we had were federation related, and those existed within Lemmy itself.

    • maegul (he/they)@lemmy.mlEnglish
      31·
      10 months ago

      Well there’s still the question of using MySQL (?) rather than postgresql, where all manner of expertise about the DB can be useful to share. Not sure what kbin uses, but pgsql is pretty common around the fediverse.

      And yea, it is all ActivityPub. I’m just not as faithful in that as others tend to be. It seems to be a fuzzy system that allows idiosyncrasies to creep in. Mastodon and Lemmy don’t get along too well and so sometimes AP just isn’t enough (I’ve just been trying to help someone whose masto instance seems not able to post to lemmy). At this moment, getting along is valuable for the platforms, for the fediverse and for us users.