-
Notifications
You must be signed in to change notification settings - Fork 218
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
Enable Telegram iOS parser for UFDR and expose "extractMessages" parameter for Telegram Parser #2005
Comments
@lfcnassif, think a little bit more about this, wouldn't it make more sense to control which parser should be used (internal, external or both) per application (not globally as it is today using "phoneParsersToUse" parameter)? Another point, I personally started using "all" sometime ago, and found it the best option, because I have already seen cases where an external parser brought some recovered message and that was not shown in internal parsed chats. And the opposite. Besides that, our WhatsApp parser shows some information not presented in the external parser. |
Hi @wladimirleite! Yes, I have already thought about this and I agree a per parser configuration, into ParserConfig.xml, would be better. We could create a forth possible value for phoneParsersToUse like dynamic or perApplication and use it by default. About all results, I agree specific subcategories for internal and external would be clearer for users, especially for those that receive already processed cases. |
Great! I think we should leave this for future issue, as the current PR (#1999) already mixed a few different things. |
Closed by #1999. |
As discussed in #1999 (comment).
The text was updated successfully, but these errors were encountered: