Data encryption at rest - Protect the database with passphrase encryption
Secure RAM wiper - Securely shred sensitive data from device memory
Automatic lock - Lock the app automatically under certain conditions
Multi-device support -- Link multiple devices, including Android tablets, to a single account
Block unknown contacts - Block messages and calls from unknown senders for security and anti-spam
Contact deletion - Allows you to delete contacts and stop sharing your profile
Disappearing call history - Clear call notifications together with expiring messages
Debug logs are optional - Android logging can be disabled
Custom backup scheduling - Choose between a daily or weekly interval and the number of backups to retain
SOCKS proxy and Tor support - Tunnel app network traffic via proxy and Orbot
Besides that, you will find all the features of Signal plus some minor tweaks and improvements. As with Signal, SMS is not supported.
Molly is open-source just like Signal. But Signal uses Google's proprietary software to provide some key features.
To support a 100% free and auditable app, Molly comes in two flavors: one with proprietary blobs like Signal and one without. They are called Molly and Molly-FOSS, respectively.
As I understand, when you update npm packages, if a package/version is specified in package-lock.json, it will not get updated past that version. But running those pip commands you mentioned is only going to affect what version gets installed initially. From what I can tell, nothing about those commands is stopping pip from eventually updating a package past what you had specified in the requirements.txt that you installed from.
If you want to just do it automatically through the settings or whatever, sure. But you can supposedly call up customer service, make up an excuse like the ads are inappropriate for your kid, and they will remove ads for no charge.
We are now offering the MS Linux Introductory CD at a special introductory price of only $249.99 (plus shipping and handling), if you order before it ships.
Basically it goes a little like this... I bounce out a song as a WAV, and then convert it to a 320 MP3 using iTunes. iTunes compresses very well (imo), and so if you compare that WAV with that 320, they will sound practically identical. I then take that 320 and Convert it to 128 in iTunes. The sound is STILL practically identical. (Because it is a good 128.) There may be a little rolloff around 8-10k (super high end) but it's more of a "sound change" than a "degradation". This conception that 128's are drastically inferior to 320's mostly comes from 1. people reading bullshit on the internet, & 2. people downloading BAD 128's!!!! Seriously. Not every WAV is equal, not every 320 is equal. I could take something at 92 KBPS and rebounce it as a WAV. does that make it a lossless audio file? Fuck no. Who knows how many times it' been downconverted/upconverted etc. Just because you downloaded a rip on /xtrill and its a 128 and it sounds bad doesn't mean 128's sound bad. Just because the apple I bought was rotten doesn't mean all apples taste awful. Basically if I listen to a song and it sounds good, I will play it. People knock me for playing 128's and I'm just like... If I can't tell the difference, then neither can you. And the bit about playing it on big systems and it sounding like shit is also a load of crap. TL;DR: If it sounds good on good headphones, play it. (That said, anything below 128 and you will notice audio quality deteriorate VERY quickly.)
SatyrSack @ SatyrSack @lemmy.one Posts 14Comments 563Joined 2 yr. ago
I used to agree until I started using gyro aim