So… you’re afraid of the command that does the thing you’re trying to do?

If you have multiple users writing to a directory, you should be relying on groups, permissions, and sgid and not care who the owner is.

I’m surprised no one’s mentioned the security implications. Mounting with nosuid and nodev options can undermine rootkit or privileged escalation exploits.

deleted by creator

deleted by creator

Flatpak is itself a file manager.

That duplicate of your folder in /run is due to filesystem links (or more likely a fuse mount, I’ve never actually looked into how flatpak works). But either way, they aren’t copies of the data.

Free tier is super limited and super easy to accidentally break out of. I had a single file in S3, but because my logging settings were wrong, I broke the free tier with junk logs.

The t2 micro ec2 instances are fine, but you need to be very careful about their storage and network egress.

Best use I’ve had for AWS that has managed to stay within the free limits has been Lambda. Managed to convert a couple self hosted discord bots to a few Lambda functions, works great. Plugging it into CloudFormation and tying up CI/CD with CodePipeline and the like were overkill but good learning exp.

I don’t think there’s any ECS free tier, but you can fit a private container repository in the free S3 limits as well.

Don’t “declutter” manually. Use your package manager.

You’re going to want to look up things like symlinks, hard links, fuse filesystems, and bind mounts among other concepts. Your “whole directory” and other duplicates are artifacts of how the filesystem and process management works, and simply running fsearch or find over them is going to be confusing if you don’t know what you’re looking at.

One Unix concept that carries over to Linux is that everything is a file. Your shared memory space, process data, device driver interfaces, etc, all of it is accessible somewhere in the same virtual filesystem tree as the actual files.

Because of this, there’s very little reason to have the whole filesystem indexed from root. If you’re worried about space usage, you want to work with packages through the package manager. If you’re worried about system integrity, you’ll want package validators.

The above is accurate, and can be considered accurate for any directory below or at well.

Per /run, it’s also mounted in memory, so trying to “declutter” it won’t get you anywhere and things will return on reboot.

Man, I use my switch all the time. But I love little metroidvania and smaller indie and single player games. Any time I see something interesting on steam, I’ll buy it on the switch if available.

I’ve also been using it to replay older stuff. The first red dead, the Arkham trilogy, currently going through Nier: Automata again.

Function/class/variables are bricks, you stack those bricks together and you are a programmer.

I just hired a team to work on a bunch of Power platform stuff, and this “low/no-code” SaaS platform paradigm has made the mentality almost literal.

deleted by creator

I actually want to learn enough code to contribute, but there’s this gap between “how to code” and “how to participate in a modern software project”.

Like, I’ve created plenty of little things. Discord bots, automation scripts, plenty of sysadmin stuff for work, etc. But like, I clone a git repo cause there’s a home assistant bug I’d like to fix for example, and I’m immediately lost on where to start.

Everything they’re willing to tell you they have on you.

Check the link I posted above, or you can look at the 802.15.4 wiki for an overview.

https://en.m.wikipedia.org/wiki/IEEE_802.15.4, scroll to the security section.

No apology needed, one thing about security is that paranoia is good. One problem with security is that paranoia leads to assumptions and misinformation, rather than understanding.

Symmetric key encryption is much faster than asymmetric, and can use much larger keys with less compute penalty. So we use acPU intensive asymmetric TLS handshakes to safely exchange the keys, and then switch to the faster method for the data.

So when ZigBee use AES 128, you can be reasonably sure the data packets are safe. The next question to ask is “do they exchange their keys safely?”

Which in this case would be “no” if you just leave the ZigBee controller in pairing mode all the time. However, you only allow pairing when you want it, and only pair with devices you explicitly allow. Unauthorized devices never get your network key.

That’s fair, since it’s possible these chips have some backdoored bootloader or something, I’ve never personally analyzed them with an electron microscope, but the architecture and wire traces are published, so you could start a chip fabrication plant and roll your own silicon.

The actual running code on them is usually GitHub hosted though, or you can write it yourself and just import the libraries you need, again usually from GitHub or the platform specific repositories.

If you’re worried about Chinese chips in your open source though, I have some real bad news for you.

If you’re using FOSS specifically as a control against Chinese spying, and not analyzing the commit logs of every package you download, I have more bad news for you.

Your Https connections are also symmetric, so that’s a silly thing to dislike.

The handshake and key exchange are asymmetric, and used to establish a symmetric session key.

ZigBee encryption is fine for the use case, because you’re only adding devices you know are being added. You inherently trust that your physical ZigBee device is the device it claims to be.

There’s potentially an opportunity to hijack the key exchange between devices at network join, but you’d have to approve the listening device to your network in the first place.

https://development.libelium.com/zigbee-networking-guide/security-and-data-encryption

There is an entire ecosystem of open SoC devices, code, platforms, development boards, etc. One of the most popular is the ESP32/8266 boards, which is a pretty good place to start.