Github messages for voidlinux
 help / color / mirror / Atom feed
From: L3Nya <L3Nya@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: not working voice chats in tdesktop
Date: Fri, 22 Jan 2021 02:52:06 +0100	[thread overview]
Message-ID: <20210122015206.jPqM-i7XVbdbMyYQa0K0NYzlHG8nVvMGB_1gSo4E8yo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28001@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

New comment by L3Nya on void-packages repository

https://github.com/void-linux/void-packages/issues/28001#issuecomment-764806938

Comment:
> > @Johnnynator
> > > Which Client did the other end use?
> > > I only ever tested this between telegram-desktop clients (both OpenSSL <-> LibreSSL and LibreSSL <-> LibreSSL) and it did work fine.
> > 
> > 
> > I think you confused group voice calls with private. private calls works fine, but voice calls don't work at all.
> 
> You didn't mention that it is about group chats in a singe word. I didn't even think about that they exist.

Voice calls is not voice chats and telegram uses this term to talk about group calls. Ok, no matter. They do exist and they don't work. 

  parent reply	other threads:[~2021-01-22  1:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  6:17 [ISSUE] " L3Nya
2021-01-19 21:21 ` ericonr
2021-01-19 22:40 ` Johnnynator
2021-01-20 13:50 ` L3Nya
2021-01-20 13:51 ` L3Nya
2021-01-20 16:14 ` Johnnynator
2021-01-21 17:20 ` L3Nya
2021-01-22  1:52 ` L3Nya [this message]
2021-03-06 13:08 ` Johnnynator
2021-03-06 13:08 ` [ISSUE] [CLOSED] " Johnnynator
2021-03-06 13:08 ` Johnnynator

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210122015206.jPqM-i7XVbdbMyYQa0K0NYzlHG8nVvMGB_1gSo4E8yo@z \
    --to=l3nya@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).