tweets
4 rows where "created_at" is on date 2021-08-18 and retweet_count = 1 sorted by display_text_range
This data as json, CSV (advanced)
Suggested facets: user, source, is_quote_status
in_reply_to_screen_name 2 ✖
- ThisIsMissEm 1
- swyx 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1428094708899745793 | swyx 33521530 | 2021-08-18T20:41:25+00:00 | 2 years on... nice explanation and discussion of JWTs here, and I pretty much am exactly where Emelia is at https://twitter.com/ThisIsMissEm/status/1427988073292476418?s=20 | 1427988073292476418 1427988073292476418 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 132] | 1133780714988736512 | 33521530 | swyx | 1 | 1 | 10 | 0 | 0 | 0 | en | ||||||
1428130743381762055 | swyx 33521530 | 2021-08-18T23:04:37+00:00 | Just got reminded its the 3 year anniversary of my first conf talk: https://www.youtube.com/watch?v=nyFHR0dDZo0 I remember being so nervous, just 1 year out of bootcamp talking React in front of my heroes @ReactRally. Never regretted it. If you can, speak at a conference. Will change your life. https://twitter.com/swyx/status/1030130810588819456 | 1030130810588819456 1030130810588819456 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 277] | 1 | 1 | 71 | 0 | 0 | 0 | en | |||||||||
1428048895850942471 | swyx 33521530 | 2021-08-18T17:39:23+00:00 | Advice for coworker new to @savvycal_: There's an unspoken etiquette to scheduling links. It can seem rude as it requires the other side to fit to your schedule Preempt it: “I’d be happy to book a meeting if you have a calendar link, or I can send you mine” and link if hypertext | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 280] | 0 | 1 | 19 | 0 | 0 | en | |||||||||||
1427988073292476418 | Emelia 👸🏻 14063149 | 2021-08-18T13:37:42+00:00 | @JessTelford JWTs for external use tend not to solve the problems people think they do; for internal use, or cross authorisation boundaries, they can be good because then you can assert using public/private key cryptography that the token your presented really came from the authorising server | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [13, 293] | 1427986367905161221 | 14063149 | ThisIsMissEm | 0 | 1 | 14 | 0 | 0 | en |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);