The most promising project in terms of plugins is Bonfire (they call them extensions)
Forkeys have a plugin system already. I’ve built a few things with it, but usage isn’t widespread, at least outside of Misskey. I wrote a bit about it and created some documentation. (Maegul your name is super familiar, apologies if you already knew about this)
I don’t think generic apub plugins will work, but a plugin system for lemmy makes a lot of sense and pople like me could then help add the features we need
Plugin a thing in so many software, from firefox, to wordpress, to godot engine, to unity engine to whatever else. I doubt it’s something extraordinary to pull off
Hmm, interestingly, the mastodon thread has more answers from mastodon users, which did not appear to deferate to lemmy. I wonder if they have lemmy.ml blocked
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.
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.
Add comment