I can say I’ve never glorified suicide. When I’ve been suicidal, suicide is literally the only logical solution my brain can arrive at. It’s completely irrational in hindsight, but it makes so much sense at the time.
I don’t think I have ever not-watched something due to content warnings alone. But it has alerted me that there may be issues, so it doesn’t surprise me when it comes up.
It’s from 2015, so its probably what you are doing anyway
A technical reason is because he has been a president before
I have 3nm ~in my pants~
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)
In France, no one spoke English even though I spoke loudly and slowly
Haha, reminds me of a holiday ages ago in France.
Someone left their handbag behind or something, and my friend said “I’ll sort it out, I know French”. To be fair, he did. But when I went back to tell him where we ended up, he was speaking slowly and loudly to the poor french person.
Which reminds me of another time in France, having breakfast. I ordered “orange juice” and the waiter looked confused. So I said it again slower, and his face lit up and said “ah, jus d’orange”.
Yeh, seems not
I felt like adding something about the specific case of 180° between edges and a vertice.
Makes sense.
And I guess too many vertices means an open set of edges (ie not close, this not a shape).
I was kinda hoping for a strange edge case, like a mobius strip or Klein bottle.
I guess a mobius strip is a 2d representation of a 1d paradigm. And a klein bottle is a 3d representation of a 2d paradigm.
It would be too much to ask of a 1d representation of a ??d paradigm.
I feel my comment adds to the discussion and wants more details.
But it was too simply phrased.
I guess the details of such a question should be obvious. And if you need the details, the question doesn’t actually add the the discussion… It just seems idiotic!
I felt like there might be a really cool scenario where a vertice isn’t considered a vertice.
Like, there actually might be some case on a 2d plane “where actually” applies.
I’m fine being wrong
What if it had 3 corners and 4 edges? Or 4 corners and 3 edges?
Just wait until you learn about the etymology of triceratops
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
The chokepoints still cover kilometers or more.
It’s not like all the cables were run at the same time
CohhCarnage said something about this.
Game Devs often include requests along these lines for sponsored segments of a stream (and only the parts of the stream paid for), including talking about COVID during the high point of the COVID pandemic.
The odd part that he noted is some of the specific wording, that he attributed to mistranslation - like “feminist propaganda”.
I have no idea about the parts relating to Chinese game dev.
The benefit of the doubt in me says: this is some bad translation and culture disconnect.
The pragmatist in me says: this guides content creators. So, take such content with a pinch of salt in these regards - play the game if it actually seems decent.
I feel like the pragmatist is pretty much default these days, all content guides you to some conclusion. So do what the fuck you want.
🦜☠️ (Idk what the emoji is. I’m sure you understand) If it really rubs you the wrong way
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!
Sounds like a long-awaited race condition finally coalescing.
The boot splash screen would expect the drivers to be ready, and will hang/timeout if it isn’t ready when it tries to render the splash screen