This is a pretty old joke. See "Church of Emacs".
aard
joined 2 years ago
Hyprland is itself a fork of wlroots, a project that the author of this post created
No, it is not. wlroots is plumbing containing parts a compositor commonly would need to implement, and many compositors - including hyprland - sit on top of that to avoid reinventing the wheel over and over again.
If you're younger than ~40 you shouldn't even know the term 'network class', unless you're really into history of computer networks. If you learned that term in some kind of school I'd question the rest of what they've been teaching as well.
If you're older than 40 you should've stopped using class based concepts at least two decades ago.
Stop sprouting that kind of bullshit.
Class based networking has been obsolete for 3 decades now - and RfC 1519 was quickly implemented, so pretty much by the mid 90s any device looking up network masks by classes could be considered some broken legacy device.
RfC 1918 - which allocates the private IP ranges - came 2.5 years after the introduction of CIDR, specifies the networks in bit notation, and only references what the equivalent networks were in class notation as reference for people who have been asleep for a few years.
The 192.168.x.x IP range doesn't allow for subnet masks greater than 255.255.255.0
This is nonsense. In that space you get a /16, and you can do with it whatever you want.
Depends on the network mask.
The problem is having a competent team to manage your infrastructure. You can do a lot with a handful of people - but you need competences spanning a lot of areas, and finding that is pretty hard.
If you can get a competent team the only advantage cloud still has is the ability to quickly scale up and down - but if there might be a need for that it'd still be better to go hybrid, most on your own hardware, and just the prepared ability to quickly bring up cloud workers if needed. The cost savings of properly doing it yourself are so huge that it still might be cheaper to just have some pre-provisioned standby hardware for that, though.
Nur Briefmarkengross, ist aber auch nicht so interessant. Ich hatte auf Planungsgrafiken gehofft.
Ah, sind keine Bilder/Grafiken drin?
Gibts nen Mirror? Die benutzen Clownflare, und das sagt mir dass ich den Artikel nicht anschauen darf weil ich boese bin.
So at least the british bit is accurate for you
WoL works as Ethernet¹ broadcast, while Wireguard routes IP, one level above that. So for the purpose of WoL the two ends of the Wireguard tunnel are in two different, not connected networks. In theory you might be able to make it work using subnet directed broadcasts - though creating some means to trigger the WoL packet on where you're terminating your Wireguard might be easier to manage.
Simple option would be just logging in via SSH to trigger it (you could script that - define a host in your SSH client config that just executes a command on connection), or something like a simple web frontend which will then trigger the WoL event.
¹ it is probably fair to assume nowadays that you're using Ethernet, and not something like Token Ring. In case you do it still works the same, just the terminology is different.