Hello Robert. Much of our development team uses Apple products, so we can sympathize with this issue. Our team was able to quickly locate the source of the conflict, which lies in how Safari treats CSRF tokens. Working around this requires a settings change in Safari. We are not comfortable with adding requirements for our users, so instead opted to research other ways the remedy the issue. However, if you wish to do this for yourself, you simply would uncheck "Prevent cross-site tracking" as shown below.

Personally, I think that particular reaction might be a bit extreme, but unfortunately the underlying issue is once again becoming important; Like we did when IE was king, we are beginning to see a growing number of websites that "only support" Chrome. This is a bad, bad, bad, bad thing. Website devs should always test, and support, a wide range of browsers. I also use Safari for nearly all everyday browsing, as many of the features it has are better than the competition (reader view, for example, is typically nicer than any other browser), but I specifically keep Firefox around for anything mission-critical and device-management related. Mozilla appears to be a great organization that supports open web standards and privacy protection, so give Firefox a try as an additional browser that won't make you feel like you are selling out to the new "Do Only Evil" version of Google.