The issue with the Result type is that it forces you to think about error cases (good) but then leaves you up to your own devices to handle them (bad). It should be no surprise you will get it wrong or make bad assumptions at some point. The whole point of Erlang/Elixir is to assume things will fail and provide a mental model around that. So when you mess up error handling somewhere, there are system-level mechanics in place. A type system for Erlang/Elixir is an attempt at getting the best of both worlds.​​​​​​​​​​​​​​​​ Trusting only one of those mechanisms to give you complete coverage is always going to be limited.

GitHub owns NPM. The next time GitHub tries to sell you "enterprise security features," ask why they can't stop the deluge of (relatively simple) NPM account takeovers, malware uploads, package squatting, etc.

Frente a los derechos humanos, el silencio no es una opción. Paz y justicia para Palestina. rtve.es/play/videos/directo/…

hello, I'm introducing my latest open-source project called lorito, an HTTP security suite. In this post, I discuss four different classes of web vulnerabilities and demonstrate how lorito helps exploit them. csal.medium.com/introducing-…

pasajes listos para Buenos Aires y entrada para la #EKO2024 ❤️ feliz de reencontrar amistades y participar en el evento de BB de @yeswehack 🤞

souvenir screenshot while it lasts 😅 vamos equipo 🇨🇱 💪

Half of the success in source code auditing is just having the confidence and faith that you will find something. It doesn't matter what language it is or how many times it's been audited. This has proven true throughout my career. Just. Don't. Give. Up.

Day 1 of #H14420 in partnership with @Zoom is here! The clock is ticking as hackers spend the day collaborating, finalizing reports, and monitoring leaderboard updates. Who will uncover the best bug of the event? 🪲

heading to London for #h14420 event 🚀

Messi really did it 😭

¡Sí, rey! ✋😃🤚

🔴 Gobierno de @gabrielboric anuncia, representado por la ministra @camila_vallejo, la creación de un Grupo de Trabajo liderado por Chile, Noruega, Grecia, Lituania, Luxemburgo y Finlandia para combatir la desinformación en distintos niveles. Este espacio es inédito en la OCDE.

with @saamux and @f4d3_cl at @Hacker0x01 #h1702 event last week, what a great event!

starting #h1702, let's go!

Hoy la comisión mixta de Seg Pública del congreso aprobó criminalizar el #hackingético al aprobar la #leydelitoinformatico Tras 3 años de discusión, primó una visión miope, antidiluviana de la ciberseguridad. Seguridad por oscuridad desde ahora en Chile . Hilo largo 1/n

créer une entreprise en France c'est compliqué, au début chaque démarche devient un problème .. la seule lumière sur le chemin est @indyteam_fr , je n'ai pas de mots pour l'accompagnement et son service client 5 étoiles à tout moment indy.fr?promocode=FEB22_Y809…

we got the 3rd place in a strong team effort all along the cup 🇨🇱 the last two rounds, @f4d3_cl and I did a fruitful collaboration that resulted in 2 critical, 5 high, 11 medium and 3 low severity vulnerabilities. Looking forward to competing next year, Chile represent! 💪

vamos team Chile, con todo! 💪

I recommend it to anyone interested in web security and code review! credly.com/badges/13f5e727-d…