elliebike
Joined 6 years ago
Joined 6 years ago
Being a US-based company doesn't make this any better, just look at Facebook.
The only people who worry are people on HN. Most other people aren't aware of what's going on, or just don't care.
It's like whenever someone shares something they made with Electron, and the comments are just Electron hate.
> More details on how the encryption for server sync works would be helpful for assessing security.
Good point - I'll add something more detailed to the README shortly
For now though, it's fairly simple. Almost all of the information is first serialized with MessagePack, and then encrypted using libsodium's secretbox. This blob is what ends up being POSTed to the server
The only other information available to the server operator is
- the username/email address/hashed password of the user
- the UUID of this history item
- the history timestamp (needed for sync at the moment)
- the hash of the machine's hostname (also useful for sync)Honestly the multi-device support is a big barrier to my adoption of Signal. Currently I use Telegram across several devices, and the messages just "sync" near instantly. With Signal you see them appear one-by-one, which is painful in a large + busy group chat. Obviously Signal has technical issues to overcome that Telegram does not, but the UX issue is still there
It uses YOLOv4 to find license plates, and then opencv to blur them :)
Happy to answer questions!