-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whatsapp Parser - Android New - 'raw_string_jid' like @lid #2270
Comments
Hi @gfd2020, into how many cases have you observed this? Anyone else noticed this and can confirm those chats are always empty? |
Hi @lfcnassif . Goog point. PS: IPED is ignoring @broadcast, but I did a test to not ignore it and a chat is created with several photo posts, for example. I imagine it's the status changes posted.. |
Yes, there is an open ticket to handle status changes: #616 I think they should be displayed in a different way, not as a chat, like Cellebrite software does. And, not sure, but as far as I remember, those profile picture changes appear like they were received photos, right? When actually they were broadcasted from the owner to all other contacts. |
Yes. Sometimes it appears as received and other times as sent... |
Hi @lfcnassif . I tested 8 new chats. Some may come empty but many come with system messages below. Maybe it's better to leave it as is: Messages and calls are end-to-end encrypted. No one outside of this chat, not even WhatsApp, can read or listen to them. Tap to learn more. 000000000000000 (000000000000000@lid) changed to 55XX99999999. You blocked this contact. Tap to unblock. You unblocked this contact. |
New Android databases are full of chats ending with @lid. These are shown as empty conversations when processing through iped.
Perhaps these @LIDS could be ignored so as not to pollute the listing of chats.
It appears that these @LIDS are unique (hidden) user identifiers.
Source:
pedroslopez/whatsapp-web.js#2330
PS: This case I'm looking at has around 2,300 chats processed at IPED, 674 are @lid.
The text was updated successfully, but these errors were encountered: