

Oh yeah definitely, that’s a major problem that’s specifically created by this policy.


Oh yeah definitely, that’s a major problem that’s specifically created by this policy.


It prevents you from jobs like airline pilots, the rationale being that placing someone potentially suicidal in control of a plane full of people isn’t a good idea. The rationale doesn’t really make total sense but you can see why they’d think that way.
My latest project runs on a VM I use vscode’s ssh editing feature on. I edit the only copy of the file in existence (I have made no backup and there is no version control) and then I restart the systems service.
So what if I mess it up? Big deal. The discord bot goes down for a few minutes and I fix it.
Same goes for the machine configs. Ideally the machines are stable, the critical ones get backups, and if they aren’t stable then I suppose the best way to fix it would be in prod ( my VMs run debian, they’re stable).


Thankfully you posted it online for everyone to see!
Please don’t platform hateful imagery for internet points.


Pretty much all monitoring solutions on the market track cert expiration nowadays. I get an alert when any of my certs have <5 days left

It might also be because you’re an admin, and thus have local moderator powers everywhere.

You would ban bob’s post from being shown on your instance’s copy of the federated community.
This happened recently, where a prolific user on !noncredibledefence was instance banned on blahaj.zone. if you visited !noncredibledefence@shit.just.works from blahaj.zone, none of his posts would be shown, but they were otherwise visible on other instances. I suspect in the case you’re talking about, it would only apply to the community on question and bob’s posts in other communities would be unaffected.


It’s a misnomer. It’s actually a slur filter


Also consider that Roquefort-sur-Soulzon, of cheese fame, has 528 inhabitants.


It’s also completely unthreatened by public boycott. People who make the choice to continue using AWS do so because of vendor lock-in, and they either can’t leave or are in a position where they agree with daddy bezos because they have money


Sorry I 'ever saw this, that sucks.
Turns out mine was broken too. I put the CPU in my gaming rig and it worked fine, so I bought a new motherboard and the problem is gone.


Syslog is considerable overkill for home lab monitoring.


SNMP does what you want. You just need a good monitoring solution that’s not as involved as Prometheus+grafana (I feel you, I’ve been there)
I really enjoy PRTG, but it’s way too expensive for a home lab, still throwing it out there if you feel like you have money to burn.
I hear good word about libreNMS, it’s next on my list when my PRTG licence runs out.
Be warned that monitoring is ultimately a fickle thing; what you don’t write in yaml config for grafana, you get to dig through obscure SNMP libs to find out (though I find that’s easier for me, ymmv) for other tools.
I recommend against: nagios (I like it but if you hate Prometheus it’s definitely not for you), checkmk (throw checkmk into the sun please it just fucking sucks), cacti (NO!), solar winds (why?)
if you feel like you want to become a datacenter admin: zabbix scales very very well, both in performance and ease of admin against hundreds of servers, but it’s overkill for a home lab, and it can get you lost in configs for hours.

This resizing is done by pictrs at runtime, when you request the image. Unless the external image host also uses pictrs, you can’t do this with any other host, no.


It’s a gigabyte ab350m gaming-3 rev 1.0. it boots grub fine but then crashes right after displaying “loading Linux 6.x”, CPU led flashes then dram led stays on, I have to turn it off with the PSU switch.
Either it’s a rev 1.0 bug which is a thing on those motherboards, or the CPU (or igpu) is defective.
https://superuser.com/questions/1854228/proxmox-doesnt-boot-after-cpu-change
I’m currently waiting on support from both the seller and gigabyte but I don’t expect anything out of it, though I’m still yet to test it in a different motherboard.


Oh wow congrats, I’m currently in the struggle of stretching an ab350m to accept a 4600G and failing.
You’re right, you should hit PCIe 3 speeds and it’s weird, but the fact that the drives swap speeds depending on how they’re plugged in points to either drivers or the chipset.


I’m not fully familiar with the overheads associated with all things going on on a chipset, but it’s not unreasonable to think that this workload, plus whatever the chipset has to do (hardware management tasks mostly), as well as the CPU’s other tasks on similar interfaces that might saturate the IO die/controller, would influence this.
B350 isn’t a very fast chipset to begin with, and I’m willing to bet the CPU in such a motherboard isn’t exactly current-gen either. Are you sure you’re even running at PCIe 3.0 speeds too? There are 2.0 only CPUs available for AM4.


It might be that the data to both disks saturates a common link before the second disk reaches full iops capability, and thus the driver then writes at full speed on one disk and at half speed on the other, for twice as long.


Apart from the mouse thing (which I’m skeptical about), cloudflare also correlates your traffic with other sites hosted on cloudflare. Bots typically don’t visit many sites, click around there, find another one, etc, whereas humans will have visited other sites, will be slower at clicking the button, will have left comments on some sites.
Also musk did claim the election was stolen in his crash out a few months ago