Earlier quoted context omitted.
Yup, latest version. I tried clearing the cache and no change. Since I was in console, I just checked syslog and I'm getting a dbus DENIED. I'll poke at it when I have more time, but I wonder if they need to fix up their apparmor perms. Curious as to why your getting a different result though. EDIT: I'd also be curious as to your opinion of Touch in general? My opinion: I love it. I'm not a huge fan of Unity, or Ubun…
Oh sh*t I'm just remembering now a problem some people had with lock files. I thought it was fixed [0]. In that thread someone said deleting .config/com.ubuntu.telegram/ /auth.lock solved the problem with Telegram not starting [1]. So look for .lock file/s and delete it/them. I still love Debian way more than Ubuntu, but I think they're doing a great work with Touch. [0] https://bugs.launchpad.net/ubuntu/+source/qtba…
Voice Calls: Secure, Crystal-Clear, AI-Powered
291–299 of 299 posts
Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#292Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#293Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#294Earlier quoted context omitted.
There is no way riot is less buggy. Try macos to macos Sierra to Yosemite voice call. It segfaults right away. Wire is buggy but generally works. The main problem with it is that metadata is collected by default.
We're not aware of any crashes at all on Riot/Desktop (especially as it's an electron app, so crashes will be due to chromium bugs). Please can you make sure it's filed on https://github.com/vector-im/riot-web/issues ? thanks!
Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#295Earlier quoted context omitted.
I don't remember dialup latency. I only remember it having low bandwidth. I'm talking about ADSL latency in the 90s.
Latency for a 56k modem was 180ms. Latency for a voice call on the same line was _much_ smaller. AFAICT, latency from my games console television to my TV is much higher...
Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#296Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#297Earlier quoted context omitted.
Are you really serious? This is a post snowden society. > An FAQ isn't binding. Probably not, but please beware that this service is not subject to US law, but the laws of the Russian Federation. > What does their TOS say? TOS are subject to change, right? And even if it wasn't, do you really think the TOS will stop a company run by a russian nationalist[1] offering a free service with a million dollar bill will stic…
> service is not subject to US law, but the laws of the Russian Federation They are not registered in Russia, afaik. > russian nationalist[1] … [1] https://www.instagram.com/p/-MrPWGr7aL/ That's just Pavel's usual populism. He says the same things about Russia or pretty much anything.
They are writing the software in Russia (right next to the VK's door to be precise), though. Source: local Saint-Petersburg newspapers.
Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#298Earlier quoted context omitted.
We're not aware of any crashes at all on Riot/Desktop (especially as it's an electron app, so crashes will be due to chromium bugs). Please can you make sure it's filed on https://github.com/vector-im/riot-web/issues ? thanks!
It was on MacOS desktop. I'll submit an issue when I get a chance to reproduce.
Re: Voice Calls: Secure, Crystal-Clear, AI-Powered
#299Earlier quoted context omitted.
Found it [1]. tldr: First message from TelegramApp has some marketing copy ("acm winner phds") but not horrible. The TelegramApp user remains calm/careful and mostly polite in every message after that. There are only a few cases of sideways slapping and they come from HN users. Despite this the conversation between TelegramApp and HN users remain informative debate and discussion. 1. https://news.ycombinator.com/item…
Being cordial and polite on Hacker News wasn't my concern. My concern is their repeated dismissal of feedback from experienced cryptographers. Cryptographers can't seem to make sense of a lot of their design decisions in the MTProto protocol. Their response to criticism has mostly been in the form of: if you can't demonstrate a break directly, then we don't care. Given how fragile cryptography can be, this is an absu…
The Telegram designers built a protocol with anticipation of some constraints. But rather than debate the plausability of the percieved constraints, the HN-crowd just dug into whatever they already knew and threw in a lot of snark in their response to close the door.
> Their response to criticism has mostly been in the form of: if you can't demonstrate a break directly, then we don't care.
I haven't seen that. I went looking for it. If you have the patience and time please dig up a link or quote.
> That's not to throw the TLS 1.0 authors under the bus here. The weaknesses of that type of scheme were yet to be widely known. In the case of MTProto, weaknesses in their use of certain constructs are widely known, and they don't seem o care.
I did see a good bit of discussion about the feasability of some of the weakness pointed out. They responded in a way that seemed to indicate they fully understood the issue but "chose" to take the risk. I'm not sure this means "they don't care". Perhaps it does. But this is where I started to see that the rift here was really about the perception of constraints, not lack of knowledge or, in my opinion, lack of care.