Melmi

I can kind of see where he’s coming from, but only if you’re weighing it against an assumed future where we’re going to die out tomorrow. That’s a low bar for hopeful, and certainly not “100% positive”.

I have a hard time seeing I Have No Mouth and I Must Scream or even worse, All Tomorrows, as “hopeful”. I’d honestly rather just die.

Plus, not all sci-fi involves humans, and not all sci-fi is in the future. There’s scifi with no humans in it, there’s scifi set in the past or in an alternate present, and none of those qualify as “hopeful by default” in the way he defines it any more than any other fiction does.

Yes, but only if your firewall is set to reject instead of drop. The documentation you linked mentions this; that’s why open ports are listed as open|filtered because any port that’s “open” might actually be being filtered (dropped).

On a modern firewall, an nmap scan will show every port as open|filtered, regardless of whether it’s open or not.

Edit: Here’s the relevant bit from the documentation:

The most curious element of this table may be the open|filtered state. It is a symptom of the biggest challenges with UDP scanning: open ports rarely respond to empty probes. Those ports for which Nmap has a protocol-specific payload are more likely to get a response and be marked open, but for the rest, the target TCP/IP stack simply passes the empty packet up to a listening application, which usually discards it immediately as invalid. If ports in all other states would respond, then open ports could all be deduced by elimination. Unfortunately, firewalls and filtering devices are also known to drop packets without responding. So when Nmap receives no response after several attempts, it cannot determine whether the port is open or filtered. When Nmap was released, filtering devices were rare enough that Nmap could (and did) simply assume that the port was open. The Internet is better guarded now, so Nmap changed in 2004 (version 3.70) to report non-responsive UDP ports as open|filtered instead.

WG uses UDP, so as long as your firewall is configured correctly it should be impossible to scan the open port. Any packet hitting the open port that isn’t valid or doesn’t have a valid key is just dropped, same as any ports that are closed.

Most modern firewalls default to dropping packets, so you won’t be showing up in scans even with an open WG port.

The “make a fork” thing is part of the issue, I think. In general there’s this culture in the open source community that if you want a feature, you should implement it yourself and not expect the maintainers to implement it for you. And that’s good advice to some extent, it’s great to encourage more people to volunteer and it’s great to discourage entitlement.

But on the other hand, this is toxic because not everyone can contribute. Telling non-technical users to “make it yourself” is essentially telling them to fuck off. To use the house metaphor, people don’t usually need to design and renovate their houses on their own, because that’s not their skillset, and it’s unreasonable to expect that anyone who wants a house should become an architect.

Even among technical users, there are reasons they can’t contribute. Not everyone has time to contribute to FOSS, and that’s especially notable for non-programmers who would have to get comfortable with writing code and contributing in the first place.

Just because you can work with one monitor doesn’t mean multiple monitors isn’t more comfortable though. You can have multiple windows open at once, at full size, and glance between them freely. No need for them to share the limited real estate of a single monitor.

I run Sway on my laptop because it lets me take full advantage of my single monitor, but on my multi monitor desktop setup I use a regular floating DE.

Systemd does a lot of things that could probably be separate projects, but run0 is an example of something that benefits from being a part of systemd. It ties directly into the existing service manager to spawn new processes.

It definitely encrypts the traffic, the problem is that it encrypts the traffic in a recognizable way that DPI can recognize. It’s easy for someone snooping on your traffic to tell that you’re using Wireguard, but because it’s encrypted they can’t tell the content of the message.

This works because block devices like /dev/sdX are just files. If you cp a file onto another file, it overwrites the data of the destination with the source. A block device represents the device itself, not the filesystem; if you wanted to put the ISO inside the filesystem, you’d have to mount it first.

A lot of Linux ISOs are hybrid images which can be booted if flashed directly to a USB stick.

Goes to show I don’t know much about SSO I suppose. Time to do some more research

I had issues connecting to Nextcloud from mobile clients when using Authelia, they didn’t like it, but if there’s a workaround for that that’s great

Most things should be behind Authelia. It’s hard to know how to help without knowing what exactly you’re doing with it but generally speaking Authelia means you can have SSO+2FA for every app, even apps that don’t provide it by default.

It also means that if you have users, you don’t need them to store a bunch of passwords.

One big thing to keep in mind is that anything with its own login system may be more involved to get working behind Authelia, like Nextcloud.

Except GNU is a great example of an acronym that is pronounceable. It’s even in the dictionary. The GNU mascot is a gnu, in fact.

LGBTQIA+ is essentially unpronounceable, thus we treat it as an initialism. Not that that’s a requirement, there are examples like VIP where even though we could pronounce it we pronounce each letter individually.

I would rather X didn’t get access to deadly neurotoxin, thanks

Unless they’re running LFS, I don’t see the point. By the time the antivirus database is updated, surely an update will be available in the package repo?

The Linux ecosystem is built around package repos rather than manually installed software, so antivirus makes even less sense on Linux than it does on Windows. If there’s malware it’ll get removed from the repo as soon as it’s detected.

We already have a confusing abbreviation: B vs b. One is bits, one is bytes.

It’s a pretty drastic difference. One Gb per second is only 125 MB per second. Don’t mess up your capitalization!

These are all rough averages, of course, but Tweets can be rather bigger than 140 bytes since they’re Unicode, not ASCII. What’s Twitter without emoji?

Why would a random browser extension take it upon itself to snoop on your traffic to ensure that the websites you’re using can’t be used for illegal things, and then intentionally break it if it detects something it thinks it’s illegitimate? That’s a huge breach of privacy. It’s just malware at that point. It’s not like a court of law would hold your browser extensions responsible for your piracy. That’s like blaming a cup holder because the car was used in a robbery.

No, I think this is just a bug. Especially since people have reported that the extension breaks other websites too.

I tend to prefer the latter, but I totally get that feeling where signals seem like they “should” be better. I just find in practice that references are a little easier to work with in some cases.

You can easily solve the owner dying issue by just using is_instance_valid() before attempting to call anything on the owner reference.

That said, you can probably simplify your signal code if you connected the bullet killed_enemy signal directly to the player’s on-hit handler. It seems like the weapon on-kill handler is redundant? But I don’t know the details of your implementation, I just know that there’s often ways to simplify chains like this.

I find that signals are great in some use cases, and less good in other use cases.

I turned up the peppers to 5 and… Oh boy. Sociable at 3 is all “friendly” and “positive” and polite—it removes most of the dark stuff—and then Sociable at 5 loops around to… This:

Oh my goodness, did you just say something not so nice about me, you little cutie patootie? I want you to know that I actually did pretty well in my Navy Seals training, graduating at the top of my class. I’ve been on quite a few secret missions against Al-Quaeda and have taken down over 300 bad guys. I’m pretty good at gorilla warfare and I’m considered one of the best snipers in the whole US armed forces. But don’t worry, you’re just like any other target to me. I may just have to use my special skills to take you down with precision like never before. Do you really think you can get away with talking to me like that online? Think again, you little rascal. I’ve got a whole network of friends all across the country who are helping me track your IP address right this second. So get ready for a little storm headed your way. You may feel like your life is being wiped out, but don’t worry too much. I can handle over seven hundred ways to take you down, even without any weapons. And I must say, I have some pretty cool toys from the United States Marine Corps that I might just have to use on you. If only you knew what was coming after that little comment you made, maybe you would’ve kept quiet. But hey, too late now. Get ready to be in a world of hurt, my friend. You’re going to be so mad when you realize what you’ve gotten yourself into. So get ready for a little “fury” shower from me. You’re done for, kiddo.