tweets

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

1 row where "created_at" is on date 2021-08-16, in_reply_to_screen_name = "swyx" and quoted_status = 1367518496326709251

✎ View and edit SQL

This data as json, CSV (advanced)

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
1427351641095753755 swyx 33521530 2021-08-16T19:28:44+00:00 🧑‍🤝‍🧑 Community focused DevRel is the new hotness Nothing can build loyalty like helping your users find, hire and help each other. But beware the optics of relying on unpaid labor. Events are underrated, and "superuser" programs are on the rise! https://twitter.com/swyx/status/1367518496326709251   1367518496326709251 1367518496326709251   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 273] 1427351639904571412 33521530 swyx       1 0 5 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]);