tweets

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

3 rows where "created_at" is on date 2021-12-10 and retweet_count = 1

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

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
1469128619716870146 swyx 33521530 2021-12-10T02:15:32+00:00 @JoeEmison @dmessing something i didnt stick around long enough to understand at Amplify was why people running atop AWS could build a faster experience than Amplify. You could blame CFN/CloudFront, but then @begin does that, with like a team of 4 people. wish i had the time to figure it out.       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [21, 293] 1469052947262754820 272692606 JoeEmison       0 1 14 0 0   en  
1469145149162676224 swyx 33521530 2021-12-10T03:21:13+00:00 When you need to do API design, call a frontend developer. The upside of the competitiveness in frontend tooling and bikeshedding on frameworks and libraries is you get a fine sense for good DX. Loving @_jstejada's explanation of React in this light: https://youtu.be/FZ0cG47msEk?t=535       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 277]             0 1 61 0 0 0 en  
1469447948475850752 swyx 33521530 2021-12-10T23:24:26+00:00 Some of my fav parts of working at @temporalio is doing architecture calls with developers who are seriously evaluating us to replace janky ad hoc systems of cronjobs and scripts. real quote from a call today: “This is going to solve every backend problem I ever had” 😍       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 270]             0 1 41 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]);