tweets
4 rows where "created_at" is on date 2021-09-12, favorite_count = 1, is_quote_status = 0 and source = "9335de48b3673c3f69433a34861c115d1d382be3" sorted by lang descending
This data as json, CSV (advanced)
Suggested facets: in_reply_to_user_id, in_reply_to_screen_name, created_at (date)
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1437117701428744197 | swyx 33521530 | 2021-09-12T18:15:35+00:00 | @KennethCassel @reactjs tyvm for that! | TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 | 0 | [24, 38] | 1437117593014374402 | 1319269656264409088 | KennethCassel | 0 | 0 | 1 | 0 | 0 | sv | ||||||||
| 1437108035483279362 | swyx 33521530 | 2021-09-12T17:37:10+00:00 | @morsapaes yes! i think a lot of devrel programs mention this in theory but dont execute well on it in practice. do your OKRs/metrics line up well with your inward facing work? what are they? i really struggled with this one bc i havent seen it myself. | TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 | 0 | [11, 253] | 1437106885304389633 | 955397748580372480 | morsapaes | 0 | 0 | 1 | 0 | 0 | en | ||||||||
| 1437112843757891593 | swyx 33521530 | 2021-09-12T17:56:16+00:00 | @KennethCassel @reactjs haha ty. supabase gets a mention! altho i honestly dont have a strong view on whether supabase is best used on client or server side. you'd be a good person to ask - where do you make your supabase sdk calls? | TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 | 0 | [24, 232] | 1437111897887752196 | 1319269656264409088 | KennethCassel | 0 | 0 | 1 | 0 | 0 | en | ||||||||
| 1437113679233916934 | swyx 33521530 | 2021-09-12T17:59:36+00:00 | @KennethCassel @reactjs yeah gotcha. i figured! thats where i put supabase too. | TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 | 0 | [24, 79] | 1437113333732331522 | 1319269656264409088 | KennethCassel | 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]);