They probably do. But even if not, it can be used for communication with insects and other animals.

Honestly, you already have the image locally if you’ve pulled it.

I guess not everyone treats their PC as an ephemeral storage, huh? I don’t trust anything that’s available only locally to survive.

Yes, remember that one as well, but this is a literal sound, not only a “plants communicate stress in some way” (if I remember the previous research correctly).

Eh… What? It’s an interesting article. The screaming is in quotation marks. So as far as I’m concerned, the title is fine.

That’s actually mentioned as one possible use case further down the article!

cat ~/.ssh/* perhaps?

On Printables you can filter by license.

I use ssh regularly, I just use a different key for each server. And thus I don’t use the default name (id_rsa) because it doesn’t make sense.

Here you go!

~ $ cat ~/.ssh/id_rsa
cat: /data/data/com.termux/files/home/.ssh/id_rsa: No such file or directory
~ $ cat ~/.ssh/id_ed25519
cat: /data/data/com.termux/files/home/.ssh/id_ed25519: No such file or directory

Few years ago or so some billionaire said that no one should die a billionaire and donated his money. Or something like that, I don’t remember the details clearly. Though I’m not sure it’s what you’re after as he’s done so when really old.

1. For all the mentioned cases, if your firewall blocks incoming packets by default, no one can access it, no matter what is the source of the port being open.

2. You don’t configure it on the docker level, at least if you care about outside connections. If you mean from your local computer to a docker container, by default you cannot connect, unless you expose the port to the system. If you mean from other docker containers, just create your own separate network to run the container in and even docker containers cannot access the ports.

3. I usually use netstat -tulpn, it lists all ports, not only docker, but docker is included. docker ps should also show all exposed ports and their mappings.

In general, all docker containers run on some internal docker network. Either the default or a custom one. The network’s ports don’t interfere with your own, that’s why you can have 20 nginx servers running in a docker container on the same port. When you bind a port in docker, you basically create a bridge from the docker network to your PC’s local network. So now anything that can connect to your PC can also connect to the service. And if you allow connection to the port from outside the network, it will work as well. Note that port forwarding on your router must be set up.

So in conclusion, to actually make a service running in docker visible to the public internet, you need to do quite a few steps!

• bind a port to your local host
• have your local firewall allow connection to the port
• have your router set up to forward connections on the port to your machine

On Linux, local firewall is usually disabled by default, but the other two steps require you to actively change the default config. And you mention that all incoming traffic is dropped using UFW, so all three parts should be covered.

So glad it isn’t us millennials ruining everything nowadays. Your turn, gen Z!

I remember not sleeping for 2 or 3 days after watching it when I was… 7? 8? Something like that.

It’s wild to me, here in the EU only companies that you have some business with (or you have given them the permission in other ways) can message you.

So apart from scams, no company, for-profit or otherwise, will message you, unless you have business with them.

I sometimes watch videos by one US expat who lives in my country and this was one of the “reverse cultural shocks” (aka stuff that surprised her when she visited the US after living here for a few years) she mentioned and it was the first time I learned something like this happens in the US.

I’m using Proton mail, I like their focus on privacy and e2e (only with other Proton users, though).

Well, then I’m nolingual, I guess.

Nah, php over python any day. Equally easy to start, equally fucked up core, but the ecosystem around it is so much saner and easier. And I’d argue it’s even easier for beginners.

Unless you need something that only has python bindings, I’d never choose python.

We use .lh, short for localhost. For local network services I use service discovery and .local. And for internal stuff we just use a subdomain of our domain.

They didn’t lose. You’re probably talking about Nazi Germany. Yes, that country lost. Doesn’t mean Nazis in Germany magically disappeared. Doesn’t mean Nazis anywhere else disappeared. Your dad never won over Nazis, just one particular Nazi country.

I personally only turn it off when someone’s visiting over night and the noise disturbs them, otherwise I just leave it on nonstop. Mainly because it would annoy me to try to open whatever and find out I have to turn on the server first. I don’t have a UPS and never even thought about getting one (for the server, I’m thinking of getting one for my 3D printer).