In one of my older posts, I talked about using Shadowsocks in conjunction with Wireguard to bypass firewall. That works, sure, but when considering what people usually use Wireguard for, the redundency of this setup becomes apparent. People use Wireguard to visit geo-blocked websites! (or hide IPs in general) I mean yes, Wireguard can do this.
Finally. After what must’ve been a month, GNOME 43 is now in Arch Linux’s official repository. A bit unusual that both Fedora and Ubuntu has newer GNOME than the bleeding-edge Arch, but I’m sure Arch devs have their reasons. Yea, it has already been a month since GNOME 43 came out, and here I am ranting writing a review on it.
Update Sep 25 ‘22: Binary build of patched linux-zen kernel is now available! See here for more info. After previously wiping out Windows 10 on my laptop (an ASUS Flip 13 OLED UX363ea), I felt better. Not because it finally became the Linux master race(tm), but rather that it stopped causing third degree burns every time it booted up.
Recently I got a new laptop. It is an ASUS Zenbook flip model with i7-1165G7 (4 core…). I thought about getting an AMD model, but if there is anything good about Intel these days, it is their Linux support for mobile CPU. Right after I got this laptop, I did the thing any person would do: Putting Arch Linux on it.
Is your Wireguard server not as fast as you thought? Does it suffer from constant disconnects and packet drops? Sometimes, it is simply caused by Wireguard using UDP instead of TCP. In some public networks, the ISP loves interrupting UDP traffic. With a technique called Quality of Service, they deliberately slow down UDP traffic to avoid network congestion in busy hours.