user28282912

Run XFCE and use Thunar. : )

import requests

theUrl = r’https://threatbutt.com/map/’

response = requests.get(theUrl)

print(response.text)

Nokia 2780 is not bad. It runs KaiOS, supports tethering and 4G cell data. As long as you stick to the script on how you use the device it will have minimal privacy issues IMHO. If that is still not enough you can skip phones altogether and get a 4G dongle for your favorite Linux laptop/tablet and just use a softphone + voip service.

SSH and freeRDP are pretty reliable.

Smart phones are a bad idea. A simple, dumb phone to make calls, texts and occasionally tether your laptop, vehicle tablet to for data access are all you really need. Even the dumb phone should have physical switches for the radios and a battery that can be removed without any tools.

We need improved Linux support for power management on ARM platforms. In general Linux on ARM has been good for a long time now. (ex RaspberryPi, Gentoo, Ubuntu)

Where things aren’t so great is the choice in OEMs putting out ARM parts like Broadcom, Qualcomm and Apple. All of whom aren’t exactly open source champions. In a less imperfect world we’d have something like RISC-V with great power management and linux support available in mobile computing SKUs/TDPs.

Thanks for noticing that. I certainly missed the ‘=1’ bit.

Debian testing, then upgrade it as they make major releases. I have yet to have a single Debian upgrade go wrong on Desktop or Server. It is basically magic.

Assuming that:

• your Linux Laptop uses wlan0 for its wireless connection and your home network uses 192.168.1.x for IP space.

On the Linux laptop:

• as root or with sudo – enable IP forwarding and load the change with sysctl -p.

sudo sysctl net.ipv4.ip_forward=1 ## updated edit thanks to folks pointing out my typo.
sudo sysctl -p

• if you have ufw installed and running – setup a NAT masquerading rule for any hosts forwarding IPv4 traffic to it.
  add this line to /etc/ufw/before.rules file right after the “*nat” line

:POSTROUTING ACCEPT [0:0]

-A POSTROUTING -s 192.168.1.1/24 -o wlan0 -j MASQUERADE

On the mac:

• set your IP address manually to be on the same LAN as the Linux laptop, but for the gateway address… point that at the IP for the Linux Laptop.

Check your passkeys. You might still have one still in the OS credential manager.

Prosody XMPP + Pidgin/(Monal|Xabber) has always worked for me. It is not hard to setup or manage, has E2E encryption too.

Ignore the idiot posting about this RAT.

If you want to secure your Linux system, use ClamAV, a local firewall like UFW or even opensnitch for a start. Also use your head when adding apps to your system. Stick to the official repos from your distro. Things like Arch’s AUR, random PPAs in Ubuntu and any random github project are going to be much riskier by their very nature so act accordingly.

If you need to risky stuff, do it a VM and network that guest into a private internal network that can only exit over a companion PFSense VM that is dual homed to the regular LAN and the private internal network. Take a snapshot of the risky guest before you use it in a session and when you are done, roll back to your clean snapshot.

Store your passwords in something like Keepass(strong master password!) and then use syncthing to push copies of the database to at least one other box locally or in the cloud if you really have to.

Some upgrades require human input like when core service config files upgrades are offered. (ex. would like to update /etc/samba/smb.conf with the maintainer’s version or keep your own?)

In my experience this can occasionally cause background apt processes to hang while they wait for your answer to that kind of question. There is a debconf trick you can try. debian_frontend=noninteractive. You can create your own cronjob, as root, that runs a script with this export command, apt update, then apt dist-upgrade -y.

If your machine is a Tuxedo laptop, this thread might interest you. Seems as though this user was hitting thermal limits and their laptop would freeze/poweroff to keep from dying.

Run your workload in a guest VM and limit its resources to whatever you desire. You can also consider c-groups if you already know which processes are causing all of the trouble.

Ignoring what users want is the tradition in GNOME and yeah ofcourse Fedora is gonna do whatever RedHat/IBM tells them to do including push AI-slop.

I would look at these things first.

1. Try another DE, something like XFCE. See if the problem persists. Sometimes swapping compositors or display managers can help too.
2. Run memtest. Failing memory can definitely cause lock-ups.
3. Lastly I’d look at graphics drivers. If you’re running Nvidia, switch from nouveau to the proprietary driver or vice-versa and see if that helps.

This project has never been more relevant in light of the recent acceleration of enshitification over at Microslop. Might be time to donate a few bucks.

It should but you can test that assumption by trying to ping any other device on the non-guest wifi. (and try ping in the other direction)

Do not, under any circumstances, conduct any private business on it. What isn’t being logged by Microsoft and shared with your employer, advertisers, various governments will be screenshot’d every n seconds. Additionally, I highly suggest, if you haven’t already, to setup a separate VLAN for this device if you ever bring it home and connect it to your home network. Defender absolutely does passive sniffing and active network scanning now. It will also be collecting and logging visible SSIDs as well. Enjoy!