i'm seriously now going to audit the whole codebase in the near future for all methods that don't have "err error" as their last return parameter and fix this up... it might be a big change in places but that's why we have go modules, you can use my old one, with the maybe you might forget to check if it's nil as an error, and later you can revise your api calls with the "oh, sorry, you have to assign the values first and then use them because if it's nil actually your code should not proceed, and that's not obvious"