I use butler a lot, but I have a free account and a limit of 50 commands, I know I am going to be told to just upgrade, but I think would be really nice if the butler system would be rethought. I think it would make more sense if the limit was either
A) Based on just the operations (So commands that do less take less away)
B) Based on resource consumption (CPU time/energy)
Or C) To diversify on B and make a certain resource value for each action that takes away from a whole value. For example, adding a tag could be 3, and setting a due date could be 5
These are the three ways I thought of that make the whole system just seem to make a lot more sense to me as a way of limiting use by making it so that commands that do less take less away from your total usage. You could also add some sort of rate-limiting/queuing to it so people can' spam the system with tasks. Thanks for reading!
@Kale Ko you can use the API directly instead of Butler, to do most of what you need. It takes some coding, but I have made that somewhat simpler with the Trellinator framework:
I also offer coding and hosting:
You can see loads of examples of stuff you can do with Trellinator here:
@Kale Ko You can either set it up yourself under Google Apps Script in which case you're technically paying for it under your Google license, or I can set it up for you, the minimum monthly cost is USD$10 (the cost goes up if you're processing a very high number of jobs).
@Kale Ko you can run Trellinator code on the command line, and you can set up your own webhook URL, so yeah I guess :) All the code for Trellinator is on github.
https://github.com/iaindooley/trellinator