cat ~/.ssh/* perhaps?

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

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.

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

All five of them.

Doesn’t it break a lot of things? Half the stuff refuses to work when some specific files have too permissive chmod.

I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they’re rich and can afford it.

Well, Fedora 40 here as well and it just doesn’t work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though.

Like trying to destroy people’s lives so they can make a few dollars.

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.

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).

Weird way to spell NixOS.

Not the same thing, I’m pretty sure something like that is in almost any language, but here it’s the official word for male masturbation, not some niche word that’s not really used much.

I know the story and you’re right, it’s pretty dumb how it’s used.

In my language, onanování is masturbating. And onan is a mild insult insinuating that someone wanks a lot.

Isn’t any math operation involving NaNs also a NaN? At least that’s my gut feeling.

I think I’ve explained quite well already, but again, many vendors, like Samsung, kill any background jobs before they have a chance to run. No matter what technology you use, it will get killed. The only thing that doesn’t get killed is an exact alarm that’s allowed to wake your phone from sleep. Everything else will get killed on Samsung. Including periodic alarms and including work manager, periodic or not.

I have no idea what the rest of your message is even talking about, I don’t have any WallpaperService, I don’t do any of what you mention, so I don’t quite understand why are you even talking about it.

In conclusion, further discussion on this topic is unnecessary because you seem to be rambling on and on about stuff that’s not at all related to why the battery optimization exception is needed. It’s not because of stock Android, but because of other vendor’s flavors of Android.

There’s a history screen, you can click the Open in HordeNG button which should fill all the parameters in a separate app where you can generate them again.

Edit: I’ll be providing the option to save all generated wallpapers in a folder of your choosing in a future update.

You don’t seem to understand that the job will be killed before it’s even triggered. Like the scheduled job will not run at all.