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
You can say it shouldn’t matter. But it really does. It’s nice to have Unix process management, it’s great to be able to lash things together with stringly types blobs, but eventually, we always move from pidgin to creole (to borrow phrasing from actual linguistics).
So how are process exit codes different from shared library return codes different, exactly? What makes it more likely that a stupid user will not check the former but will check the latter? Your argument is valid, but *this bug* is not a good example against processes and pipes
No, that’s what you’re not getting. It really is the fragility of the interface that gets you the “It returns content by default, hope you’re smart enough to check the error code, what do you mean nothing did” surprise not surprised dynamic
Again, that "it returns content by default" is a *consequence* of the streaming design of the interface. It would be *exactly the same* as a shared library, with that design constraint. You'd end up with a "more data" callback getting called before the main entry returns error.
If the bug were due to a weakly typed error message being ignored by default in a client then you'd have a point. But it isn't. The gpg command exits with a big fat retcode 2. That's just as good as a C function returning an error code.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
