tweets

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

1 row where favorite_count = 457, source = "95f3aaaddaa45937ac94765e0ddb68ba2be92d20" and user = 24179991 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

  • Daniel Vassallo · 1 ✖

retweeted 1 ✖

  • 1 1

favorite_count 1 ✖

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
1460851683542515713 Daniel Vassallo 24179991 2021-11-17T06:05:57+00:00 When I was an employee, I had daily/weekly/monthly/yearly goals. I would have plans on how to meet them, and anything unexpected was almost always undesirable. Nowadays, it’s the opposite. Almost everything important comes from random unexpected events.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 254]             0 26 457 1 1   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]);