tweets

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

4 rows where user = 727704217012604928 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

retweet_count 3 ✖

created_at (date) 3 ✖

is_quote_status 2 ✖

quoted_status 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
1457535446674718725 Mark Erikson 727704217012604928 2021-11-08T02:28:24+00:00 I spent the afternoon hacking on the experimental RTK "action listener middleware" API. After applying multiple suggestions, I'm excited to report that: **it now has support for long-running async workflows!** Changelog, discussion, and "docs" here: https://github.com/reduxjs/redux-toolkit/discussions/1648#discussioncomment-1603347       TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 277]             0 2 32 1 1 0 en  
1457535874837749765 Mark Erikson 727704217012604928 2021-11-08T02:30:06+00:00 The "workflow support" comes from adding a new `condition` option that's `(predicate) => Promise<boolean>`. It's based off of http://Temporal.io's https://docs.temporal.io/docs/typescript/workflows/#condition API. You can now wait for actions, state diffs, etc. Thanks to @swyx for suggesting this!       TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 276] 1457535446674718725 727704217012604928 acemarke       0 1 7 1 1 0 en  
1458630426709442562 Mark Erikson 727704217012604928 2021-11-11T02:59:28+00:00 In the spirit of "working in public", but also "I'm human" and "ARGH THIS IS BROKEN SOMEONE HELP ME": I've spent the last few days trying to rewrite the new RTK middleware types. Thus far I have completely failed. The _horribly_ hacked-up code is here: https://github.com/reduxjs/redux-toolkit/commits/feature/listener-middleware-fixes       TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 280]             0 2 20 1 1 0 en  
1467343720936792071 Mark Erikson 727704217012604928 2021-12-05T04:02:59+00:00 I'm not a frequent podcast listener, but I am _loving_ these deep-dive discussions that Swyx is recording. Great guests, thorough discussion of meaningful topics, and some really good insight into the state of our industry. https://twitter.com/swyx/status/1467304180003917824   1467304180003917824 1467304180003917824   TweetDeck 9335de48b3673c3f69433a34861c115d1d382be3 0 [0, 223]             1 5 45 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]);