It would. But it’s a good option when you have computationally heavy tasks and communication is relatively light.

Once configured, Tor Hidden Services also just work (you may need to use some fresh bridges in certain countries if ISPs block Tor there though). You don’t have to trust any specific third party in this case.

If your CPU isn’t ancient, it’s mostly about memory speed. VRAM is very fast, DDR5 RAM is reasonably fast, swap is slow even on a modern SSD.

8x7B is mixtral, yeah.

Mostly via terminal, yeah. It’s convenient when you’re used to it - I am.

Let’s see, my inference speed now is:

• ~60-65 tok/s for a 8B model in Q_5_K/Q6_K (entirely in VRAM);
• ~36 tok/s for a 14B model in Q6_K (entirely in VRAM);
• ~4.5 tok/s for a 35B model in Q5_K_M (16/41 layers in VRAM);
• ~12.5 tok/s for a 8x7B model in Q4_K_M (18/33 layers in VRAM);
• ~4.5 tok/s for a 70B model in Q2_K (44/81 layers in VRAM);
• ~2.5 tok/s for a 70B model in Q3_K_L (28/81 layers in VRAM).

As of quality, I try to avoid quantisation below Q5 or at least Q4. I also don’t see any point in using Q8/f16/f32 - the difference with Q6 is minimal. Other than that, it really depends on the model - for instance, llama-3 8B is smarter than many older 30B+ models.

Have been using llama.cpp, whisper.cpp, Stable Diffusion for a long while (most often the first one). My “hub” is a collection of bash scripts and a ssh server running.

I typically use LLMs for translation, interactive technical troubleshooting, advice on obscure topics, sometimes coding, sometimes mathematics (though local models are mostly terrible for this), sometimes just talking. Also music generation with ChatMusician.

I use the hardware I already have - a 16GB AMD card (using ROCm) and some DDR5 RAM. ROCm might be tricky to set up for various libraries and inference engines, but then it just works. I don’t rent hardware - don’t want any data to leave my machine.

My use isn’t intensive enough to warrant measuring energy costs.

Maybe not as important, but I still like having a fancy futuristic animation when a device is locked and idle.

I hope Wayland gets screensaver support at some point.

Well, that’s exactly what I did. My point was rather that there’s no single consistent way to do this across different DEs with different Wayland implementations - and that’s supposedly considered a feature from Wayland design’s perspective.

Here’s a KDE-specific script with kdotool (Wayland always needs custom solutions for simple things):

#!/bin/bash
WIN="$(kdotool search --class org.kde.konsole | head -1)"
if [[ "$WIN" != "" ]]; then 
    kdotool windowactivate "$WIN"
else 
    konsole
fi

If you don’t find such a setting, you can try writing a script that checks if it’s running already (e.g. with pgrep), activates the window if found (no idea how to do that in Wayland properly) and launches a new instance otherwise. Then use a custom .desktop launcher for Konsole.

Disabling root login and password auth, using a non-standard port and updating regularly works for me for this exact use case.

I have a MediaWiki instance on my laptop (I’ve found the features of all other wikis/mindmaps/knowledge databases decisively insufficient after having a taste of MW templates, Semantic MediaWiki and Scribunto).

Also some smaller things like pihole-standalone, Jellyfin and dictd.