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
Applications can now be either triggers or responders, but not both at the same time. As I see, apps with TRIGGER action (info.guardianproject.panic.action.TRIGGER) are responders. Apps with CONNECT/DISCONNECT actions and without TRIGGER action are triggers. Apps with both TRIGGER and CONNECT/DISCONNECT are responders that have the functionality of connecting triggers. Therefore, we cannot create an application that will be a trigger and a responder at the same time.
For example, we are working on messenger. If it receives a panic message, it will trigger other applications. But it must be able to receive a panic signal, (for example, from Ripple), and clear the messages. Thus it should be trigger and responder at the same time.
It might make sense to add an UNIVERSAL action or something like that to detect apps that are triggers and responders at the same time.
The text was updated successfully, but these errors were encountered:
Applications can now be either triggers or responders, but not both at the same time. As I see, apps with TRIGGER action (info.guardianproject.panic.action.TRIGGER) are responders. Apps with CONNECT/DISCONNECT actions and without TRIGGER action are triggers. Apps with both TRIGGER and CONNECT/DISCONNECT are responders that have the functionality of connecting triggers. Therefore, we cannot create an application that will be a trigger and a responder at the same time.
For example, we are working on messenger. If it receives a panic message, it will trigger other applications. But it must be able to receive a panic signal, (for example, from Ripple), and clear the messages. Thus it should be trigger and responder at the same time.
It might make sense to add an UNIVERSAL action or something like that to detect apps that are triggers and responders at the same time.
The text was updated successfully, but these errors were encountered: