Semperverus

You haven’t noticed the issue then. X11 tends to run everything at the lowest common denominator, and doesn’t allow per-monitor scaling.

without something breaking like its arch

I have had seven full-system failures across the last two decades using Ubuntu that could not easily be troubleshooted and fixed.

I have had exactly zero with Arch.

Take that as you will.

You got it backwards though. The root cause is not the change in work ethic. The change in work ethic is the symptom. People have to get nitpicky about breaks and such and show no loyalty entirely because companies stopped being loyal to their employees. This can be demarcated with the death of the pension.

Why does Lemmy not prevent duplicate links, at least within a time window?

I avoid all of the modern gnome apps now as a result of this.

Even Windows allows the equivalent of server side decorations…

Everything in KDE is the bare minimum for core functionality. Anything less is not functional.

My problem with Gnome is the foundation itself.

They act like they know best, and rarely listen to user feedback.

They act like Apple, and that is very bad.

Not only that, but they also act like they are the default and only desktop on Linux, and rarely if ever cooperate with other desktop groups to make things work smoothly.

They are dragged kicking and screaming into following standards, and were the biggest source of NACKs (effectively a “veto”) on the Wayland protocol and a huge reason why Wayland still isn’t complete after over a decade of design.

The gnome desktop is pretty, but it is not functional. You can make it functional by installing gobs of extensions, but those extensions don’t follow a cohesive workflow concept, and often break with updates. It’s like trying to mod Skyrim or Minecraft.

To contrast that, KDE:

• Explicitly listens to its users and has scheduled times for specifically taking in user feedback (within the scope of broad goals)

• Actively works to be interoperable with other environments

• Follows standards and pushes them forward

• Has all the functionality out of the box, and can be made pretty with extensions/assets (the inverse of Gnome).

• Functionality mostly doesnt break on updates unless it’s major (like switching to Wayland as the primary development target).

“The south shall rise (ahem) again!”

deleted by creator

Who touched the boats?

Oh yea definitely, I know this pain very well

File headers, magic bits, all sorts of stuff. Plus you can (and they do) try to load common file types, so if a PNG isn’t loading correctly, it fails the test.

“Oh sorry, looks like we couldn’t decrypt that traffic, those packets went to the burn pile”

“Hey there customer, if you want internet access on our network (the only one available in your area), you have to install our intermediary certificate on your machine!”

Monkey’s paw curls

We bought KDE a small house!

True programmers know that novice code is a rite of passage. Every programmer worth their salt looks at their own older code and cringes at it. Most people who do this for a living are more likely to give helpful pointers rather than tear you down, if anything.

If someone is being a jerk to you about your code, stop listening to them immediately and walk away or block them.

This needs to get added to the common nomenclature as the third option 😂

We use one of these at work! There are a couple of companies offering these solutions such as PaloAlto, Zscaler, etc. and they are typically of the “Next-Gen Firewall” variety (I.e. they scan the content of the packets rather than just routes and ports and such).

The way they work is basically that you establish VPN connections to their endpoints, and they scan the traffic as it passes through. Like a VPN, you get a new IP address that is shared with other customers, but there is a way to pin your original IP in the packet headers if you need.

These connections can be handled via one of a few ways:

1. Software on the workstation (best option as it allows deeper traffic routing and control, as long as your workstations are locked down)

2. IPSec tunnels configured on the building’s router service’s endpoints/datacenters

3. GRE tunnels configured on the building’s router to the service’s endpoints/datacenters

4. A physical firewall box that sits in front of your other hardware that does any of the above OR something bespoke

Note that unless you have option 4, none of these replace traditional “dumb” firewalls. If you’re still using IPv4, you still need a NAT firewall.