tweets: 1425253637979181061
This data as json
| id | user | created_at | full_text | retweeted_status | quoted_status | place | source | truncated | display_text_range | in_reply_to_status_id | in_reply_to_user_id | in_reply_to_screen_name | geo | coordinates | contributors | is_quote_status | retweet_count | favorite_count | favorited | retweeted | possibly_sensitive | lang | scopes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1425253637979181061 | 33521530 | 2021-08-11T00:32:01+00:00 | @ritakozlov_ it does look good! the problem (that we are also wrestling with) is when you tie API to cron its hard to do some things like "every 3rd wednesday" or "last day of the month" as this code sample was probably trying to do also we're designing for long running wfs that may overlap https://twitter.com/swyx/status/1425253637979181061/photo/1 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [13, 293] | 1425240576975278080 | 232076816 | ritakozlov_ | 0 | 0 | 5 | 0 | 0 | 0 | en |