JustAnotherArchivist
JustAnotherArchivist
Yes, a new `Item` dataclass in the Twitter module for this would be the way to go. I'd call it `Tombstone`, and it should have at least an attribute `text:...
@vladkens Are you still working on or interested in implementing the tombstone handling? If not, I'll look into it this weekend.
Obsoleted by 6a6b02cb and 3d6cd63a. As mentioned before, `KeyError`s should be reported individually as bugs so they can be fixed properly.
Yeah, this is probably only helpful to people who have worked with `strftime` or an equivalent function before. But I guess it's as close as it gets to a common...
Does that API endpoint return something different than the 'top' search? If so, is this functionality available anywhere on Twitter's web interface without authentication?
What's your snscrape version, and do you have some examples of profiles that trigger this?
This is closely related to #433. The specific problematic tweet is 979340820968026112, and that's age-restricted. Why that's sometimes `TweetTombstone` and sometimes `TweetUnavailable` is beyond me.
What's your snscrape version, and do you have some examples of profiles that trigger this?
Tweet 1567449406835724290 specifically causes the crash. It quotes 1567414879723610112, which by itself does not cause any issues, but when retrieved through the former, 1567276089122213889 (quoted in 1567414879723610112) is referenced under...
@ronnypollak `result`? I see the same error as above on that one, `KeyError: 'rest_id'`. 1586039847688572928 is the tweet causing the crash.