tweets

This is data scraped from swyx's timeline! See blog post

3 rows where "created_at" is on date 2021-12-02, favorite_count = 1 and user = 33521530 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: in_reply_to_user_id, in_reply_to_screen_name

user 1 ✖

  • swyx · 3 ✖

retweeted 1 ✖

  • 0 3

favorite_count 1 ✖

created_at (date) 1 ✖

  • 2021-12-02 · 3 ✖
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
1466195579822694404 swyx 33521530 2021-12-02T00:00:41+00:00 @ShaneaLeven @jeanqasaur naw salesforce tracks sales just pointing out that this data often integrates faster into salesforce than salesforce integrates into other tools, therefore salesforce de facto is the eventual center of gravity for all CRM data unless of course you use @sgrove's @onegraph 😉       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [25, 300] 1466194337088385025 89629801 ShaneaLeven       0 0 1 0 0   en  
1466219481965809664 swyx 33521530 2021-12-02T01:35:40+00:00 @beyang @sourcegraph set some measurable level of "truly mainstream"?       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [21, 69] 1466213645872816128 16520821 beyang       0 0 1 0 0   en  
1466430577947594762 swyx 33521530 2021-12-02T15:34:29+00:00 @beyang @sourcegraph oh wow, that's a big "and" in there. well... good luck :)       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [21, 78] 1466409946002591744 16520821 beyang       0 0 1 0 0   en  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);