[green-eclipse]

I think you're looking at this all wrong. If Telegram did this officially with Google, would they have had to craft this klunky workaround for breaking up RPC strings and randomizing the user agent? I don't think so.

Also the Google Pay analogy seems off. Telegram backdooring free access to Google Translate is not at all the same as Google partnering with 4 banks for transaction processing. One is totally unofficial, the other is an actual partnership.

[arihant]

Yes the string split is a very odd. I agree with you there. Very confused that Google can't catch this. It's adding to the same string it should look same in the heap anyway? Simple college plagiarism programs like MOSS will catch this.

For Google Pay, what Google is doing is actually not legal. Government wanted each third party (non bank) app to be restricted to 25%. Google will get in trouble when government actually starts cracking down (and when they get close to the 25% mark). We don't know how government is looking at them, because they're under threshold anyway. The legal way for GPay to handle over 25% of total transactions is to register at least as a Payment Bank.