This page describes the extremely useful expedite feature. See also cohorts.
Peter finds that a Plucky delay of 2 hours works well for him. But waiting 2 hours for every change is sometimes inconvenient. He wishes he could give Susan the ability to approve any changes he makes without waiting for the 2 hour delay. He can, using expedite.
How to set it up
A user must be part of a cohort or have at least one supporter in order to use expedite. Of course, all new users are automatically added to the Everybody cohort, and so can make requests of others in this same very large cohort without preparing in advance.
To reiterate, in order to expedite you need one or more of the following:
Cohorts (mutual support with other Plucky users).
Supporters (specific people you trust such as friends).
Making an expedite request
Once you have a pending configuration change (i.e., a rule that has not taken effect yet), an expedite request can be made by clicking the “expedite” button.
Click the Plucky button in your browser. The button is on the “config” page, next to each pending configuration item. In addition, expedite requests can be sent to u.pluckeye.net for up to 10 recently added but still pending configuration changes by typing the following in a console.
If you have several pending changes, you can expedite ones that match a particular pattern by typing that pattern after
For example, the following sequence will expedite only a request for
allow foo.com, and not one for
pluck + delay 99 pluck + allow foo.com pluck + allow bar.com pluck expedite foo
In Plucky 1.0.64 and above, you can use the
-n argument to see what Plucky would expedite without actually creating the expedite requests. This can be useful when you have a lot of pending changes and you only want to expedite the most important ones.
pluck -n expedite
Approving an expedite request
Expedite requests show up and can be approved on your queue. The web page uses “notifications” so that by loading it into one of your browser tabs, you can be notified of an expedite request without needing to actively check the page.
Getting an expedite approval
If the expedite request is approved and the change isn’t immediate, you can run
pluck sync to request that Plucky check for expedite approvals.
Expediting a change to the delay
Expediting a change to the delay requires expediting the new delay and removal of the current delay. For example,
pluck delay 90 pluck delay 0 pluck expedite -n
After running the above commands, the output of
expedite -n is:
Creating expedite request for - "delay:90" Creating expedite request for + "delay:0"
Both of these changes must be expedited for the delay to change from 90 to 0. This behavior may change someday because it isn’t as much by design as by accident, but until then, that’s how it works.
If you have abused the expedite system, even once, you should probably use the noexpedite feature to prevent yourself from doing that again.
pluck + noexpedite
After that, mourn the loss of the really useful expedite feature, and keep on pluckin'.
supplicate, mayprove, approved?
As of Plucky 1.0.61, the following commands are no longer recommended because they use older expedite code that has largely been supplanted by the new
pluck expedite commands above, the one caveat being that
pluck expedite requires a user account on https://u.pluckeye.net/ .
pluck supplicate # replaced by pluck expedite pluck mayprove # replaced by pluck sync, but often unnecessary pluck approved? # replaced by pluck sync, but often unnecessary
pluck mayprove was necessary to fetch old approvals, and while
pluck sync is similar in that it would fetch new expedite approvals, most of the time it is unnecessary to run
pluck sync manually because it is usually invoked automatically in the new expedite code.