Hello world!

We would like to start by saying thank you ❤, no really 🙏 THANK YOU to ALL the moderators out there!

Without you folks, we would have no one to help keep our community safe and help build the communities both here on Lemmy.World and on other fine instances. To this end, we want to make sure your voices are heard 📣 loud and clear📣.

So, in the spirit of transparency, we would like everyone to know that we are looking to help out the folks working on Sublinks. Over the last several months we have grown to be more than just Lemmy.World. We’ve added platforms such as Pixelfed and Sharkey to help offer our users more diverse options for expressing themselves online. We still are very committed to Mastodon as well.

We DO NOT plan on moving away from Lemmy as a software platform at this time. Any changes in our core services would need to be discussed extensively internally AND externally with our community members. We firmly believe in the growth of the Fediverse and without the users, there would only be software, and that’s no fun!

Sooo…

The Sublinks team has written up a little survey, which we feel is both thorough and inclusive. It covers a wide range of topics, such as user privacy, and community engagement, along with trying to gauge things that are difficult when moderating.

Also please be aware the information collected by this survey is completely anonymous. As many of us in the social sciences background know, if you want the REAL feelings of individuals, they need to feel safe to express themselves.

👉Moderation Survey HERE👈

Please feel free to comment in this thread, we will do our best to respond to any genuine questions.

We look forward to hearing from each and every one of you!

=Sincerely,
Fedihosting Foundation

PS … also if this sounds like a corporate press release to you folks, we still punk 🤘😜🤘

  • nutomic@lemmy.ml
    link
    fedilink
    arrow-up
    41
    ·
    8 months ago

    This is not true, Lemmy can definitely have plugins and there is an extensive discussion about this topic. The conclusion is that plugins should be implemented in webassembly, so that they can be written in many different languages. See extism for details. Whats needed is someone with a clear use case who can implement a proof of concept, as it wouldnt make sense to add plugin hooks that no one uses.

    Also mod tools can be implemented as api clients such as LemmyAutomod.

    • Rooki@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      8 months ago

      Ok thanks never knew about such discussion! But it is missing like hooks, events, triggers. Otherwise a plugin is almost useless and just hooking directly to the db would be more effective.

      External bots, have one big downsode that kills it for most “plugin” use case, it is pull, many use cases want a push method over a trigger, event or similar. And to fetch the api every second is inefficient if you say so. Direct db access is not available for everyone.

      • nutomic@lemmy.ml
        link
        fedilink
        arrow-up
        18
        ·
        8 months ago

        Sure the plugin hooks still need to be implemented. It wouldnt make much sense to do that now before any actual use case exists, then the hooks would remain unused or wouldnt even work properly. Thats why it should be implemented together with a proof of concept plugin.

        • Rooki@lemmy.world
          link
          fedilink
          arrow-up
          9
          ·
          8 months ago

          On sublinks we already do stuff apready with those hooks. So that is already implemented

            • Rooki@lemmy.world
              link
              fedilink
              arrow-up
              9
              ·
              8 months ago

              In the services, the “events” all of those can be hooked into. In our case the only thing that is missing is a way to load a plugin into the software is missing. But it is comming up and if someone really needs that urgently a custom build, it is really easy to integrate a logic into it and build it into a custom build, by simply putting it into a custom file and then pulling upstream for updates.