Nimrod

This comment has been haunting me a bit. I have been struggling with my port forwarding in the rest of this thread, so I decided I need to investigate alternatives. I've heard good things about Tailscale, so I started googling. The following quote is directly from the Tailscale web-page: (emphasis mine):

"WireGuard is typically configured using the wg-quick tool. To connect two devices, you install WireGuard on each device, generate keys for each device, and then write a text configuration for each device. The configuration includes information about the device (port to listen on, private IP address, private key) and information about the peer device (public key, endpoint where the peer device can be reached, private IPs associated with the peer device). It’s straightforward, particularly for a VPN. Every pair of devices requires a configuration entry, so the total number of configuration entries grows quadratically in the number of devices if they are fully connected to each other."

I find it odd that they would say this, if the Wireguard VPN works as you stated. Any tutorial or article regarding wireguard fails to make this discussion obvious, so I am now even a bit more confused. (still won't solve my port forwarding issue. So I guess I'm stuck with Tailscale anyway...

Damn. That sounds perfect. That's exactly how I was hoping it would work. But for some reason my phone won't connect... I wonder how to troubleshoot it.

Okay, I thought something seemed a bit odd about what I was doing. So for my use case, I only need to access my home network with my phone, or my laptop. So all I need is a wireguard server on my home network (currently the case, running wg-easy), and the wireguard client on my phone and laptop.

I have that happening right now. And strangely when I am connected to my home wifi I am seeing the "last handshake" information in the wireguard app. But as soon as I turn off wifi and attempt to use my cell network, that line disappears from the app.

Although the frontend webpage for wg-easy still shows my phone connected.

Lets pretend it is connected. You're saying I could simply type "192.168.3.69/login" into my phone's browser, and I would see the mineos login page as if I was on my home's wifi?? Because that would literally be perfect.

EDIT: I am dumb, and just needed to download the font to my system. Please ignore

Heyyo, me again. I have been tweaking with the Yambar for a little while now, and I thought I was getting somewhere, but now I have a different issue, and I can't seem to get the proper terms to google. Again, I think I'm missing something basic.
It's the emojis, why can't I see them? I can't see them online in people's example dotfiles, I cant see them in vim (I imagine this is intentional?) And I surely can't see them in my status bar. It's driving me crazy. I really want to have a super minimal, lightweight bar, but I don't want it cluttered with all sorts of text!

Thanks again,

Thanks for the quick reply! (and for going out of your way to help). I renamed the YAML file, and tried to run it from the terminal and it threw some errors (missing dependencies for some of the content in that example YAML. I installed those dependencies just to see if it would show up, and it did! All the icons are broken (guessing that's a font thing?) and a few of the bits/bobs aren't working properly, but it runs!

Thank you so much. I will now begin the fun task of tweaking (AKA breaking it, fixing it, and breaking it) until it fits my needs.

It's definitely not as pretty as bumblebee-status! But if it's lighter on resources, than it's a win. I guess I'll have to test that somehow...

The dock comes with a usbc integrated. So I don’t actually think there’s an option to switch it.

After some more digging, it seems to be related to the the “display link” part of the dock. There are lots of reports out there where people are complaining about display link docks introducing latency on the inputs.

So I think a new dock is going to be required.

Thanks for the reply.

It looks like libinput-gestures is similar to touchegg/touché in the sense that it only adds support for 3 or 4 finger gestures. It looks like 2 finger gestures are supposed to be supported by your DE or are app specific.

Thanks for the reply!

I would love to run gnome/wayland, but my Chromebook is about a decade old, and it was a cheapo from the start. It only has 2GB ram, so I’m running as light as I can. Unless there is a way to put wayland on xfce, I might be stuck. I appreciate the reply!

Interesting! Looks pretty slick. Might be a nice stepping stone into that world. This chromebook is so old that it could be a perfect playground for this sorta thing. I don’t have any important files/apps or anything on it that I’m afraid of damaging or being without. Thanks for the suggestion.

After some serious googling, it looks like gestures is a feature that really only exists in the "luxury" DEs. There is something called Touchegg and Touche that can add them to others, but I'm not far along enough to know if it will do what I want it to.

I just tried debian with Xfce, and it's pretty fast, but I REALLY love using gestures! It makes my tiny screen feel way bigger.

I'll be honest, I'm a bit scared of Arch, but this might be the push I need to give it a go. What's the worst that happens?

Can you add trackpad gestures to Arch?

Yeah, you don't have to remove it (I didn't when I tried this 10 years ago) but if you don't you always have to hit ctrl+l when it boots, or it could get stuck looking for ChromeOS. The hardware is so old now, I don't really care if I brick it. I'm just learning about linux by goofin.