zwekihoyy

telegram isn't even e2ee, why would anyone recommend it.

i would like to add on to this, do not bring your own device, just simply keep school/work and personal stuff entirely separate. simple as that.

all work and schools that allow you to use a personal device that I'm aware of will require you to have whatever software for surveillance that they have on provisioned devices, you'll likely end up messing up and leaking something private, and it just takes up storage space.

it's the organization's device, they can put whatever nonsense they want on it, just be sure that you only ever use accounts from them on the device. never a personal account of any kind.

the lack of privacy with cards is primarily what is giving you security with them. trust factors will always exist somewhere in the chain.

to be more to the point of the post, though, you can agree with a person's singular opinion without supporting or agreeing with that person.

typically I wouldn't recommend just moving file paths for packages, especially if you aren't sure what you're doing. assuming all you did was chsh -s, I wouldn't worry about it.

I found the "best of both worlds" setup is xfs for root fs and then btrfs for /home.

I shuddered at the mere thought of vim. why would you do that to yourself

this is how you burn potential for future relationships

tbh I'm pretty sure the issue I ran into was user error anyways, but once I finally figured out what I was doing, I decided to land on xfs for root and btrfs for home for the following reasons.

1. xfs is supposedly more performant and common in data centers
2. having a separate partition mounted at /home allows for os reinstalls or even distro swaps while retaining my home directory contents (assuming my user is the same)
3. most of the contents I want backed up are held in /home. I don't want snapshots of my entire system laying around
4. I like being extra

I've had some wild issues that I can't even begin to explain with btrfs. I landed on using xfs for / partition and btrfs on /home

true, --substitute false will compile all dependencies, down to the compiler itself, but a simple (/s)

nix-build "  " [package] --check

will compile just the chosen package, skipping dependencies, and compare it against the cached binary in the repo to ensure they're equivalent.

I could have gotten that nix-build command slightly off as I'm typing this from memory. I am also saying most of this in jest as they aren't really solutions to anything mentioned above and I moreso find them interesting features.

but with a simple --substitute false you can make it compile on install. I love nix

you're ignoring the very large elephant in the room known as "maintenance". r&d is only the first hurdle.