Current state of video calls?

[fylux]

What is the current state of support for video calls?

[Vincymic]

Damn right!

[fylux]

Any update?

[Vincymic]

Any update?

Forget about video calls now, especially from grishka, since he was fired from telegram months ago.

[fylux]

@Vincymic Are you aware of any other ongoing effort to support video calls?

[grishka]

@fylux there currently isn't anyone at Telegram to maintain this library

[Vincymic]

In fact, even for calls, it's been getting to the 2.4.4 version for months now. But is there any possibility that you will return to work for telegrams and maybe make video calls?

[grishka]

But is there any possibility that you will return to work for telegrams and maybe make video calls?

Not unless Pavel changes his stance on QA at least.

[frzifus]

@grishka, which QA point do you mean?

[grishka]

@frzifus I mean doing sensible QA at all. Especially regression tests. But then for calls, there isn't a good, exhaustive way of testing them prior to release because there's an infinite amount of combinations of devices, network conditions and network configurations. You have to collect feedback and logs, analyze that and act based on that. No way around. This is nothing but a dead end.

I still haven't quite figured out what to collect and how to analyze it. After all, I'm a developer. I write code. I make a terrible QA engineer, even though I naturally do some basic testing. I make an even more terrible data scientist and an absolutely abysmal DSP engineer. There's a reason why QA and data analysis is done by separate people in just about any other company.

[Vincymic]

I know you were already developing video calls, too bad you are not continuing the development ... Il giorno mer 4 dic 2019 alle ore 17:19 Gregory K <[email protected]> ha scritto:

…

@frzifus <https://github.com/frzifus> I mean *doing sensible QA at all*. Especially regression tests. But then for calls, there isn't a good, exhaustive way of testing them prior to release because there's an infinite amount of combinations of devices, network conditions and network configurations. You have to collect feedback and logs, analyze that and act based on that. No way around. This <https://contest.com/docs/voip> is nothing but a dead end. I still haven't quite figured out what to collect and how to analyze it. After all, I'm a developer. I write code. I make a terrible QA engineer, even though I naturally do some basic testing. I make an even more terrible data scientist and an absolutely abysmal DSP engineer. There's a reason why QA and data analysis is done by separate people in just about any other company. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#93?email_source=notifications&email_token=ALEU3MSNMF43NAR35JKLMELQW7KC3A5CNFSM4H6UFAXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF5SLCA#issuecomment-561718664>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALEU3MVMJS4WPT3GDDXCUY3QW7KC3ANCNFSM4H6UFAXA> .