Plugins for fediverse platforms.

Where is this up to? Is anyone thinking along these lines?

I’ve seen @db0 espouse such (eg https://lemmy.dbzer0.com/comment/8581651) (sorry for the tag if annoying).

I’ve certainly thought of it myself … because it’s a pretty obvious idea for an ecosystem aiming for richness and sustainability.

Seems a perfect fit for reusable moderation tooling too, rather than each new platforms having that trouble.

This is essentially #bluesky 's idea it seems.

@fediverse
#fediverse

  • imaqtpie@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    It’s definitely a good idea. I’m not sure how high it is in priority when we still need to work on basic federation mechanics, but eventually I think it makes a lot of sense.

    • maegul (he/they)@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 months ago

      Well, the thing about establishing a plugin interface is that it facilitates 3rd party work on the platform by decoupling core development and its build processes from the development of any additional feature which can be done in whatever tech stack or manner the plugin developer wants.

      When it comes to moderation tooling I’m honestly a little confused that there isn’t more work or noise around a developing a sideloaded tool. With the current lemmy APIs for instance, surely one could make a web app, for admins/moderators only, that consumed feeds, exposed the admin/moderator powers and then added whatever additional information or views, filters, notifications or aggregations that moderators want in whatever UI that works better for moderators. Any ML/AI could also be added, with resultant metadata (or any other data for that matter) stored in a separate database. I’m probably missing something here, but I’m honestly a little confused.