Fail2ban is just another tool in your toolbox. Defense in depth, as others mentioned.
Fail2ban is primarily a tool to prevent brute force attacks, especially useful for services that don’t do their own throttling. For example I usually put ssh in fail2ban, but if Authelia’s built-in protection is good enough, then use that.
Outside ssh, anything that could be used to brute force credentials should be in fail2ban if they’re exposed: web sites with simple auth, mail, etc.
I installed CacyOS on my MSI laptop with Nvidia m2060 + igpu and Intel CPU a couple of months ago. I can play genres through Steam just fine. It performs better than it did on Windows 11.
I’ll be honest, I was amazed I had no issues getting it running. CachyOS has sone great tools to set things up and their wiki is excellent. I just followed the steps in there to set up GPU switching. I disabled secure boot, since that can get in the way of drivers loading, but they have instructions for that as well.
Wi-Fi worked out of the box. I even have a luks encrypted root.
The main issue I had was MSI specific hardware, like battery charging control, normally managed by the Dragon Center. I found an open source replacement for that.
I can’t speak to the battery performance since I always use it plugged in. It’s a few years old so it’s probably not great anyway.
Your mileage may vary. It’s probably going to be more off a struggle with hardware specific to the model of laptop rather than Nvidia.
The “what about second breakfast” meme comes to mind. Thanks for clearing that up!
My guess is that it changed from open source to a proprietary license. From Wikipedia:
Initially, Paint.NET was released under a modified version of the MIT License, with the exclusion of the installer, text, and graphics.[9] However, citing issues with the open source code being plagiarized by others that had rebranded the software as their own and bundled user content without their permission, the availability of the source code was restricted, in December 2007 Brewster announced his intent to restrict access to components of the program (including its installer, resources, and user interface).[10] In November 2009, the software was made proprietary, restricting the sale or creation of derivative works of the software.[10][11]
Yeah that’s my guess at well. Before I figured it out, I used a VPN connection into my local network (which works through hairpin NAT). I’m not a security expert, but that may be more secure than granting the permissions wholesale.
I had this happen too recently and only for certain apps. Turned out Android has a new permission that was being enforced: “Nearby devices”. Once I granted that to my browser, it could access my LAN again.
Depends on what in using it for. There is no way to fully avoid the Internet anymore. You can’t interact with businesses or government without it. So, for that, we’re stuck with it.
I work in IT so I’ll be stuck with it there. I already have no expectation of privacy at work, though.
For entertainment and engaging with communities like Lemmy, I think losing anonymity through mandatory online id would be the nail in the coffin.
I already moderate myself on social media, but I have an outlet in these communities. I would simply stop using them if I lost that.
I would guess underground networks would rise up to replace them, but I would not want to put myself at risk. I don’t trust VPNs enough for that.
I think it’s fair to want a more helpful error message, but that’s not necessarily the purpose for path. There is a real cost to every entry in your $PATH. Not as much as in the world of spinning rust, but some.
There are some completion modules for shells that will suggest misspelled or even installable packages if it can’t find the command. Those are arguably better options.
As for traditional systems, I remember a time where running arbitrary commands, even with an --help argument could be dangerous and we had to set least try ‘man command’ first.
I thought this was how unix always has been? Sbin is for root binaries. It doesn’t make sense to include a bunch of commands you don’t have permission to execute in the path. I remember this being the case back in the 90s and didn’t realize it was no longer the norm.
My guess is not just traditional developers, but anyone doing any amount of coding, like data scientists, business analysts, etc.
Especially if they’re using AI, those tools work better on Linux, or as is the case most places, wsl2 inside Windows.
I believe Windows is kept because of the Office tools. However, Windows needs 12 layers of security tools that constantly get in your way, so the path of least resistance is to just stay in your wsl2 sandbox.
The knee jerk reaction to this from enterprise IT is often to restrict access to WSL. This solves the problem, but creates disgruntled users who will continue to try and work around it.
What they should consider, in my opinion, is giving these people real Linux workstations that can be enrolled in group policies, SSO, and all that good stuff. Commercial vendors of Linux will support these use cases.
Some places roll out Macs, which work almost as well, but the hardware is more expensive. Hardware and commercial software support may be better, though, I don’t know.
I think either is a superior alternative to Windows.
The workday would be 4 hours: 2 hours at dusk, 2 hours at dawn with a quick break around midnight for running around, screaming for no reason in particular. The rest of the day would be naps.
In no particular order:
Edit: A few bonus channels that may be of interest but didn’t all fit the criteria for me:
No problem. I just spent a few minutes prompting Gemini and requested that it provided sources. I think it’s about right, because it matches what I remember (LTT had a YT privilege to replace videos in situ, where as GN did not), but the usual AI caveats apply. Sorry if that seems low-effort, but I don’t see a rule against quoting AI, and I’m not that invested in this either. (Mods: please take this down if it’s against any rules).
The response it gave me at first was a bit too long for this post so I asked it to summarize, and I’ve added the other sources it gave me to the bottom.
Here is a condensed summary of the controversy:
- The Core Issue: In August 2023, the YouTube channel Gamers Nexus (GN) published a massive 44-minute exposé criticizing Linus Tech Tips (LTT) for rushing content, which led to significant data and testing errors in their hardware reviews.
- The “VIP” Privilege: GN revealed that instead of taking down flawed videos and losing their algorithmic momentum, LTT was using a backdoor YouTube privilege—available only to massive creators through a partner manager—to silently replace the source video file on the backend after publication.
- The Proof: GN proved this by comparing the YouTube versions of LTT’s videos to versions syndicated on the Chinese platform Bilibili. Because LTT didn’t have the same VIP privilege on Bilibili, the original uncorrected videos containing glaring data errors were still live there, while the YouTube versions had been magically fixed.
- The Fallout: GN argued this was an unfair advantage that allowed LTT to prioritize quantity over quality without facing the massive financial and algorithmic penalties that regular creators face when forced to re-upload. Following the intense community backlash, LTT paused their entire production schedule to overhaul their quality control labs and promised full transparency regarding future video corrections.
Why GamersNexus Hates LinusTechTips
This video essay provides a comprehensive retrospective and breakdown of the entire Gamers Nexus and Linus > Tech Tips controversy, providing further context on the claims and the resulting fallout.
Sources:
It could definitely be me misremembering. I’ll see tonight if I can find it. Either way, it would be GN making that claim, so not exactly an independent source.
If I remember correctly, YouTube treats/treated some big time creators differently and gives them access to actually do in video edits. LTT had this access, GN did not. It’s been a long time since and I’m not on my computer right now so I don’t have a source, but that’s my memory of it.
I’m aware, but when I talk to regular people here in the Midwest, they will not be thinking heat pumps if you call them AC. I’m just trying to make sure everyone is on the same page.
Your diagram is almost right, but I think it will help to understand more of the details. It’s important to understand the difference between DNS (domain name lookup) and IP routing.
To break your diagram down more, this is what happens when any computer looks up your website:
GET / HTTP/1.1
Host: example.com
...lots more headers...
<blank line>
That’s all very simplified, of course.
As others pointed out, things may seem to work differently from the “inside”, if hairpinning is not available or enabled. This is not related to DNS, but to IP routing. The firewall doing NAT can get confused and not know what to do when an internal request goes to an external IP that it itself has. When it turns that around and routes it back to the internal network, that’s called hairpinning.
One “fix” for this, often used in enterprises, is to use so-called split DNS. All that means is that if you’re asking your internal DNS server for an internal name, it will give you the internal address (192.168.1.123 for example), but an external client would get an external IP.
TL;DR: DNS and IP routing are separate concerns and happen at different parts of the TCP/IP stack.
AC in the US aren’t (usually) heat pumps. The most common setup here is a furnace for heating (usually natural gas) plus AC, connected to the same central air unit. Heat pumps are pretty common, but not nearly as universal.
Just mentioning it because “AC” isn’t usually used to refer to heat pumps here.
Our technical debt will live forever