@UniversalORL#AskUniversal trying to get some help around check in and package delivery but in their air on a new flight without phone service. Is there any chat option to our hotel?
@whignewtons my son is convinced we are watching a recording of The Dispatch Live with how much y’all are saying “Biden”. @stephenfhayes just said “Biden” too. It’s spreading.
@whignewtons I thought of David’s theory about how the courts are becoming the place of first resort because they have to respond: https://t.co/2ZyEEwfMMQ
Now they’re handing Facebook’s customer service.
I've launched my Swift blog 📖!
I'll be exploring topics less discussed in the Swift community, with the modest goal of 1 article per month.
The first article: https://t.co/8S4cVJlPHP
Check it out and let me know what you think!
And if you like it, subscribe to RSS 📡
Cheers!
New discovery: I _can_ get the command line option to work but I had to use "127.0.0.1" to refer to my local machine instead of "localhost". Apparently the latter will just fail silently? Or maybe I missed an error/warning somewhere.
Can any Android peeps explain why everything I have found regarding setting the emulator 's proxy appears to be wrong? Only way I could get mitmproxy working was to set the proxy setting directly in the WiFi setting of Android.
The entire Internet was telling me to set it in Android Studio, or the emulator settings or on the command line (emulator -avd <device> -http-proxy <proxy>. None of those options seemed to affect the network settings at all.