You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Sorry for the delay in responding, and feel free to ask any questions.
is there a way to only have the text/html tweets and not the application/json ones within the html file?
It’s partially possible.
If the tweet still exists, I can return the text, which is saved in the CSV file. If it doesn’t exist but is returned in JSON format, I can retrieve the text. Currently, the library doesn’t do this due to the API’s rate limiting, which restricts the number of requests and can lead to requests being blocked. The function exists but isn’t used.
If the return is in HTML, it’s not possible, as I would need to write a scraper for each Twitter/X UI type.
To address this, I’m considering an extra module that extracts the text from the iframe using AI… I could work on something like that; it’s a bit labor-intensive but sounds interesting.
Is there an option to only have the "Click to load the iframe from Archived Tweet" menu, and not the three others?
The idea with the other three is that if the original option no longer exists (as links may have changed since they were saved), it would be possible to access them another way. This is common with images saved in 2011 (the tweet link doesn’t exist, but the image link does).
To streamline the view, I could implement an option to return only iframes with original links and another option to return everything.
Forgive me since I'm very new at this type of thing.
I've read through all the links and documents but I'm still lost
I'm using the command line tool
I've managed to download the tweets I need from an account and everything is working fine. I have two questions and I hope they're not too dumb haha.
I like the html file that is downloaded that contains the tweets. But the questions are about what's within the file
Thanks for helping!
The text was updated successfully, but these errors were encountered: