Fair point. To mitigate this, we never store your password. Basically we exchange your username/password combo for a token from Hype Machine which is used to authenicate requests.
The only data we store are your username and some basic settings in a .plist (`open ~/Library/Preferences/com.Plug.Plug.plist`) and your token which you can view in Keychain Access.app and search Plug.
The app looks awesome, and also served as my introduction to Hype Machine. How I haven't managed to hear of this service before is beyond me. Now I'm just sad I didn't know it existed until now.
Also great to hear that Swift development is going smoothly. I just started into learning it, and so far the strangest thing I've found is that I've learned a ton of Objective C by having to struggle through missing documentation/examples and having to learn the Obj C way of doing things and then translating them to Swift. It's been interesting.
I'm intrigued by optionals, but I feel like returning nil for objects in ObjC - a pattern I've always used - is kind of the same thing in a different like. Do you have experience with returning nil instead of objects? How does that compare to optionals?
Yes, i did use that same pattern. And if you want to, you can kind of force Swift to do this (String! is an "unwrapped optional" and can be nil or have a value) but it feels unnatural. You definitely have to design a bit differently than ObjC. Luckily Swift's enums are amazing and you can return multiple values (through tuples), so there are great ways to return different types of values.