tweets
6 rows where "created_at" is on date 2021-12-18, favorite_count = 0, is_quote_status = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang
This data as json, CSV (advanced)
Suggested facets: in_reply_to_user_id, lang
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1472112194666045444 | swyx 33521530 | 2021-12-18T07:51:12+00:00 | @zimmskal @symflower i think for open source its also very confusing to the contributor experience unless you go out of your way to document it. not sure how to fix except at a platform and industry normative level. like, no, i dont want to install the entire universe just to fix a typo in docs | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [21, 296] | 1472111793187217408 | 33521530 | swyx | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1472116783653998593 | swyx 33521530 | 2021-12-18T08:09:26+00:00 | @zimmskal @symflower @sourcegraph idk maybe issue automation isnt that necessary if we had better search and filtering. but for example if a PR only touches one repo dont rebuild the whole world. permissions not just about secrets, is also about approvers and reviewers. and hybrid closed/open source situations | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [34, 312] | 1472114790646665219 | 218911998 | zimmskal | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1472117742329335814 | swyx 33521530 | 2021-12-18T08:13:15+00:00 | @zimmskal @symflower no 😅 just been suppressing the error every time i commit. its really bad and i feel terrible about it. when i add change a file and the git hook runs lint, i have like 43 lint warnings about eslint+TS that idk how to fix. will try to consult @JoshuaKGoldberg before he leaves | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [21, 297] | 1472115447768174592 | 218911998 | zimmskal | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1472119027480809476 | swyx 33521530 | 2021-12-18T08:18:21+00:00 | @zimmskal @symflower @gitlab i probably gave too trivial of an examples. bash scripting to set up areas sounds ideal. make that part of the platform default tooling. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [29, 165] | 1472118001252065281 | 218911998 | zimmskal | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1472121311715540997 | swyx 33521530 | 2021-12-18T08:27:26+00:00 | @zimmskal @symflower @sourcegraph we (Temporal) are an open core company - core server, docs, sdk, protobufs are all open source. as company grows we need to build closed source extensions to some of these. would be nice to have both in same monorepo. | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [34, 251] | 1472119535125901312 | 218911998 | zimmskal | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1472105565845344256 | swyx 33521530 | 2021-12-18T07:24:51+00:00 | @ropsue wdym? | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [8, 13] | 1472104656755204098 | 49575745 | ropsue | 0 | 0 | 0 | 0 | 0 | pl |
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]);