We need a lightweight desktop software solution to connect to an external communication protocol.
Focus areas:
Zero bloat: strictly one-on-one text exchange, no public directory or multi-channel complexity.
Direct authentication flow via standard credentials/OTP.
Fast, typed IPC between the UI and native background processes.
Soft-delete visual markers: retain the original body text with a clear "message deleted" tombstone.
Prior experience with real-time sockets or native API libraries is strongly preferred. PM with relevant work examples and your TG handle for fast follow-up.
Why not just say you want a custom Telegram client built, instead of dressing it up as a generic external communication protocol integration. The credential and OTP flow, the one on one only scope, the mention of a TG handle for follow up, all of that points pretty clearly to Telegram's MTProto rather than some unnamed protocol.
If that's the case, the part that deserves a direct question is the soft delete requirement. Asking for the original message body to be retained locally with just a tombstone shown when the other person deletes their message is not a normal client feature, it is a way to keep reading messages after someone has deleted them, without their knowledge ➜ what is the actual use case here? As described, this is functionally a surveillance feature, it lets one party silently defeat the other party's expectation that a deleted message is gone, and that is worth naming plainly rather than dancing around.
Or did I get all this wrong? In which case clearer requirements would help.
