deleted by creator
deleted by creator
deleted by creator
Using podman-compose, I usually have a section like:
volumes:
- ./local_folder:/container/folder
Specifically, I have to use either an absolute path or a relative path with “./” to prevent it from treating a directory as a volume name.
Yeah, I’m confused by this video (which is from nearly a year ago, btw). It looks like a gnome shell overview more than anything.
YouTube does exactly that if you disable your watch history. Or rather, they just disable video recommendations on your home page altogether.
Do you have a quote from the license to prove that? Louis Rossman himself said we’re free to grab the code and edit it.
The source is available on their gitlab instance, so whether it not it conforms to some specific definition of open source, the source code is readily available for anyone to view and modify.
Pretty good privacy. It’s an unexciting name for a public/private key encryption program.
I believe WhatsApp uses the same protocol (or at least the same crypto algorithms), though I’m not sure if they were involved in its development.
Good point on the metadata. Signal has the “sealed sender” thing, which (I think) helps with the metadata problem somewhat.
My practical answer: Nah, it’s probably not going to nuke your files.
My software engineer answer: Never trust us to not make a mistake. It doesn’t take much to accidentally nuke a directory.
As the other commenter mentioned, your best bet is being selective about which services you use to communicate.
Unencrypted (plain text) is the worst, since data is easy for a third party to sniff (think of it as a wiretap). For example, HTTP and SMS are unencrypted.
Encrypted is a good start, since third parties can’t sniff your traffic, but the server handling your communications can usually see everything that passes through it. For example, HTTPS is an SSL-encrypted variant of HTTP, and services like Facebook messenger are encrypted, but Facebook can still see all of your messages, since it’s stored on their servers.
End to End Encrypted (E2EE) is the golden standard. Only the endpoints (i.e. you and your friend) can see the content of your messages, and all traffic is encrypted in a way that even the server cannot view it. Signal is end to end encrypted, as are many other modern messaging platforms (WhatsApp is E2EE in theory, as is Google Meet, but we can’t verify this ourselves).
Username checks out.
Or worse… expelled
You can easily create a firearm with a short length of steel pipe and a nail. I don’t know how this will do anything. Plus people can just drive to another state.
So you’re admitting that people were eating tide pods, which makes it not, as you would say, “complete fiction”.
Though there are different flavors of iron oxide. Gun bluing is iron oxide, but so is rust. One is protective and the other is detrimental.
Agreed, for me containers are really nice for playing with new software without dirtying my host install.
“Complete fiction” is a bit of a stretch, but it was grossly exaggerated how many kids ate the danger candy.
Apparently Tide’s marketing team went through many iterations on the pods, and they intentionally made them look like enticing treats. Probably not the smartest on their part either.
I’m using droidify and couldn’t find signal in there either.
Bonus when you disable software flow control: In addition to Ctrl+r to reverse search through commands, you can search forward via Ctrl+s