Twitter retweet archived and filesize filter

[wankio]

1. example :

x.com/xxshisan
x.com/httbaa

these are two of many files when download with above two user
the files are exactly same, retweet from same {author[id]}, only retweet id is diff, how to prevent these problems ? i don't want to download dupplicated content which have retweeted or reposted etc by multiple users

/xxshisan/retweets/c68679+1894739424019382390_1325840882394755072_RT @c68679_ 【专注05后得吃】女大学生的大奶的乳交，谁不爱？？@DaguidiyNone_1.mp4
/httbaa/retweets/c68679+1894757099214954762_1325840882394755072_RT @c68679_ 【专注05后得吃】女大学生的大奶的乳交，谁不爱？？@DaguidiyNone_1.mp4

"filename": "{author[name]}+{tweet_id}_{author[id]}_{content[:50]}{name}_{num}.{extension}",
"archive": "~/gallery-dl/archive-twitter2.sqlite3",

in those reposted, retweeted, etc usually have an arrow, which you can click on it and Copy Link, the link there is from original post, i think original_post_id should saved into archived along with tweet_id too ?

2. Some user may tweet or retweeted/reposted a post/tweet which are video have so big in filesize, eg 1-2GB+, how i can filtered these video, make it don't download but also logging it with {url} into respected x.com/{user[name]}

eg:
https://x.com/beiying_sex/status/1894659099620774172 big video, skipped download
logging into ./beiying_sex/skipped_download.txt
inside txt:

https://x.com/beiying_sex/status/1894659099620774172 big vdeo, etc  
https://x.com/beiying_sex/status/1894659099620774173 big vdeo, etc  
https://x.com/beiying_sex/status/1894659099620774174 big vdeo, etc  

[mikf]

Update archive-format

The default includes both {tweet_id} and retweet_id values ("{tweet_id}_{retweet_id}_{num}")
Change it to "{retweet_id|tweet_id}_{num}" to treat original Tweet and its Retweets the same.

You can filter them with --filesize-max

  --filesize-max SIZE         Do not download files larger than SIZE (e.g.
                              500k or 2.5M)

but there is no way to log them separately other than a [downloader.http][warning] File size larger than allowed maximum logging message.