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 know that, but create_or_find is also racy, and its own docs say as much, so I'm confused about why it's been added if I wanted consistency I wouldn't use either of these APIs
I am definitely not advocating that `create_or_find` is a good API. I argued against adding it at the time. For real improvement to happen though, I think Rails needs to:
- Become more comfortable with APIs that are coupled to a single DB. Upsert in particular is really tricky, and the number of DB agnostic APIs you can build for it are *extremely* limited - Build more APIs focusing on the DB as the source of truth.
Users are too used to the app holding state, and then telling the DB, expecting consistency. It's hard to undo that and train folks that it woks by giving the DB a change and then asking it for the state of things
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
