Open neocryptek opened 6 years ago
That's correct. But let me note it for further discussion as we build out support for DisaOpenSource this year.
@neocryptek May I know what is the use-case you are thinking of?
I had some ideas for mirroring between plugins, priority fallback between plugins, or backup/sync between plugins, etc. Lots of interesting and unique features could be built taking advantage of multiple services support in Disa! Listening to/injecting into the Bubble event stream seemed like the perfect entry point for plugin to plugin communication (without having to modify/couple every plugin together to support such features).
My concern is that the said feature comes with huge security and privacy implication, which can very easily be exploited by bad actors.
Do you have any more information on what "build out support for DisaOpenSource this year" entails?
Is it possible to subscribe to bubbles from other plugins or send bubbles to other plugins?
I assume not since bubbles seem to have a reference to the service they were sent to, so they seem to be coupled to that service, not a generic messaging event system?
https://github.com/Disa-im/DisaOpenSource/blob/710effae5a5ddc7440e841eac503887894b46e36/Disa.Framework.Shared/Bubbles/Bubble.cs#L61