What you are calling “hostility” is just gnome not wanting to reinvent the wheel. Almost everyone uses systemd and it is easier to take advantage of existing features then it is to try and maintain more code.

Were you using ancient hardware or something? More modern CPUs shouldn’t have this issue.

Also middle nodes shouldn’t be getting ddosed.

Host a middle node

Do not host a entry node or a exit node. Also none of the hardware you listed is great for hosting. It could work but I would go for somethinga little more modern. Something like a i5-7500 would be great. Get a router with vlans since you probably will want to segment the network.

For networking make sure you have a solid low latency reasonable bandwidth connection. I would do gigabit fiber since that will provide a decent amount of bandwidth while having low latency.

Also you could look into running a i2p node on the same machine since they both need volunteers.

What do you mean by blocked at a protocol level? You might give it a try on a random port to see what happens.

You could also look into port knocking. It is dated but still worth while.

Did you also forward UDP port 443?

If not I would as well since it is used for QUIC which is supported and automatically turned on for Caddy.

Isn’t it Russian?

I would use Caddy or something else that is less complex to setup

Why wouldn’t you setup a firewall on the VPS?

OpenWRT also has great IPv6 support

What are you running?

If it is http based use a reverse proxy like Caddy

This is honestly out of the scope of this community

Not as of yet

KDE still has some bugs to work out

Have you tried dwl?

Support is pretty new so I think it will just take time to iron out

Wayland isn’t a piece of software. It is simply a set if standards apps use to talk to the desktop which then talks to the kernel and hardware.

Apps access resources via XDG portals. If there isn’t a portal for something it needs to be implemented at the desktop.

Back to your use case, I think you probably just need the appropriate desktop extension. Drawing on the desktop sounds like a desktop level thing.

I think it boils down to trade offs.

The major benefit to Wayland is that it has less overhead since apps talk directly to the desktop. Having desktops implement the protocols instead of relying on a external project means that the user experience is cleaner.

For smaller projects like window managers there are libraries that implement the core protocols. This allows for the minimal window managers Linux traditionally had as an option.

I won’t argue that Wayland has issues with remote desktop. The problem currently is that it has to be implemented as a custom non standardized solution by every desktop. I don’t think that there are any portals for doing session management which is unfortunate.

From a accessibility perspective I believe that has already been addressed.

I also don’t see any reason to try to “market” Linux. Windows 11 is the successor to Windows 10. It isn’t that bad compared to ever other version of Windows.

That’s a known Wayland limitation

It has been addressed with a new protocol but it takes time for it to work its way down.

Yes and no

This only applies to the gnome for now.

The benefit is that it way easier to manage since you don’t have to worry about physical hardware.

I get that it could easily be to expensive but it might not be bad with educational discounts.

Neat project but not enterprise grade