issue_comments

Table actions

7 rows where author_association = "MEMBER" and "created_at" is on date 2019-11-03 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, created_at (date), updated_at (date)

user 1

author_association 1

  • MEMBER · 7 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
549096321 https://github.com/dogsheep/twitter-to-sqlite/issues/3#issuecomment-549096321 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/3 MDEyOklzc3VlQ29tbWVudDU0OTA5NjMyMQ== simonw 9599 2019-11-03T01:27:55Z 2019-11-03T01:28:17Z MEMBER

It would be neat if this could support --since, with that argument automatically finding the maximum tweet ID from a previous search that used the same exact arguments (using the search_runs table).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Command for running a search and saving tweets for that search 488833975  
549095641 https://github.com/dogsheep/twitter-to-sqlite/issues/27#issuecomment-549095641 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/27 MDEyOklzc3VlQ29tbWVudDU0OTA5NTY0MQ== simonw 9599 2019-11-03T01:12:58Z 2019-11-03T01:12:58Z MEMBER

It looks like Twitter really want you to subscribe to a premium API for this kind of thing and consume retweets via webhooks: https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/api-reference

I'm going to give up on this for the moment.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 retweets-of-me command 514459062  
549095463 https://github.com/dogsheep/twitter-to-sqlite/issues/27#issuecomment-549095463 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/27 MDEyOklzc3VlQ29tbWVudDU0OTA5NTQ2Mw== simonw 9599 2019-11-03T01:10:52Z 2019-11-03T01:10:52Z MEMBER

I imagine it won't, since the data I would be recording and then passing to since_id would be the highest ID of my own tweets that have been retweeted at least once. So it won't be able to spot if I should check for fresh retweets of a given tweet.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 retweets-of-me command 514459062  
549095317 https://github.com/dogsheep/twitter-to-sqlite/issues/27#issuecomment-549095317 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/27 MDEyOklzc3VlQ29tbWVudDU0OTA5NTMxNw== simonw 9599 2019-11-03T01:08:10Z 2019-11-03T01:08:10Z MEMBER

Hmm... one thing that could be useful is that retweets_of_me can support a --since parameter - so if run frequently it should hopefully let us know which tweets we would need to run statuses/retweets/:id.json against.

I'm not sure if the --since parameter would show me a tweet that was previously retweeted but has now been retweeted again. I'll have a bit of a test and see.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 retweets-of-me command 514459062  
549095217 https://github.com/dogsheep/twitter-to-sqlite/issues/27#issuecomment-549095217 https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/27 MDEyOklzc3VlQ29tbWVudDU0OTA5NTIxNw== simonw 9599 2019-11-03T01:06:25Z 2019-11-03T01:06:25Z MEMBER

Wow, that retweets_of_me endpoint is almost completely useless: $ twitter-to-sqlite fetch https://api.twitter.com/1.1/statuses/retweets_of_me.json It returns my own tweets that have been retweeted, but with no indication at all of who retweeted them.

It looks like this needs to be combined with this API - https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/get-statuses-retweets-id - to fetch the details of up to 100 recent users who actually DID retweet an individual status. But that has a one-every-12-seconds rate limit on it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 retweets-of-me command 514459062  
549094229 https://github.com/dogsheep/github-to-sqlite/issues/5#issuecomment-549094229 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/5 MDEyOklzc3VlQ29tbWVudDU0OTA5NDIyOQ== simonw 9599 2019-11-03T00:44:03Z 2019-11-03T00:44:03Z MEMBER

Might not need an incomplete boolean - may be possible to handle this with alter=True and then by filtering for users with null values in certain columns.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add "incomplete" boolean to users table for incomplete profiles 493671014  
549094195 https://github.com/dogsheep/github-to-sqlite/pull/8#issuecomment-549094195 https://api.github.com/repos/dogsheep/github-to-sqlite/issues/8 MDEyOklzc3VlQ29tbWVudDU0OTA5NDE5NQ== simonw 9599 2019-11-03T00:43:16Z 2019-11-03T00:43:28Z MEMBER

Also need to take #5 into account - if this command creates incomplete user records, how do we repair them?

And make sure that if we run this command first any future commands that populate users don't break (probably just a case of using alter=True in a few places).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 stargazers command, refs #4 516763727  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);