TL;DR;
Bot can change avatar and nickname to impersonate people, but a [bot] label is shown and the profile on click is still the bot ones.
This feature is particularly useful for bridge bots.
Bot can change avatar and nickname to impersonate people, but a [bot] label is shown and the profile on click is still the bot ones.
This feature is particularly useful for bridge bots.
I say we do a header Chat-Bot-Impersonate containing the alias name, but there is the question whether that field should be encrypted, to mitigate meta data collection (as example in mega groups).
Technically we might need a new column in the message table and thus a new database version so it would make sense to combine implementing this with bot buttons in order to only add one new db version & migration function.
For api the message object will have one more property bot-impersonate-alias and 3 methods: has_impersonate_alias and getter and setter functions for the property.
related pull-request: impersonate: allow to override sender name by r10s · Pull Request #2231 · deltachat/deltachat-core-rust · GitHub