Most GPUs will have fan spin & lights if only on pcie power (the pcie slot provides 75W without external connection), but then misbehave during display; I know it sounds stupid but make sure the 12V power connector on the top of the card is firmly plugged in, that connector in particular has a reputation for being unreliable.

They don’t have to care about the minority affected to be impacted; it affects readiness, which will affect them.

Laws which cause people to leave due to feeling unsafe will require others to be brought in to fill their roles, who are in-turn coming from somewhere else.

It’s not a crippling issue (for a military) by any means, but laws that fuck with the readiness of a base piss a lot of people off.

Definitely not saying any military is a font of diversity and acceptance, but their most important asset is their logistics so fucking with that will not win you a ton of friends there.

The link you posted has nothing to do with this SoC?

You’re not going to get 2.5G over wireguard on the 3588, but you are definitely going to get over 1G.

Wireguard scales well with cores, but due to the way big.LITTLE is implemented on the 3588, it could lose performance if it tries to split the workload between core complexes.

I’m sure the developers are competent, but the reason I care about the design decisions is the same reason the electric brakes on cars don’t interface with its infotainment system; the interface inherently creates opportunities for out of spec behaviour and even if the introduced risk is tiny, the consequence is so bad that it’s worth avoiding.

If you have to have an airbag be controlled by software (ideally the mechanism is physical, like a pull tab), it should be an isolated real time device with monitoring your accelerometer and triggering the airbag be it’s only jobs. If it’s also waiting to hear back from another device about whether your subscription ran out before it starts checking, the risk of failure also has to consider that triggering device.

It can be done perfectly, but it’s software so of course it has bugs.

That information changes none of my issues; if you don’t see the plethora of potential implementation bugs involved, either you don’t code professionally or you shouldn’t be.

Yes, but also from an implementation perspective: if I’m making code that might kill somebody if it fails, I want it to be as deterministic and simple as possible. Under no circumstances do I want it:

1. checking an external authentication service.
2. connected to the internet in any way.
3. have multiple services which interact over an API. Hell, even FFIs would be in the “only if I have to” bucket.

America isn’t even the most democratic country in the Americas, but that’s clearly not the point they’re making.

If the title was “…end of world democracy” you’d have a point but given how much fascistic rhetoric and policy has increased around the world since trunpism it’s fair to say many countries are following the US lead here.

deleted by creator

Most firewalls are at their safest when you first get them i.e by default they block everything coming in. As you start doing port forwarding and the like you start making the network selectively less secure; that’s when you have to pay attention.

I had an EdgeRouter X for years before I started my job. They are solid devices, and I’d definitely put them above most consumer routers.

Because they only charge for the hardware, they will eventually run into the same disincentive to provide consistent timely updates. If you do buy an Ubiquiti or similar enthusiast brand, do still keep an eye out for the CVEs that don’t get patched.

I build Linux routers for my day job. Some advice:

• your firewall should be an appliance first and foremost; you apply appropriate settings and then other than periodic updates, you should leave it TF alone. If your firewall is on a machine that you regularly modify, you will one day change your firewall settings unknowingly. Put all your other devices behind said firewall appliance. A physical device is best, since correctly forwarding everything to your firewall comes under the “will one day unknowingly modify” category.

• use open source firewall & routing software such as OpenWRT and PFSense. Any commercial router that keeps up to date and patches security vulnerabilities, you cannot afford.

The difficulty is that a VPN isn’t just a product like ProtonVPN, it’s a huge family of software and protocols.

You can block vpn.protonvpn.com, but since most operating systems come with VPN functionality out of the box, you’d have to start listening to all traffic (not just DNS lookups) and blocking ALL packets that might be VPN traffic without causing regular disruption to non-vpn traffic.

TL;DR: it’s easy to prevent unmotivated users from downloading a VPN app. It’s practically impossible to block a motivated user from using a VPN, and they’re the users you particularly care about.

What kind of idiot workplace would allow that? Perhaps if you don’t assume the people you talk to are literally brain-dead, you might understand what they’re saying.

hat’s a bad faith interpretation of “the people control the means of production”.

I want you to consider the difference between the work needed to complete a task, and the work needed to manage a workplace: for one of those tasks, only the experts in that task can meaningfully contribute to the outcome, whereas for the other, everybody who is part of the workplace has meaningful input.

I don’t know about your experience, but everywhere I’ve worked there have been people “on the ground” who get to see the inefficiencies in the logistics of their day to day jobs; in a good job a manager will listen and implement changes, but why should the workers be beholden to this middleman who doesn’t know how the job works?

I’ve also had plenty of roles where management have been “telling me where to cut”.

Sure, but that’s not necessarily a bad thing; if the Linux version is missing useful output that would be bad, but if the DX to Vulkan translation ironed out a performance regression, or the scheduler works better in this scenario, or filesystem access had issues with NTFS it could also cause performance differences in Linux favour.

Blaming the creation of a new law on anybody except the lawmakers is a pretty shit take, but blaming it on 150 year old colonialism is actually infantilistic.

Setting up the PiHole device as a DNS server & DHCP server still won’t make all traffic flow through it, you need it to be a gateway for all traffic that isn’t destined for an internal subnet.

To do that, you’ll need to set up your device as a router, with the necessary entries in iproute2 and iptables in order to keep lock out external connections without conntracks. You might be able to route to a turnkey container of some kind.

Are you trying to route your DNS queries through your VPN device or all of your traffic?

Just your DNS queries is easy, set up the VPN as the default route for the device (using netplan or iproute2), then all queries from PiHole will go via that.

All traffic is a bit harder, unless your PiHole device is the only thing between your regular devices and the internet.

They made a smart call that has probably increased the long term privacy of their users.

People were using port forwarding to host illegal shit, and governments were getting pissed off about it. Mullvad has been able to prove in court that they don’t keep logs, but that’s not a perfect deterrent; a properly motivated government, perhaps if somebody is using Mullvad to host CSAM, might attempt to legally force Mullvad to put logging in and add anti-canary clauses.

Preventing port forwarding keeps customers as consumers rather than hosters, and avoids this issue.

Not necessarily, plenty of good programs written in C89 for example.

With something that is heavily library dependent, having a more recent development stack may mean better maintained libraries but definitely not a sure thing.