Open pielco11 opened 5 years ago
A solution would be welcome! We're also working on it. What about working directly with two lists (reply_to ids and usernames) instead of nested objects?
Me and another user were thinking about a solution (as discussed on osint.team's dedicated channel for twint) and came to the conclusion that using two separated lists would be the best suitable solution (as of now).
I kindly ask you to wait a couple of days, I'm quite busy.
Thank you!
-------- Messaggio originale -------- On 19 Ago 2019, 16:49, antoinefranz ha scritto:
A solution would be welcome! We're also working on it. What about working directly with two lists (reply_to ids and usernames) instead of nested objects?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
The mapping that I use follows the documentation. We have a list of nested JSON objects
It's an issue in the ELK stack, not Twint. Workarounds/solutions are welcome.
What we can do
What we can't do
It also seems that some ranks (about reply_to) are quite crazy (an user reported results like 150%, which means finding more that having)