tweets
3 rows where in_reply_to_user_id = 12816182 sorted by lang
This data as json, CSV (advanced)
Suggested facets: source, is_quote_status
created_at (date) 2 ✖
- 2021-07-28 2
- 2021-10-23 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1420211877276049408 | swyx 33521530 | 2021-07-28T02:37:52+00:00 | @matiasfha @Rich_Harris @stolinski @gndx Svelte also has one way data flow under the hood, but uses binding and syntax sugar to simulate LOCAL two way data flow. its not that different. data propagation with stores vs context however are very different. | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [41, 255] | 1420201456108441603 | 12816182 | matiasfha | 0 | 2 | 24 | 0 | 0 | en | ||||||||
1420261009583788032 | swyx 33521530 | 2021-07-28T05:53:06+00:00 | @matiasfha @Rich_Harris @stolinski @gndx btw you can implement the same thing for React too. its just that the React core team prefers boilerplate to sugar syntax. https://twitter.com/swyx/status/1294310598419689472?lang=en | 1294310598419689472 1294310598419689472 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [41, 187] | 1420216170402091009 | 12816182 | matiasfha | 1 | 1 | 5 | 0 | 0 | 0 | en | ||||||
1452037531244007427 | swyx 33521530 | 2021-10-23T22:21:39+00:00 | @matiasfha @kyleshevlin yep. this needs to be on the svelte FAQ somewhere lol its such a common question by react devs | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [24, 118] | 1452031976517427202 | 12816182 | matiasfha | 0 | 0 | 3 | 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]);