Problem
I would personally like a way to have a (for the user) readonly connection which can be added via an integration.
This would be used to show that they are a verified user of a website I also host.
I doubt something like this would be merged into main (a custom connection, readonly, that end users are unable to remove), so I was thinking how it could be implemented without touching much of Fluxer's code at all.
Proposal
A way for people to develop plugins for the various packages (app, api, admin etc) installed from the admin panel on a plugin page, which would allow for custom behaviour, without affecting Fluxer code directly, so people can pick and choose features to implement into their self-hosted instance.
This could be custom connections on profiles, additional fields, channel types, system behaviour, it would be quite expandable especially for things which aren't likely to be implemented into the main repository
A plugin system would also mean that updating Fluxer would be simpler due to not needing to manage merge conflicts if people code features in themselves
5 comments
Comment by @kokomo123
Comment by @vesaber
Comment by @snappyapple632
Comment by @vesaber
Comment by @rogue-agent