tweets

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

3 rows where favorite_count = 82 and source = "95f3aaaddaa45937ac94765e0ddb68ba2be92d20" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

created_at (date) 3 ✖

user 2 ✖

source 1 ✖

  • Twitter for iPhone · 3 ✖

favorite_count 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
1134311153960534016 Lee Byron 14904098 2019-05-31T04:10:28+00:00 Super curious to see how this works out. Historically I’ve been very skeptical of schema federation and the costs it incurs on an org, so I’m hoping to learn from the community on what works and doesn’t work from this new attempt. https://twitter.com/apollographql/status/1134086759489384449       Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 230]             1 11 82 0 0 0 en  
1430388488923324417 swyx 33521530 2021-08-25T04:36:05+00:00 @mikeal i worked at AWS and supabase is outshipping teams 10x their size and funding. i dont know whats in the water there but @kiwicopple and team have got it. https://twitter.com/swyx/status/1424586713490358275?s=21   1424586713490358275 1424586713490358275   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [8, 185] 1430193529565839368 668423 mikeal       1 6 82 0 0 0 en  
1447312313426460672 swyx 33521530 2021-10-10T21:25:19+00:00 Obsessed by how turning sync into async processes improves UX. Imagine an API call w/ 5 requirements fails bc 2 inputs were invalid. Instead of keeping state on client or duplicating validation, the API call starts a session and you “talk” with it to resolve the invalid inputs. https://twitter.com/swyx/status/1445299225974095877   1445299225974095877 1445299225974095877   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 279]             1 4 82 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]);