I've been trying out Devin from @cognition the last few weeks, and here are my thoughts...
Big thanks to @cognition and @buildfutureto for providing me with access to try out Devin!
@AaronBuildsIt@buildfutureto@cognition Haha we both submitted last minute ๐
Really interesting project, best of luck building it!
https://t.co/uH3D1Bargr
I've been trying out Devin from @cognition the last few weeks, and here are my thoughts...
Big thanks to @cognition and @buildfutureto for providing me with access to try out Devin!
I think you may have been misinformed a bit.
VPNs don't just change your IP. What it essentially does is encrypts all of your traffic and sends it to one server (the VPN server).
Without a VPN, your ISP can see *every* site you visit. With a VPN on, all they see is scrambled data going to ONE server (Proton's). That's all they see. They have no idea what you're sending to proton, other than you're sending *something* to proton.
Proton then unscrambles it on their end and then sends the request to wherever you're trying to send it to. So your ISP knows you are using a VPN, but they can't see what you're doing with it. The only ones who could realistically spy with you is proton themselves.
Hope this helps!
@ThatNamons@TheTruth11702@ProtonVPN Sure, they can "see" the traffic, but they can only see it's encrypted openvpn/wireguard traffic to proton's servers no?
More in depth explanation from an AI:
The IOMMU (Intel VT-d / AMD-Vi) is a CPU/motherboard hardware feature that counters this by building strict access-control tables (DMAR/IVRS) mapping which PCIe devices are allowed to touch which memory regions โ and critically, Vanguard does not manage these tables itself; that is the job of the UEFI firmware and the Windows kernel. Vanguard's kernel driver (vgk.sys) instead acts as an auditor: it queries Windows to confirm that IOMMU, Secure Boot, TPM 2.0, and HVCI (Memory Integrity) are all active, and throws a VAN:RESTRICTION error and blocks launch of Riot games if any are missing. HVCI is the most powerful layer โ it uses the IOMMU to back a hypervisor (VBS) that sits above even the Windows kernel, creating protected memory regions that no unsigned or unauthorized PCIe device can write to, regardless of spoofed device IDs. The key change in Riot's May 2026 update was enforcement timing: previously, IOMMU was only fully active after the Windows kernel initialized, leaving a pre-boot window DMA cards exploited freely. The new update pushes IOMMU enforcement into UEFI/POST โ the PCIe enumeration phase โ so when a DMA cheat card powers up and attempts its illegal memory transaction at boot, the IOMMU intercepts it immediately, triggers a hardware fault, and the system crashes, hangs, or boot-loops before Windows even starts loading.
Basically these DMA devices by default have unfettered access to all memory on a system. When enabled, the IOMMU enforces an allow list. If a DMA device attempts to read memory outside the ranges explicitly mapped for it, the OS will crash/some kind of error will happen.
The cheat/DMA devices will often pretend to be an NVMe drive or network card, and then read the game's memory. Obviously, a real NVMe or network card has no legitimate reason to touch a game's memory, so with IOMMU enabled, those devices are only supposed to access the memory Windows gives them for normal operation. If a fake device tries to read anything outside of that, the IOMMU blocks it and the OS could crash (more precisely an error is raised/caught)
These machines are likely crashing on boot now because the DMA device starts trying to read memory it is not supposed to access as soon as the system comes up. In the past, IOMMU wasn't (or wasn't fully) enforced at boot, so the device could get away with those reads. Now that IOMMU is being enforced much earlier, those same memory accesses are blocked immediately. Because this is happening so early in the startup process, the system doesn't have any way to recover from it, which leads to a crash
@HighlordRetard@KILLEDXNIMPACT@SpookyGhost81@crash@riotgames Even if it had bricked your windows install, a reinstall with keep files on would wipe out installed programs but leave appdata/programdata intact. Im guessing it's reinstalling the C:/Windows folder
@RhymZ200@deteccphilippe@Dangermad6691 If you have the cheat device installed your pc will not boot with the setting (IOMMU) on.
Nothing gets permanently bricked, you could either turn off the setting or remove the DMA device
They just require you to have the setting on to play the game