tweets

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

1 row where "created_at" is on date 2021-10-12 and display_text_range = "[0, 266]"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: 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
1448027262121496578 swyx 33521530 2021-10-12T20:46:16+00:00 To put Temporal inside of Netflix's "paved road", they needed every part of the stack to adapt to their needs, from Fast Properties (config store) to Chaos Monkey (fault injection) to Metatron (certs) to Wall-E (authn) to Gandalf (authz) to their own flavor of gRPC. https://twitter.com/swyx/status/1448027262121496578/video/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266] 1448024109389008896 33521530 swyx       0 0 9 0 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]);