@JasonCarswell dropped a request for me in chat.

x0, would you mind making a post about your Chromebook + server setup, please? Like I'm 5. Include size and specs and apps (ie. touchscreen, RAM, drive, uses, customizations, what not to use for, what not to expect, what to avoid, etc.). Or find the link if you already did? I'm debating that or a tablet (that I can also use as a camera monitor) with wireless keyboard. Whether tablet or chromebook, I'd tether it to my phone.

Because the Chromebook part is the more unique aspect, most of this post will be about that. For my full setup this is a rooted Chromebook. But I'll try to cover some of the other parts too.

The first and most important step to living in the lite-life, for those who wish to dream, is 90% about picking the right Chromebook. If you want to go light then you have to go light. Because we'll later use this as a thin client to a server or desktop, the performance of the Chromebook is a 0% factor. This is a mobile monitor, and more likely in my use case, a mobile terminal.

Here are the considerations we need when picking one. It needs to have an Intel processor instead of an ARM processor if we are going to put Linux on it (most Linuxs). An 11" screen will make this smaller and more mobile. A 14" screen is where we have the most options and so ironically we can often match the weight at that screen size just from the larger selection. Last, we need the model to be listed on Mr. Chromebook's rooting guide. You can find the list of supported devices and associated methods here

I know for mine the listed method is "CR50 (SuzyQ, battery)". The SuzyQ refers to a SuzyQuable which is a specially adapted cable meant to signal to the device to accept modifications to the firmware. For my case I ended up not needing it. The board name for mine is LICK, which ultimately defines the methods needed and how that process goes. I think it may be the case that any listed with CR50 can avoid use of a SuzyQuable as long as you leave a copy of the original OS on the device. For me, once I got the firmware hacked and a BIOS that will boot more locations, I just put in a microSD card to act as my Linux disk. The BIOS replacement will also allow you to boot from a Live USB to do the installation. Because it is now half rooted (the CR50 method), when booting you first start in a ChromeOS boot menu, press ctrl-l and a number to swap to the other bios, and then select your linux disk. If you want to be exactly like me you would use Artix Linux with OpenRC for the init system and XFCE for the desktop environment.

This exact chromebook comes in different screen sizes but for whatever reason the 15.6" one was the only one I could find with an Intel processor. https://a.co/d/09AUC0By

That one is 3.48 pounds. You can definately go lighter. And if it is listed on Mr. Chromebook it can be hacked. But mine ended up being pretty easy. You just want to read the full guide on that site. It saves time in the end to do a full RTFM in this case. RTFM is tech speak for (read the fucking manual). And AI can be handy here as well. The nice thing about the CR50 method is it is non-destructive. You aren't going to mess something up if you try it.

That being said, hacking it is not the most critical part. That's just an extra step to get more control. So it can be good to buy one that is known to be hackable if you can help it. But you can use a plain Chromebook as a thin client.

Now this is primarily meant to be used as a thin client for servers. So terminal based and web based applications primarily. But VNC can be used when that is needed.

This is the extension you'd mostly be relying on in a vanilla chromebook. With that you can access a real operating system on a VPS. Or you can access your desktop at home via port forwarding, or a reverse ssh tunnel to a VPS, or with a personal VPN like Wireguard or Tailscale. Add some hotspotting with a phone and you are now fully mobile. You are now more mobile than 90% of people with a laptop. And you have more real hardware on the other end of a keyboard. You can now run "local" AI models or any other heavy thing your want via your desktop. When I'm at home I still access my desktop this way even if it's in the same room as me.

Personally I use Wireguard now. This isn't like a VPN you buy. This is your own VPN you set up. AI can tell you how to get it set up. Some people use Tailscale for the same thing. Tailscale is a wrapper to Wireguard that is supposed to make the setup easier. I've never touched it, and I didn't find Wireguard to be hard anyway.

But if you want to go the port forwarding route instead you can. You just get into the admin interface of your router and set it up. Depending on your service that is going to be at 192.168.0.1 or 10.0.0.1 in your browser. You'll just want to pick a non-standard port for your ssh if doing that (really anytime ssh is involved that is more optimal). Just use random.org to pick a random port number below 65000. Once you pick a port, you can adjust the ssh port on your desktop at /etc/ssh/sshd_config.

I did mention reverse ssh tunnels. I wouldn't suggest it. It's hacky. It's a last resort. You can google it if you need it.

This is a broad overview and a few hints. To really do it ultimately you'll need to consult some google, because there are a few different routes you can go with it. And everyone will end up with different hurdles to google past.

I'd suggest just buying the Chromebook and then start integrating some of these things slowly.