It probably can be patched with this: https://github.com/toleda/audio_CloverALC

You can also use a USB headset as I do.

flake8 for Python is nice, although defaults can be a bit weird...

Code Climate or Codacy are nice too. They collect tools like flake8 and run a server side report kind of like coverage.

Hmm... he mentions the Giphy thing at the beginning of the article, then never again.

The Giphy mention seemed really dangerous to me. Now I don't use Signal but I imagine it's 1) optional and 2) requests are proxified/anonimised through an intermediary (the Signal servers in this case). And why is this dangerous? Because this "don't build cool stuff on this serious app" is what makes people not use the app. It's creating boring, dull apps what stops them from becoming mainstream successes. If we are trying to make the public using secure apps because we believe in privacy, we have to make them appealing.

This is similar to the case of how nobody uses PGP because how horribly bad it is, UX-wise.

That said the rest of points he brings up are good. I just didn't like the Giphy mention, especially taking into account he didn't say anything else about it, he just brought it up.

Hi there! The Giphy thing is what set me off writing the blog post in the first place. Maybe I should've expanded a bit more on that in the article. As far as I can tell, the idea is that requests to the Giphy API gets proxied through Signal.

I don't see anything in moxie's blog post about whether this is optional. If it isn't and it's sending everything you type to the Giphy API then we have a whole new problem.

In the blogpost by moxie, there's the example of typing "Im excited", which then gets sent in multiple API requests to giphy (basically one of 'I', one of 'Im', one for 'Im+' etc.). Now, if this is an action you don't do explicitly (like pressing a button or something, to search for gifs), then it would basically send everything you type in order to continually search for gifs and then offer suggestions? It's not clear from the blogpost. I hope at least that this is not what moxie had in mind.

Giphy only occurs when you click on a button to add an attachment, and you have to click on Giphy, THEN you search for GIFs.

I promise that nobody is going to force you to use the GIF search. For a demo on how this feature works, check out the short video embedded into the blog post. [1]

I second the parent poster's question: "why is this dangerous?"

[1] https://whispersystems.org/blog/images/giphy.webm

It's not clear to me, but I assumed that that only happened if you tapped on a "search for gifs" button, which is something that can happen accidentally, but... that's unlikely.