Monsterovich

Lanemu P2P VPN - an implementation of a decentralized virtual private network operating on a peer-to-peer basis, in which participants connect directly to one another rather than through a central server. Network participants can find each other through BitTorrent trackers or BitTorrent DHT, or through other network participants (peer exchange). Starting with version 0.14, RUDP support has been added, and peers can connect to each other without port forwarding (NAT traversal via hole punching). The application is a free and open-source alternative to Hamachi VPN; it is written in Java (with some components in C) and distributed under the GNU LGPL 3.0 license. It runs on Windows, GNU/Linux, FreeBSD, and Mac OS.

Changelog for 0.14.1:

- Fixed issues in the RUDP library: memory leaks when using shutdownHook, deadlocks, handling of corrupted UDP packets, and many other issues that were identified during testing.

- Added the display of the connection protocol to the peer list.

- Added an experimental build that compiles a .jar file into an executable using native-image in GraalVM. For now, this is for the headless version of the application on Linux x86_64. To avoid running Lanemu as root, you also need to do `sudo setcap cap_net_admin=eip Lanemu-headless`.

- Updated dependencies.

TearFree was only recently added to modesetting. But there's no release yet. In any case, the fact that it hasn't been in Xorg for so long looks like sabotage.

Since GTK4, GTK is a dead framework. I don't even have it on my system. GNOME killed GTK, so I'm waiting for the community to finally fork GTK3 and make a compatibility layer for GTK2, because there are a lot of GTK2 applications.

> This is kind of the problem, though. X11's model of 'everything can access everything' is obviously bad,

It's neither bad nor good. That's the default. All the "no security" cries are nothing more than whining (not a single person has been harmed in 20 years). If security features were so necessary, people would have been implementing them a long time ago - https://www.x.org/releases/X11R7.6/doc/xorg-docs/specs/Xserv....

> but when wayland went with a more restrictive model they didn't provide a means for legitimate functionality like this

Furthermore, this model is embedded in the core architecture and cannot be fixed except by crutches.

This looks like sabotage from the Wayland-centric mesa developers who didn't add TearFree to the core xorg modesetting driver because the older one had this feature. Use V-Sync in the compositor.

> In reality, Wayland works great for most Linux desktop users (on the mainstream distros) and no-one is funding X because no-one wants to.

Actually, because it's ready and it works. And yes, most distributions use Xorg by default and all attempts to switch to Wayland fail, ex. Ubuntu. (maybe GNOME is an exception, but it's probably the only DE where Wayland somehow works).

> It's janky as hell, screen tearing is everywhere unless you're running extremely particular driver + hardware + X configurations

There you go again with your mythical screen tearing that I've never seen.

You should learn to enable V-Sync in your compositor or in xorg.conf (the option is called Tearfree in Mesa).

> the screen locker doesn't even engage if you have a context menu open

For some reason, it worked for me.

sleep 5 && xflock4

then I open the context menu and wait 5 seconds. After 5 seconds the screen locks successfully.

> vital things like compositing are hacked on in janky ways

Bullshit. Compositing in Xorg is done properly and it's not mandatory in cases where it's not needed. Besides, the compositor in Xorg can be changed to any other compositor regardless of the window manager (exceptions - compiz).

> For some people, Wayland isn't there yet.

Essentially all people who use their computer for more than just a Google Chrome launcher.

> Are distro developers supposed to ignore that and keep pushing X, despite it being the worse option for most of their users?

The only thing that works in all use-cases is Xorg.

> Isn't it enough to provide X as an option for people who need something Wayland doesn't do yet?

Thank you, but no.

> Plus, Wayland is getting better, X isn't.

No, it's not improving. It's adding more crutches, we haven't seen such crutches even in Xorg.

> Here's a screenshot of me sharing a window in firefox:

You forgot to mention that it doesn't work without portals and Pipewire dependency, and portals have to be implemented individually for each DE.

> I use global hotkeys to switch between keyboard layouts, see the screenshot. Works fine.

Because the KDE developers went to a lot of effort to make it work. That doesn't mean it will work well in other DEs and that is Wayland's problem.