tweets

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

1 row where "created_at" is on date 2021-07-28, quoted_status = 1420423346727051268 and user = 33521530 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

  • swyx · 1 ✖

quoted_status 1 ✖

  • 1420423346727051268 · 1 ✖

created_at (date) 1 ✖

  • 2021-07-28 · 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
1420477145969618946 swyx 33521530 2021-07-28T20:11:57+00:00 My opinion: you want standard comp (cash/stock) up to ~150k, THEN you want options. Why? TAXES. esp with 83b election. Give yourself a ~40% raise with this ONE WEIRD TRICK! You know how you should be critical of tech advice from online? Goes double for devs talking finance :) https://twitter.com/cassidoo/status/1420423346727051268   1420423346727051268 1420423346727051268   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 280]             1 0 46 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]);