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
Things that annoy me: devs with zero-tolerance bug reporting policies. No, if I just debugged the problem for you and told you exactly what chain of events caused it and how, you do *not* need 500kB of logs and pages of system info from me any more.
If I file a bug having done half your work and you close it as NEEDINFO asking for redundant logs, I'm just going to locally patch your software and move on and your other users can suffer and you can go ahead and debug everything by yourself all over again.
Apple?
Nah, random Gentoo bug wrangler. Most don't care when I don't spam the tracker with `emerge --info` and build logs when I already found the problem (and I just want the package maintainer to fix it), but apparently some do. And honestly, I can't be arsed.
I feel like a majority of the time someone asks for logs they ultimately never respond once you provide them. Asking for logs is the cheapest way one can help in cases like this.
I have once offered a company to keep a device in failure state online and extract all the info they need, with a power cycle being a known workaround. It took me a few days to convince them that even if I could "fix" the device by power cycling, I want to help *them* debugging.
They ended up accepting my offer and requested a wireshark trace of a `curl $host/`, and nothing more. Apparently that is supposed to help debugging a web server responding with an internal server error.
I power cycled the machine and closed the issue.
Do you remember the fights I had because I was linking to the logs rather than attaching?
Sigh...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
