I know a lot of FOH engineer that can design an array hang, dial in delays, do crazy sub array stuff, manage a Dante network, AND make a band sound good.
They are quite comfortable as FOH, systems, monitors RF or even just a patch monkey.

Just because a lot of people that call themselves sound engineers can’t do that, doesn’t mean nobody is a sound engineer.
I get that engineer is a protected term, but the majority of those apply to disciplines that have been around for centuries not 70 decades.

Original sound engineer would make their own kit. So they were probably electrical engineers, applying their knowledge to sound.

Be an audio tech. That’s cool. I’d rather be on a gig with someone I consider a sound engineer tho.

That’s fascinating! You should update the Wiki on trebuchets.

https://wikipedia.org/wiki/Trebuchet

Clearly someone has pulled a Scots Language Wiki and has been writing bullshit on that article for years

And there have been 5 people banned from GitHub due to racist and homophobic slurs, which violates Godot CoC and GH ToS.
I don’t think these users were providing valid criticism. Never mind the fact that GH issues are not really the place to complain about some twitter drama.

https://beehaw.org/comment/3969324

Racist and sexist slurs, most likely.
You know, edgy 14 year old kids on xbox

Which applies to EU countries.
Not sure if apple is going to do separate builds for separate regions

If you want remote access to your home services behind a cgnat, the best way is with a VPS. This gives you a static public IP that your services connect to, and that you can connect to when out and about.

If you don’t want the traffic decrypted on the VPS, then tunnel the VPN back to your homelab.
As the VPN already is encrypted, there is no point in re-encrypting it between the vps and homelab.

Rathole https://github.com/rapiz1/rathole is one of the easiest I have found for this.
Or you can do things with ssh tunnels.

For VPN, wireguard is very good

It’s from 2015, so its probably what you are doing anyway

Thankfully containers are open source.
Everything is “docker this” and “docker that”. But podman is viable, and there are other container systems.
The container format is so ubiquitous it’s FOSS. I mean, it’s kubernetes.

I would say the more regular expiration and renewal of an LE cert is better.
It’s an ongoing check instead of an annual check.

At the homelab scale, proxmox is great.
Create a VM, install docker and use docker compose for various services.
Create additional VMs when you feel the need. You might never feel the need, and that’s fine. Or you might want a VM per service for isolation purposes.
Have proxmox take regular snapshots of the VMs.
Every now and then, copy those backups onto an external USB harddrive.
Take snapshots before, during and after tinkering so you have checkpoints to restore to. Copy the latest snapshot onto an external USB drive once you are happy with the tinkering.

Create a private git repository (on GitHub or whatever), and use it to store your docker-compose files, related config files, and little readmes describing how to get that compose file to work.

Proxmox solves a lot of headaches. Docker solves a lot of headaches. Both are widely used, so plenty of examples and documentation about them.

That’s all you really need to do.
At some point, you will run into an issue or limitation. Then you have to solve for that problem, update your VMs, compose files, config files, readmes and git repo.
Until you hit those limitations, what’s the point in over engineering it? It’s just going to over complicate things. I’m guilty of this.

Automating any of the above will become apparent when tinkering stops being fun.

The best thing to do to learn all these services is to comb the documentation, read GitHub issues, browse the source a bit.

Bitwarden is cheap enough, and I trust them as a company enough that I have no interest in self hosting vaultwarden.

However, all these hoops you have had to jump through are excellent learning experiences that are a benefit to apply to more of your self hosted setup.

Reverse proxies are the backbone of hosting and services these days.
Learning how to inspect docker containers, source code, config files and documentation to find where critical files are stored is extremely useful.
Learning how to set up more useful/granular backups beyond a basic VM snapshot in proxmox can be applied to any install anywhere.

The most annoying thing about a lot of these is that tutorials are “minimal viable setup” sorta things.
Like “now you have it setup, make sure you tune it for production” and it just ends.
And finding other tutorials that talk about the next step, to get things production ready, often reference out dated versions, or have different core setups so doesn’t quite apply.

I understand your frustrations.

I’ve been meaning to play with rust, and I’ve always enjoyed tinkering with various MCUs… Although I’m not very strong with firmware/embedded programming.

Do you think programming an ESP32 is a good project for learning rust?
Any suggested place to start? (Tutorials, YouTube Vida etc)

Blowing up as in catastrophically failing.
Not blowing up as in to the moon.

Nano is useful because it is everywhere.
There are better editors, but being familiar with nano and it’s shortcuts means you can edit files pretty much anywhere.
Same with knowing the basics of vim (like being able to edit, exit and save)

Oh, this looks great!
I’ve been struggling between customize and helm. Neither seem to make k8s easier to work with.

I have to try cuelang now. Something sensible without significant whitespace that confuses editors, variables without templating.
I’ll have to see how it holds up with my projects

Buying extra sets of bed linen is easiest the best money I have spent.

When I was younger, I’d get away with changing less often and rushing the full bed linen through in a day.
Now, I can take a few days to do that laundry, and have fresh bedding whenever I want.
At least 2 sets of bed linen is a fantastic investment

Oh yeh, they’re fucked.
A straight rip of the '94 (or whenever) java date library spec without any changes since then.

If your windows computer makes an outbound connection to a server that is actively exploiting this, then yes: you will suffer.

But having a windows computer that is chilling behind a network firewall that is only forwarding established ipv6 traffic (like 99.9999% of default routers/firewalls), then you are extremely extremely ultra unlucky to be hit by this (or, you are such a high value target that it’s likely government level exploits). Or, you are an idiot visiting dogdy websites or running dodgy software.

Once a device on a local network has been successfully exploited for the RCE to actually gain useful code execution, then yes: the rest of your network is likely compromised.
Classic security in layers. Isolatation/layering of risky devices (that’s why my homelab is on a different vlan than my home network).
And even if you don’t realise your windows desktop has been exploited (I really doubt that this is a clean exploit, you would probably notice a few BSOD before they figure out how to backdoor), it then has to actually exploit your servers.
Even if they turn your desktop into a botnet node, that will very quickly be cleaned out by windows defender.
And I doubt that any attacker will have time to actually turn this into a useful and widespread exploit, except in targeting high value targets (which none of us here are. Any nation state equivalent of the US DoD isn’t lurking on Lemmy).

It comes back to: why are you running windows as a server?

ETA:
The possibility that high value targets are exposing windows servers on IPv6 via public addresses is what makes this CVE so high.
Sensible people and sensible companies will be using Linux.
Sensible people and sensible companies will be very closely monitoring what’s going on with windows servers exposed by ipv6.
This isn’t an “ipv6 exploit”. This is a windows exploit. Of which there have been MANY!

Ah, I think it’s like “keep track of 7 items, the 8th might push something else out” ( https://en.m.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two ).

So like mind-map-complexity.
Like, when you are trying to figure out some bullshit OOP inheritance, you are 9 levels deep and have no idea what the original problem was, but you feel like you have made a connection to the solution, but now you have to backtrack everything (or figure out where your last edit was) to try and figure out what that connection actually means and what you have to do now

I haven’t tried this yet, but I’m excited for it’s potential.
Having a bunch of RES-like enhancements with toggles, and the ability for users to (manually & anonymously, via a button) “submit” their preferences to a central database would be an awesome way to gather Lemmy user feedback on various upcoming features.
This would give fantastic options for Lemmy developers to implement, popularity of features, and easy ways for users to choose what they want (as long as any permanent Lemmy implementations come with an enable/disable toggle)