tweets

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

2 rows where "created_at" is on date 2021-10-12 and favorite_count = 10

✎ 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
1448040791629185025 swyx 33521530 2021-10-12T21:40:02+00:00 Now the hard question: Could Amazon host Temporal as a service? Yes. Just like Hashicorp does (https://twitter.com/mitchellh/status/1316510643030114304?s=20), or Stripe (come learn more at our Nov meetup http://temporal.io/meetup), or {REDACTED_BIGCORP}, in a long tradition that goes back to our origins at Uber.   1316510643030114304 1316510643030114304   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 274] 1448027264289959938 33521530 swyx       1 0 10 0 0 0 en  
1448044941679022083 swyx 33521530 2021-10-12T21:56:32+00:00 @temporalio That is not to say we aren't mature! Just that it buys time and trust. We are already SOC2Type2 certified and serving multi-bn $ publicly listed companies in production. We're just not GA/self serve yet. (We're taking waitlist signups for Temporal Cloud https://temporal.io/cloud)       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [12, 291] 1448043292881420293 33521530 swyx       0 0 10 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]);