I would venture that H Janson wrote it . <| sep |> The only Theo slash fic I have saved is a short little oneshot linkao 3 The Housewarming Party by dracogotgame <| sep |> I would not trade KAT for AD <| sep |> Let ' s go bowling . <| sep |> I believe it ' s Tropico with a Marxist ideology . <| sep |> thank you , this is very good advice . Currently the I ' m using this on the back end cycles the tokens every 5 seconds on e . g . i send a request , it invalidates that token , and returns a new one , but there is a five second window in the event that i ' m sending multiple requests concurrentlyso basically my workflow is to use alamofire , with a custom request adapter . this allows me to call # request normally , but will intercept it , attatch the auth headers , and forward it to the server . then I just catch the responses as normal , and update the token in keychain if one was sent back from the server . I strongly agree on the fact that I will have to deal with weird failure models that I ' m not used to , so I ' ll need to study up on best practices . here ' s the part that still feels a little weirdare you saying it ' s ok that i essentially have a view controller that ' s empty shown initially , like this