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)

An extension is a great way for users to try features before companies implement them.
I have huge respect for games that enable modding, then - respectfully - incorporate mod QoL features into the main game. It shows they are listening to the community.

An extension is actually a great way to propose a feature, allow users to try it, and if it’s popular then you have a great case for devs to implement it.

And I wish that Reddit had spent time & money implementing RES features natively. It was basically a “Reddit but useable” feature list.

If the router/gateway/network (IE not local) firewall is blocking forwarding unknown IPv6, then it’s a compromised server connected to via IPv6 that has the ability to leverage the exploit (IE your windows client connecting to a compromised server that is actively exploiting this IPv6 CVE).

It’s not like having IPv6 enabled on a windows machine automatically makes it instantly exploitable by anyone out there.
Routers/firewalls will only forward IPv6 for established connections, so your windows machine has to connect out.

Unless you are specifically forwarding to a windows machine, at which point you are intending that windows machine to be a server.

Essentially the same as some exploit in some service you are exposing via NAT port forwarding.
Maybe a few more avenues of exploit.

Like I said. Why would a self-hoster or homelabber use windows for a public facing service?!

How many people are running public facing windows servers in their homelab/self-hosted environment?

And just because “it’s worked so far” isn’t a great reason to ignore new technology.
IPv6 is useful for public facing services. You don’t need a single proxy that covers all your http/s services.
It’s also significantly better for P2P applications, as you no longer need to rely on NAT traversal bodges or insecure uPTP type protocols.

If you are unlucky enough to be on IPv4 CGNAT but have IPv6 available, then you are no longer sharing reputation with everyone else on the same public IPv4 address. Also, IPv6 means you can get public access instead of having to rely on some RPoVPN solution.

I thought T568B at each end was standard practice these days

I’ve played it fine on steam proton on arch

Older games for specific older console hardware were specifically designed.
It leveraged specific features of that hardware.
They literally hacked the consoles they were releasing on to get their desired results.
And because it’s consumer gaming hardware/software neither backwards compatible nor forward compatibility for all the stuff the pulled were ever built in. So a game would have to target multiple platforms to actually release on multiple platforms .
It’s like why so many games don’t run Mac OSX. “Why don’t they just release windows software for free on Mac OSX?”. Because it needs to be redesigned to work on OSX, which costs money.

Everything up to, what, PS4? is probably specifically tailored to that specific hardware. Games that released on PS3 and xbox-whatever would have some core software dev team, then hardware specific developers. It would be targeted for the target hardware.
At some point, things like Unity and Unreal Engine took over, with generic code and targeted compiling. Pretty much (not quite) allowing developers to “just hit compile”, and release to multiple architectures.

Any official re-release of Nintendo games have generally been on an emulated system. Where they have developed that emulation to work with the original software.
There are some re-releases, where the game has essentially been rebuilt from the ground up, using original assets but to work with modern (and flexible) game engines.
Both of these have a lot of work, so not free. Worth $60 or whatever Nintendo charges? Meh, that’s competing with real games.

If you own (or buy) a nes/snes/N64 cart, you can rip it. There are plenty of ways.
It’s not the source, but it’s what it compiles to. And you can reverse engineer the source, then adapt it to modern game engines. There are a few open source projects that do this. Their quality varies.
Or you can build an emulator to run that software, as if it was the original hardware - an emulator.
Nintendo can skip the rip, decompile and reverse engineering steps. They likely have access to the source code, and the actual design specs for the hardware (not just what they tell developers - who then hack the hardware anyway) All of this requires a LOT of work. So a sellable product from someone like Nintendo requires a lot of investment.

Emulators are good. Any used for speedrun leaderboards on equal footing to actual hardware (ie times are similar, even if they are different categories) will be good enough that you wouldn’t know.

I take it step 3 is ??

I believe hotel rooms & their contents are specifically designed around this

The benefit of using config files is easy version management via git.
Makes it easy to rebuild from scratch and easy to rollback a change that breaks something

A lot of companies will actually have a policy about this, probably to return them

If you think coal mines are bad, wait till you see the conditions in the Alexa mines!

You missed a then/than as well

Other services will be reflected by active DNS records.

If the only DNS record points to a “Buy this domain” webpage, I think it’s fair to argue that is misuse.
Doubley so if it turns out many unrelated domains are owned by and point to the same webpage, and it’s just doing a js hostname thing to make it seem relevant to the current address

Transfering a domain from one registrar (IE reseller) to another can be a pain, but yes you can - it normally involves a fee and manual actions from the registrars.
As long as the new registrar supports the TLD. A few Geo-TLDs can only be resold/managed by some registrars.

The easiest thing to do is to point the domain at ClouDNS nameservers.
Make sure you are happy with ClouDNS (I’ve never had issues with them) etc before committing

I think the headcanon is that the shortest distance is impressive.
Either a different faster and harder route through “the kessel”. Or that 12 parsecs is the absolute minimum distance it can be done in, perfectly apexing every corner.

Nginx Proxy Manager is probably perfect for you.
Pick a domain (like mylab.home or something), set up your home network to resolve that domains IP as your docker hosts IP.
NPM will do self-signed certs. So, you will get a “warning, Https is insecure” kinda page when you visit it. You could import NPMs root cert into your OS/browser so it trusts it (or set up an “don’t warn for this domain” or something).

If you don’t want per-client config to trust it, then you need to buy a domain, use a DNS that supports letsencrypt DNS-challenge, and grab certs that way (means you don’t need a publicly accessible well-known route exposed)

It’s more than just views. It’s rewatches, binge watches, complete vs interrupted episode watches, probably even time skips.
Likely also where the view comes from, like a specific search vs general recommendations vs targeted recommendations