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.

But how will you get a “universal” view of the fediverse? No single authoritative view exists.

You yourself acknowledge that this is complicated, but I honestly don’t understand what appeal a hacked together fake centralized system would have for people if they don’t care about decentralization in the first place. Any such solution is almost inevitably gonna end up being janky and hacked together just to present a façade of worse Reddit.

Lemmy’s strength is its decentralization and federation. It’s not a problem to be solved, it’s a feature that’s attractive in its own right. It doesn’t need mass appeal, it’s a niche project and probably always will be. I don’t think papering over the fundamental design of the software will make it meaningfully more attractive to the non-technically minded.

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.

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.

That’s I guess why CSEM is used, because if the images are being shared around exploitation has clearly occurred. I can see where you’re coming from though.

What I will say is that there are some weird laws around it, and there have even been cases where kids have been convicted of producing child pornography… of themselves. It’s a bizarre situation. If anything, seems like abuse of the court system at that point.

Luckily a lot of places have been patching the holes in their laws.

CSAM is supposed to be more explicit that the images are essentially crime scene photographs, and to emphasize that it is Abuse first and foremost and not merely pornography.

CP is a morally neutral term, or at least the components words themselves are. CSAM is not, and is explicitly negative.

This is certainly an interesting topic. There are men who are comfortable wearing dresses and wearing makeup and all that, just as there are women who are comfortable with cutting their hair short and wearing baggy clothes and all that. It’s also true that those people are sometimes harassed and called “eggs” by people who are ostensibly trans-friendly (especially fem-presenting guys).

But I don’t think that that is equivalent to the trans experience. I assume you’re not trans, correct me if I’m wrong, but dysphoria is a real thing that for many people is very deeply related to physical body parts, and your theory just doesn’t account for that at all. I don’t think that your average fem-presenting guy wants to take HRT to get breasts, let alone go to the extra length of getting bottom surgery and get vaginoplasty. There’s clearly something more about dysphoria than it just being a matter of what they like differing from what’s socially acceptable, unless you broaden it so wide as “liking having breasts or a vagina” or “liking having a penis”, and even that is a stretch because dysphoria is a very visceral sense of wrongness in one’s body that goes much deeper than just preferring a different body part.

Not all dysphoria is physical, either. It can relate to misgendering, or any number of societal things that aren’t necessarily related to just what we’re “allowed” to do. Frankly, unless gender is outright abolished and there are no longer distinctions between genders or even societal differentiation between sexes, I don’t see it going away. And even in a post-gender world, I imagine there would still be trans people (perhaps by another name) who experienced physical dysphoria.

Your theory also doesn’t account for trans people who present as would be socially acceptable for their assigned gender at birth, and have interests that are similar to their AGAB, but still identify as trans and even may experience dysphoria.

All in all, while I appreciate your conclusion to support trans people, I disagree with your reasoning. I don’t think that being trans is merely a result of one’s likes not being in line with societal norms. I think it goes much deeper than that, and can’t be reduced to such a simple cause.

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.