Hi, I’m Maxi

Admin at dataterm.digital
Find me on Mastodon: @Sirs0ri

  • 1 Post
  • 5 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle
  • At the moment lemmy and kbin are both pretty early in their develoment cycles - kbin had so many issues that we couldn’t get it to run at all, lemmy runs, but it’s far from being smooth.

    We’ll keep an eye on both and see how the development goes, and we might consider a kbin instance once it’s reached a certain maturity. But, and that’s a big but, we’ve got a community that’s attracted over 200 people in a matter of days, and unless there’s a process to migrate all those users smoothly from one instance to another, it’s pretty unlikely that we’re gonna replace this lemmy instance with a kbin based platform entirely.


  • it kinda does!

    we had some spam from a user from another instance earlier and at first it looked like changes made to comments through an admin’s actions (especially deleting it) wouldn’t federate

    now it looks like these changes federate sometimes, but not consistently. Lemmy’s moderation tools definitely need a bit of work 😅



  • definitely a good place to ask this!

    My linited understandign based on Lemmys docs (https://join-lemmy.org/docs/en/administration/federation_getting_started.html) is that only the community you subscribe to will federate:

    If you search for a community first time, 20 posts are fetched initially. Only if a least one user on your instance subscribes to the remote community, will the community send updates to your instance. Updates include:

    • New posts, comments
    • Votes

    That should explain the missing content as well: Lemmy only fetches a portion of a community at the time of subscribing, and only the content created after the initial federation will be sent to us - you can manually force a refresh by getting the link to a comment on the remote instance, and searching that on our instance - that’ll get all the data about its parents, but that’s admittedly pretty inconvenient. The process is described in more detail in the docs linked above!