tweets
2 rows where display_text_range = "[18, 298]" sorted by lang
This data as json, CSV (advanced)
created_at (date) 2 ✖
- 2021-07-30 1
- 2021-11-23 1
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1421225521178763266 | swyx 33521530 | 2021-07-30T21:45:43+00:00 | @acdlite @reactjs ya i see fixtures as "manual tests" that complement e2e/unit/integration testing. By all means automate everything if you can, but there's a lot of stuff that can't be automated, particularly bugs we don't know about yet. Fixtures help reduce the activation energy to repro bugs! | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [18, 298] | 1421224201181143040 | 21782915 | acdlite | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1463069720802783244 | swyx 33521530 | 2021-11-23T08:59:38+00:00 | @gr2m @temporalio we frame it as “It is designed with TypeScript-first developer experience in mind, but works equally well with JavaScript.” in our docs this is because the team feels strongly that type safety should be heavily recommended as part of the DX of using Temporal. Eliminates footguns | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [18, 298] | 1462998929562214404 | 11754732 | gr2m | 0 | 0 | 1 | 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]);