@matthenderson@benbrooks I can’t see that happening, but I would certainly love to see anything more in the range of documentation, macro examples, third party actions, etc. I’m just not sure how to make it happen.
@benbrooks@matthenderson charging for training or support puts a negative feedback into the system, encouraging complexity and confusion instead of simplicity and understandability. This is definitely not a direction I would go in!
@matthenderson thanks for the article. I liked how @benbrooks put it - Keyboard Maestro needs 10,000 more pages in the documentation. It already runs to 100 pages long, its hard to imagine making it more detailed.
@danielpunkass true enough. Plus when I first looked at it it was riddled with bugs - I imagine its a lot better now (your previously tweet (what’s an ADN message here called?) indicates otherwise of course).