You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I honestly cannot fucking believe this worked as well as it did. How on earth. what the fuck @ me, what the hell were you thinking.
You can have as many threads or processes listening on the same port as you want with SO_REUSEPORT. The "several threads calling accept()" pattern is also not uncommon, though not as good as SO_REUSEPORT.
I am aware of this fact. This is not the issue. The issue is that I forgot an edge case that resulted in 2 threads racing for control of the port.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
