Aleksorsist@azonenberg @urja that's actually more what I'm thinking. Basically the modules are always looking at the data, it's just new parameters that get clocked in once the previous condition is met. I can't think of a trigger that doesn't need a sequential list of conditions (with commands across channels treated kinda like multi-threading)
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.