So you end up with a complete new archive, but with less downloading.
-
-
Replying to @mwichary
yep, that would make periodic backups much faster, and avoid loss age from link rot :-)
2 replies 0 retweets 0 likes -
Replying to @fanf
Sounds good. Will try to add soon. Given the file naming scheme I used, it feels it should be easy to build.
1 reply 0 retweets 0 likes -
Let me just check that it handles multi-image tweets... Yep!
1 reply 0 retweets 0 likes -
I should probably register a pro-forma complaint about hard-coding the ANSI clear-to-EOL escape sequence.
1 reply 0 retweets 0 likes -
More portable method: generate output as a string, pad with 79 spaces, truncate to 79 chars, then write.
1 reply 0 retweets 0 likes -
Replying to @jefposk
Two issues with that, I think a) assumes your terminal has 80 characters, and b) the cursor will be in a weird place.
1 reply 0 retweets 0 likes -
Replying to @mwichary
Assumes the terminal has at least 80 chars, which should be safe. And if you want to get elaborate you could BS over the spaces.
1 reply 0 retweets 0 likes -
Replying to @jefposk
Oh, it’ll break over 80 then? Sorry, can’t say I’m an expert on ANSI, but this doesn’t seem like an improvement?
1 reply 0 retweets 0 likes -
Replying to @mwichary
Hardcoding ANSI sequences works on any ANSI terminal/emulator, any size. It's just bad practice. But probably works everywhere.
1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.