JustAnotherArchivist

I'm still working on other things, but current master (c65e36a0) should work correctly now.

You're going to need to share more information then. `snscrape twitter-tweet --scroll 1577907836356644865` with the latest master (plus some extra code on top that shouldn't affect this) returns 1577992565542080513 as...

Until there is a reproducible example that doesn't work with the current master, I'm going to consider this fixed.

@socketpair I'm not sure what you mean by "it predating RFC". `Content-Encoding` was specified in HTTP/1.1 in 1999 ([here](https://tools.ietf.org/html/rfc2616#section-14.11)), and as explained in the original issue, it is not the...

No, serving a `.tar.gz` with `Content-Type: application/x-tar` and `Content-Encoding: gzip` is perfectly valid. [Here](https://gist.github.com/JustAnotherArchivist/30b681a7450f0e90b33ed9a6ad0c33cb)'s a little minimal web server I wrote a couple months ago for testing purposes. Downloading http://127.0.0.1:8080/f.tar.gz...

I think that S3 usage is okay, actually. The browser decompresses it if the file is used in a `` tag because it needs the actual `text/css` data. This is...

This should be handled in combination with #392 most likely, i.e. return some sort of tombstone instead of a `Tweet` item. I'll try to get that done soon.

Not currently, and I forgot about the open PR for it. Note that file attachments will never happen because they're not publicly accessible without authentication. The same applies to long...

The `KeyError`s need to be handled properly in the individual cases rather than just blindly catching them all. Emitting a warning is good, but those will undoubtedly be ignored by...

Both of those are actually examples of tombstones. And they might be useless *to you*, but in general, it may be important to record that there is content that isn't...