Encrypted, as it's used with messengers, means E2E encrypted. Anyone who is calling Telegram 'encrypted by default' while technically correct, is being very, very misleading.
Well, calling it "unencrypted" is equally misleading
... and technically wrong as well.
In a somewhat technical community we should strive to communicate correctly and not invent new meanings for well-defined terms.
By all means come up with a new nasty sounding term, but don't lie and excuse it with "it means something else now", that is borderline childish/sleazy salesman-ish.
> Well, calling it "unencrypted" is equally misleading
Encryption implies it protects message content from third parties. Show me someone who agrees its bad if the third party is some random guy from ISP, but it's good if its some random guy from Telegram LLC.
Telegram is effectively unencrypted, because the messages are by default readable by someone else, like is the case if there was no encryption at all.
Third parties are not just your average script kiddie capturing packets at your internet cafe, third parties are also everyone who hacks Telegram server, every intelligence agency that hacks Telegram servers, and a possible parent company that buys Telegram.
I think there's a pretty big difference between "your messages can be intercepted and arbitrarily modified by anybody who has any access to any router or server between one of your devices and the Telegram server" and "your message security is the security of the Telegram servers only".
> Show me someone who agrees its bad if the third party is some random [girl] from ISP, but it's good if its some random [girl] from [service operator].
To be clear, DoH refers to DNS over HTTPS (also thanks to u/wizzwizz4 for clarifying that in a sibling comment) and wasn't at all meant to be a sound. Not sure if that came across wrong, now that I read it again I see that it might have.
