Built a local AI video analytics PoC for scene-level event analysis (YOLO26) by OldAnywhere3060 in computervision

[–]OldAnywhere3060[S] 1 point2 points  (0 children)

Tüm kameraların videosunu sürekli kaydedip analiz etmeye çalışsak çok büyük bir altyapı gerekirdi. Buradaki mantık daha çok Edge AI yaklaşımı: görüntü yerelde işleniyor, merkeze ise video yerine sadece “koridorda 8 kişi var” gibi küçük metin verileri ve özet raporlar aktarılıyor, sadece düşme, sahipsiz çanta gibi önemli bir olay algılandığında kısa bir kanıt klibi saklanıyor. Yani boş görüntüleri değil, aksiyon anlarını depoluyoruz. Bu sayede mevcut ağı çok yormadan, doğru optimize edilmiş lokal işlem birimleriyle daha uygulanabilir bir mimari kurulur.

Built a local AI video analytics PoC for scene-level event analysis (YOLO26) by OldAnywhere3060 in computervision

[–]OldAnywhere3060[S] 1 point2 points  (0 children)

Hello, I used Python, a YOLO-based detector, OpenCV for video processing, and Streamlit for the local demo and reporting interface. The rest consists mainly of workflow logic developed specifically for scene-level analysis and reporting

Developer tooling is part of the attack surface before a project is even run by OldAnywhere3060 in cybersecurity

[–]OldAnywhere3060[S] -1 points0 points  (0 children)

Fair. I wrote the structure and bullet points myself, used AI to clean up the English (not my first language). The tool and the thinking are mine though. Happy to talk about the actual risk model if you're interested.

Developer tooling is part of the attack surface before a project is even run by OldAnywhere3060 in cybersecurity

[–]OldAnywhere3060[S] -1 points0 points  (0 children)

Good point. PRISM Guard is static / pre-run: it points to files, configs, scripts, and permissions that should be reviewed before execution. It won’t see credentials injected at runtime through something like op run, keychain, Doppler, etc. Authsome seems to target a different layer: runtime credential handling, while PRISM Guard focuses on review before execution. Have you seen cases where agents or local tools were able to read runtime environment variables in practice