I've gotten notices from Hetzner for hosting IPFS node, apparently it does some local network discovery by default which looks like a malware when you squint hard enough.
Don't forget that some of the new features are mutually incompatible. For example couple years ago you couldn't use the "new ui system" with the "new input system" even when both were advertised as ready/almost ready
As someone who's learned Vulkan to a fairly deep level over the last two years I've found learning with LLMs invaluable, especially for explaining concepts and the whys behind things.
That said debugging graphics bugs has to be some of the hardest things you can do as they generally manifest as driver crash followed by VK_DEVICE_LOST error. Vibe debugging these inside a 60k vibecoded rust renderer is... just not possible.
Agents can get you the initial boilerplate for setting up most of the resources, but are completely clueless about subtle issues with synchronization, transitions, formats and so on.
You joke, but I remember seeing a talk by Wunderlist CTO who has pretty much that. Also polyglot company and microservices in random languages. Can't find the talk now, but https://www.infoq.com/news/2014/11/gotober-wunderlist-micros... mentions 60 services at least.
KYC data is the most dangerous data that can leak right now. If your CC leaks, you will know almost immediately and can revoke it and generally will get your money back. Password leaks can be neutered with 2FA. Medical data leak can perhaps be used in a complex extortion, but generally for most people this data is worthless.
KYC data on the other hand allows third party criminals who have bought your KYC on the black market to perform money laundering in your name (by opening bank accounts) and taking debt in your name. Generally you won't even know this is happening until it's too late and debt collectors come. And it's not like you can revoke your biometrics/liveness check/selfie and who knows if revoking your passport/id card would actually work.
IMO it's much better if a dedicated KYC processor, like Persona, with actual security team/mindset, handles this rather than random website inside their zendesk instance. But there still needs to be extremely strict regulation surrounding this data.
Also while CC data will be getting less dangerous over time due to AI fraud detection and mandated 3DS, KYC data will IMO be getting more dangerous over time because more fintech/govtech will rely on it.
I think that biggest difference is that your client applications don't need to be explicitly configured to use the bastion server. For example ssh, web browsers, rdp, samba and so on can just pretend that you are inside the target network. Doubly useful if this is a "customer" network and you are working with multiple customers.
Oh wow, the guy used the word "versatility"... he even dared "narrative" and "just" - the latter one two times! Astonishing, does he have no shame copy pasting this obvious AI slop? It is obvious that no person in their right mind would utter such things!
reply