tweets
2 rows where display_text_range = "[47, 318]" sorted by lang
This data as json, CSV (advanced)
in_reply_to_screen_name 2 ✖
- HorusGoul 1
- SaraJChipps 1
created_at (date) 2 ✖
- 2021-10-15 1
- 2021-11-24 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1449120277393117185 | swyx 33521530 | 2021-10-15T21:09:32+00:00 | @HorusGoul @CascadiaJS @temporalio @typescript currently you need some devops skill to self host Temporal Server and your own Workers, since it was designed for backend devs who are used to doing these things. However there are ongoing projects to make it run in a single binary + hosting Workers for you in future :) | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [47, 318] | 1449118387016278018 | 608298095 | HorusGoul | 0 | 0 | 5 | 0 | 0 | en | ||||||||
1463630230665367558 | swyx 33521530 | 2021-11-24T22:06:54+00:00 | @SaraJChipps @cherthedev @levlinds @bitandbang indeed the sheer credentialism and gatekeeping in traditional tech fields has made me start asking “have you thought about web3?” when aspiring developers ask me about how to break into tech. i can’t recommend it bc i haven’t done it, but it’s clearly far more welcoming. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [47, 318] | 1463584905254916098 | 15524875 | SaraJChipps | 0 | 0 | 2 | 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]);