@Salsa12__ But will it still be enough for internal processes like integrity checks and other detection techniques? I have seen some cheat tools that use this still.
@DoranekoSystems@hasherezade thanks for contributions to ecosystem. gonna try it today. the only missing part is AI integration with an option of bring your own keys.
Interview with a Senior Software Architect : “I integrate AI capabilities into our SBP Digital Banking Suite” https://t.co/zw5TZyZljf
Check out my latest article: Feed the Raptor, Not the Pigeon
How Hierarchical Chunking + Contextual Retrieval Turns a Plain-Old RAG Into a Carnivore https://t.co/dErkQmndtV via @LinkedIn
@BavariaDevanshi the graph-like depiction of the LCM is incorrect for a diffusion-based model, which should instead show a U-Net or an iterative denoising process.
Yes, we’re both talking about the same thing, but the difference lies in our levels of understanding. If you provide folder-level access to VS Code, it opens the door for extensions to access your files, which could attract unwanted attention. If you’re only referring to project-level browsing, that’s fine. But if your intention is to replace Windows Explorer with VS Code, that would be a clear mistake from a cybersecurity standpoint.
@RickStrahl it's not really possible to use it for Explorer purposes on Windows. because the extensions have incredible access to anything and which might cause unexpected vulnerabilities. But on macOs, due to it's stupid file navigation system, it worth to sacrifice. 🥹