
E82 Custom Headlights
Considering I had a brand new Merc CLA before this. I love this car more.

Considering I had a brand new Merc CLA before this. I love this car more.
I host a number of services behind my residential YF connection, but because this is expanding, I'm considering moving to their business package, mainly for an additional static ip block.
I'm wondering, has anyone had experience moving from a residential package to business, and how did it go, and was it to a residential address?
Just given I'm also a fully remote worker, not having an internet connection is a pretty big deal for me, and I don't wanna be left without one for days.
We've recently been asked to identify and map all open-source software across our estate as part of "Mythos preparedness". I'm happy to support the exercise, but I find the framing a little odd.
The messaging seems to imply that Mythos is particularly effective at identifying vulnerabilities in open-source software. My question is: why are we focusing on Mythos specifically? AI-assisted vulnerability discovery isn't unique to Mythos. Claude, GPT, Gemini, Llama, Mistral and others are all capable of analysing code and identifying vulnerable patterns. It feels like we are just buying into this hype over Mythos and management are advertising for them.
More importantly, why is the discussion centred on open source? Vulnerabilities are not an open-source problem. Proprietary software, vendor products, operating systems, databases and SaaS platforms can all contain vulnerabilities. This feels less like an open-source vs closed-source debate and more like a software supply-chain problem!
To me, the real question is whether, if a vulnerability is identified anywhere in our dependency chain by an AI model, researcher or vendor, we know where it's used, who owns it, whether we're affected, and how quickly we can deploy a fix once one becomes available.
Am I missing something, or are others seeing a similar focus on open-source software specifically rather than vulnerability management as a whole? And also specific focus on Mythos like Anthropic litterally invented Skynet.
Can anyone tell me if when upgrading from the G4 Pro Doorbell to the G6 Pro Entry, I can keep and re-use my existing G4 PoE chime? Anyone know if they are compatible. I didn't want to assume.
Hey, quick question about the current recruitment event (Gamma Vanguard) in Star Trek Online.
When I went to create my character, I had that “Play Now” button at the top with the Vanguard promo, but I initially clicked the one at the bottom with the flashing icon next to the Jem’Hadar symbol. That seemed to give me a regular gamma recruit, so I backed out and made another using the top option instead.
Just want to sanity check, is that the correct one for getting the free Vanguard ship reward? And how exactly do you unlock it?
I’ve played through a bit and just got to the point where I received the temporal device / transponder thing, but I’m not sure what I actually need to complete to earn the ship.
Am I on the right track or did I mess this up somewhere?
Running into a weird issue with a proxmox VM using NVIDIA vGPU (tested on both a Tesla P4 and A5000).
The NVIDIA VGX display adapter (comes with the NVIDIA GRID drviers) doesn’t expose 5120x1440 (my client monitor is a Samsung G9), only things like 4096x2160 and 5120x2880. I can add 5120x1440 using CRU or EDID overrides and it works fine at first. Moonlight streams properly, game works (Dead Space 3 is the reason I’m avoiding other virtual displays for info it will crash out on the usual MTT/SudoMaker virt display drivers).
Problem is after a few reboots, Windows eventually comes up in 5120x1440 at the login screen and then Sunshine/Moonlight breaks. I just get a black screen with a white border or “host didn’t send any video”. After that happens, nothing fixes it. Reinstalling drivers, forcing another previously working resolution, removing virtual displays, reinstalling Sunshine etc doesn’t help. Only way back is restoring a snapshot from before I added the resolution.
Weird part is VNC still works perfectly at 5120x1440, so it doesn’t seem like the resolution itself is invalid. It’s just the streaming stack that stops capturing/sending video.
Feels like something about the custom EDID or the display coming up in 32:9 at boot is breaking NVENC or capture.
Has anyone seen Sunshine/Moonlight fail like this with custom resolutions or VGX? I know this works fine for most games that would use SudoMaker or MTT, but there are a few that will only work vGPU wise on the nvidia vgx display adapter like DS3.
---
Things I’ve already tried (probably tried a lot more than this tbh)
Same end result every time: works initially, then eventually breaks after reboot/shutdown once the system starts using 5120x1440 at login. Once that happens, even managing to change the resolution back to anything else, doesn't work either.
---
EDIT:
After a lot more testing this actually turned out not to be EDID / resolution / VGX related at all, but the VirtIO network drivers. I came across this issue which pointed me in the right direction:
https://github.com/ClassicOldSong/Apollo/issues/1181
Switching the VM NIC from VirtIO to E1000/E1000E immediately fixes the problem and makes Sunshine/Moonlight stable again, even with 5120x1440 in use. So the black screen / white border / “host didn’t send any video” seems to be caused by something in the VirtIO network stack rather than NVENC or the display pipeline.
The downside is that E1000/E1000E are emulated NICs, not paravirtualised, so performance drops significantly. In my case that means losing 10Gbit and falling back to ~1Gbit, so it’s not really a proper fix. Next thing I’m going to try is downgrading the VirtIO drivers, as I have another VM with older drivers where this issue doesn’t occur. Will update again if that works, but for now if anyone else hits this, try switching NIC type as a quick test to confirm it’s the same issue (then maybe try downgrading virtio drivers).
EDIT:
Working VirtIO NIC driver: NetKVM 100.90.104.21400 (2021-10-30)
Problematic VirtIO NIC driver: NetKVM 100.101.104.28500 (2025-07-09)
After downgrading the VM back to 100.90.104.21400 and restoring the VM NIC to VirtIO, the VM remained reachable and the issue appears resolved.