tweets

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

2 rows where "created_at" is on date 2021-08-12, in_reply_to_screen_name = "swyx" and user = 33521530 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

user 1 ✖

  • swyx · 2 ✖

created_at (date) 1 ✖

  • 2021-08-12 · 2 ✖
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
1425624206524379136 swyx 33521530 2021-08-12T01:04:32+00:00 @temporalio something we debated at work that @martinfowler's Event Sourcing article leaves unclear: does Event Sourcing require you to fully reapply each function, or is it enough to just "dedupe" and restore state? https://news.ycombinator.com/item?id=28140598       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [12, 242] 1422424339589189633 33521530 swyx       0 0 2 0 0 0 en  
1425892922717704192 swyx 33521530 2021-08-12T18:52:19+00:00 Fixes for each: 🚫 iTunes: https://krausefx.com/blog/introducing-overkill-dont-let-itunes-interrupt-your-workflow 🚫 Mail: https://discussions.apple.com/thread/1856375 🚫 Dictionary: https://apple.stackexchange.com/questions/245592/el-capitan-how-to-disable-force-click-dictionary-pop-ups-in-chrome 💁🏽‍♂️ https://twitter.com/swyx/status/1425892922717704192/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 129] 1425889455643119616 33521530 swyx       0 1 31 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]);