You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the kernel' APP_ID and APP_PRIVATE_KEY have been exposed as org secrets I think I should go back to my original implementation where the worker for this plugin controlled the dispatching of it's own workflows for MTProto API (workrooms, etc...) features.
with two config entries ubiquity-os kernel is dispatching tons of workflows for no reason which can be avoided
self-dispatched means we can validate no-op payloads first
it's cleaner and more efficient from a plugin standpoint
removes the need for two entries in the config
optimizes the github rate limit consumed by this plugin
it's no longer considered "unsafe" to do so or the secrets wouldn't be exposed
The text was updated successfully, but these errors were encountered:
Now that the kernel'
APP_ID
andAPP_PRIVATE_KEY
have been exposed as org secrets I think I should go back to my original implementation where the worker for this plugin controlled the dispatching of it's own workflows for MTProto API (workrooms, etc...) features.The text was updated successfully, but these errors were encountered: