bro 3 hours wtf

for now

i didn’t know you could use emacs for security analysis

it’s certainly interesting, but what do you do when someone actually breaks in?

that’s an incredibly slow cpu (I’ve literally never heard of a 600MHz cpu in anything this century).

You’re free to try, but I wouldn’t expect it to run any web browser (including obsidian, because that’s electron). I’d recommend using it to experiment with extremely lightweight software like Alpine Linux with some lightweight WM

it gets very technical very quickly on Linux, but have a read here: https://linrunner.de/tlp/introduction.html

what terminal emulator are you using?

there’s a bunch of Reddit mirrors, no one likes them

you can buy used hard drives for pretty reasonable amounts of money

Matrix?

very nice!

Sounds stressful asf, you should try take a break and relax (e.g. turn off all computers in the house for a few days). The rushed decisions you make now might not be the best

In terms of suggestions, I’d recommend:

• Isolating untrustworthy network devices (e.g. web3 shit and your roommate’s pc) in VLANs
• Running untrustworthy code in containers or vms
• Getting a proper router (openwrt one maybe?) and managing it yourself, don’t let your roommate touch it
• Setting up firewalls on your pc (restrict ports to the ones you actually need)

This would involve learning more about networking, Wikipedia and the arch wiki has pretty good information on it.

I think for cjk typing you can use fcitx5 with the input method engine corresponding to your language. have a look here

EDUT: actually the arch wiki has a good writeup on this

oh shit they have multi communities

https://voyager.lemmy.ml/multi_communities

why would they name it voyager, it’s so confusing wtf

it is what it is. I’ve personally just decided that performance is worth sacrificing for a better OS, but it’s understandable if that’s not worth it for you

or only write instructions for Linux if you’re really evil

I’d try:

• running solaar from the terminals so you get the output log
• checking what you have in /etc/udev/rules.d

dxvk usually uses way more vram tho

you’ll become comfortable with the cli, it’s seriously not hard.

all you need to know to start is:

• ls (list files)
• cd (change directory)
• nano (edit text file)

then you can branch out from there