tweets
2 rows where "created_at" is on date 2018-06-24 and user = 33521530 sorted by lang
This data as json, CSV (advanced)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1010677126897504256 | swyx 33521530 | 2018-06-24T00:12:59+00:00 | Ever wondered what the @gatsbyjs bootstrap output means every time you type `gatsby develop`? I went code spelunking today and wrote them up in this gist: 👉🏼 https://gist.github.com/sw-yx/09306ec03df7b4cd8e7469bb74c078fb 👈🏼 there's a lifecycle chart to be made somewhere here but this is the primary sequence. https://twitter.com/swyx/status/1010677126897504256/photo/1 | Twitter Web Client 887710c0899816dfe9fb0176eb05d760cbe15732 | 0 | [0, 273] | 0 | 11 | 72 | 0 | 0 | 0 | en | ||||||||||
1010922550912802816 | swyx 33521530 | 2018-06-24T16:28:12+00:00 | 🚴🏼♂️🏠New Bikesheddy Opinion: Frameworks should **enforce** vertical separation of code (organize by feature), rather than horizontal (organize by type). Make separation the default and interactions explicit. Change My View. https://twitter.com/swyx/status/1010922550912802816/photo/1 | Twitter Web Client 887710c0899816dfe9fb0176eb05d760cbe15732 | 0 | [0, 225] | 0 | 15 | 102 | 0 | 0 | 0 | en |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [tweets] ( [id] INTEGER PRIMARY KEY, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [full_text] TEXT, [retweeted_status] INTEGER, [quoted_status] INTEGER, [place] TEXT REFERENCES [places]([id]), [source] TEXT REFERENCES [sources]([id]), [truncated] INTEGER, [display_text_range] TEXT, [in_reply_to_status_id] INTEGER, [in_reply_to_user_id] INTEGER, [in_reply_to_screen_name] TEXT, [geo] TEXT, [coordinates] TEXT, [contributors] TEXT, [is_quote_status] INTEGER, [retweet_count] INTEGER, [favorite_count] INTEGER, [favorited] INTEGER, [retweeted] INTEGER, [possibly_sensitive] INTEGER, [lang] TEXT, [scopes] TEXT, FOREIGN KEY([retweeted_status]) REFERENCES [tweets]([id]), FOREIGN KEY([quoted_status]) REFERENCES [tweets]([id]) ); CREATE INDEX [idx_tweets_source] ON [tweets] ([source]);