tweets

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

1 row where "created_at" is on date 2021-10-21 and source = "6746f3a6d1b3aa371a4a2dc1c08c7862cd6e911e" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

source 1 ✖

  • FeedHive.io · 1 ✖

created_at (date) 1 ✖

  • 2021-10-21 · 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
1451156477587116040 Jannik Wempe 1116441589012934657 2021-10-21T12:00:40+00:00 You have a lot of influence on how much luck you have. Maybe you can't change the odds themselves, but you can change the "Luck Surface Area". This article by @swyx made me think quite a lot the last few days 🤔 https://www.swyx.io/create-luck/       FeedHive.io 6746f3a6d1b3aa371a4a2dc1c08c7862cd6e911e 0 [0, 237]             0 3 16 1 1 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]);