Melmi

deleted by creator

When done correctly, the banner is actually a consent banner. It’s a legal thing, not necessarily trying to discourage criminals. It’s informing users that all use will be monitored and it implies their consent to the technology policies of the organization. It’s more for regular users than criminals.

When it’s just “unauthorized access is prohibited”, though, especially on a single-user server? Not really any point. But since this article was based on compliance guidelines that aren’t all relevant to the homelab, I can see how it got warped into the empty “you no hack” banner.

I don’t think the relevance of the TLD matters. It’s worth being aware of whether you’re using a ccTLD, especially in the case of countries like Afghanistan, but you also used .io as an example which is overwhelmingly used by non-British Indian Ocean Territory sites and is proven reliable. It’s even managed by an American company.

Then .app isn’t a part of the original TLDs, but actually a part of the new wave of modern gTLDs. And if you’re considering .app, there’s no reason not to consider the thousands of other generic TLDs out there.

Like with the ccTLDs, the only thing you have to consider is the trustworthiness of the managing org.

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.

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.

Don’t see too many leftists defending military contractors…

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

There are already AI-written books flooding the market, not to mention other forms of written misinformation.

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.

But hey, instead of killing everyone, eugenics could lead us to a beautiful stratified future, like depicted in the aspirational sci-fi utopia of Brave New World!

I agree with you, ultimately. My point is just that “good for humanity vs bad for humanity” isn’t a debate, there’s no “We want to ruin humanity” party. Most people see their own viewpoint as being best for humanity, unless they’re a psychopath or a nihilist.

There are fundamental differences in political views as well as ethical beliefs, and any attempt to boil them down to “good for humanity” vs “bad for humanity” is going to be inherently political. I think “what’s best for humanity” is a good guiding metric to determine what one finds ethical, but using it to categorize others’ political beliefs is going to be divisive at best.

In other words, it’s not comparable to the left/right axis, which may be insufficient and one-dimensional, but at least it describes something that can be somewhat objective (if controversial and ill-defined). Someone can be happy with their position on the axis. Whereas if it were good/bad, everyone would place themselves at Maximum Good, therefore it’s not really useful or comparable to the left/right paradigm.

I don’t think that “everyone is inherently equal” is a conclusion you can reach through logic. I’d argue that it’s more like an axiom, something you have to accept as true in order to build a foundation of a moral system.

This may seem like an arbitrary distinction, but I think it’s important to distinguish because some people don’t accept the axiom that “everyone is inherently equal”. Some people are simply stronger (or smarter/more “fit”) than others, they’ll argue, and it’s unjust to impose arbitrary systems of “fairness” onto them.

In fact, they may believe that it is better for humanity as a whole for those who are stronger/smarter/more fit to have positions of power over those who are not, and believe that efforts for “equality” are actually upsetting the natural way of things and thus making humanity worse off.

People who have this way of thinking largely cannot be convinced to change through pure logical argument (just as a leftist is unlikely to be swayed by the logic of a social darwinist) because their fundamental core beliefs are different, the axioms all of their logic is built on top of.

And it’s worth noting that while this system of morality is repugnant, it doesn’t inherently result in everyone killing each other like you claim. Even if you’re completely amoral, you won’t kill your neighbor because then the police will arrest you and put you on trial. Fascist governments also tend to have more punitive justice systems, to further discourage such behavior. And on the governmental side, they want to discourage random killing because they want their populace to be productive, not killing their own.

The problem with a “beneficial to humanity” axis is that I think that most people think their political beliefs, if enacted, would be beneficial to humanity. Most people aren’t the villains of their own stories.

The very act of politics is to disagree on what is best for humanity.

That’s not what’s going on here. It’s just doing what it’s been told, which is repeating the system prompt. It has nothing to do with Gab, this trick or variations of it work on pretty much any GPT deployment.

We need to be careful about anthropomorphizing AI.