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
I wanted to pose a question here to possibly help out with maintainability and targeting individual items in a better way. I've noticed that some modules target multiple files (Example: snapchatConv.py) and will extract information under a broad umbrella. I recommend we entertain the idea of splitting these files into individual files.
Example: snapchatConv.py becomes:
snapchatGeo.py
snapchatAiConv.py
snapchatCallLogs.py
snapchatConv.py
etc.
This way if someone is only looking to extract geo locations then they can target that module specifically. This also helps in case a file format changes, we know which file to begin correcting.
The text was updated successfully, but these errors were encountered:
@ramseys1990 because most parsers take so short of time to run and parse, there has been some work to try and combine parsers into singular python scripts for reducing checkboxes on the GUI. I guess it would really depend on the analysts needs and if it makes sense to split them out vs. have them combined
I wanted to pose a question here to possibly help out with maintainability and targeting individual items in a better way. I've noticed that some modules target multiple files (Example: snapchatConv.py) and will extract information under a broad umbrella. I recommend we entertain the idea of splitting these files into individual files.
Example: snapchatConv.py becomes:
snapchatGeo.py
snapchatAiConv.py
snapchatCallLogs.py
snapchatConv.py
etc.
This way if someone is only looking to extract geo locations then they can target that module specifically. This also helps in case a file format changes, we know which file to begin correcting.
The text was updated successfully, but these errors were encountered: