tweets

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

1 row where user = 1290693397 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

created_at (date) 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
1456915351241990145 Lou ☁️ 👨‍💻🏋️‍♂️🎸🚴🏻‍♂️🏍 1290693397 2021-11-06T09:24:22+00:00 In some senses, I do think he's right ✅ @swyx did a good job of outlining the problem. When we're new to content and/or tech it feels natural to write "beginner content" or sometimes meta-content (content about content—wait, that's *this thread* 😱 😆) https://www.swyx.io/meta-creator-ceiling/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 276] 1456915349639680008 1290693397 loujaybee       0 2 6 1 1 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]);