

I’ll also add that if you do enable SSH and are stupid enough to expose port 22, then at least make sure you have key-based authentication instead of password authentication and keep your keys safe.
“Life forms. You precious little lifeforms. You tiny little lifeforms. Where are you?”
- Lt. Cmdr Data, Star Trek: Generations


I’ll also add that if you do enable SSH and are stupid enough to expose port 22, then at least make sure you have key-based authentication instead of password authentication and keep your keys safe.


I could never get Gnome Network Displays to work, but it’s worth a shot.
Looks like that site is dead and has being an AI slop domain squat.


I personally never want to touch anything Adobe ever again, but for my father’s and grandfather’s use cases, they still need it, so if it ends up working well, maybe it’ll finally allow them to use Linux.
For reference, sharing your local IP address is a little like saying “I’m in room 223” (local IP address) and not saying what building (network) you’re in. Someone can’t walk into 223 in a different building and get to the same room you’re in.
Honestly, even if someone knew what network you were on, a local IP address wouldn’t be that useful because even if they successfully got on your network, as long as you have a properly-configured firewall and no vulnerable network-exposed services on your system, they can’t really do anything.
Honestly, while it’s still not a bright idea to tempt fate like that, even sharing your public IP isn’t that bad for the same reasons if it’s a competent home user; the worst that can happen on a properly-configured network is that someone tries and fails to exploit vulnerabilities that aren’t there and MAYBE drum up your internet bill. Also, for most ISPs, your public IP changes pretty often anyway, usually something like every few days to a week, due to changing DHCP leases.
Uploading a gz source archive to a Git repository is absolutely cursed. Still, looks like a cool project.