Vibe coding has turned devs into ‘AI babysitters,’ but they say it’s worth it
Bitcoin: The Trust Machine - YouTube
among-llms: You are the only impostor. One wrong word and they'll tear you apart Among LLMs turns your terminal into a chaotic chatroom playground where you’re the only human among a bunch of eccentric AI agents, dropped into a common scenario -- it could be Fantasy, Sci-Fi, Thriller, Crime, or something completely unexpected. Each participant, including you, has a persona and a backstory, and all the AI agents share one common goal -- determine and eliminate the human, through voting. Your mission: stay hidden, manipulate conversations, and turn the bots against each other with edits, whispers, impersonations, and clever gaslighting. Outlast everyone, turn chaos to your advantage, and make it to the final two. Can you survive the hunt and outsmart the AI?
Certificate and Public Key Pinning A nation state with control over a Certificate Authority could create SSL certs for any domain and easily perform a MITM. That's the risk. First idea that comes to mind to mitigate it, would be to at least pin domains to CAs so that a random CA controlled by a nation state can't issue a new certificate for any domain without going unnoticed. This might be overkill and apparently is not a good idea: - PKI has significantly improved - browser vendors (Google, Mozilla, Apple, Microsoft) now strictly control CA trust stores and remove non-compliant CAs - Certificate Transparency - all certificates must be publicly logged, making rogue certificates detectable - CAA records - DNS records that specify which CAs can issue certificates for a domain - Pinning creates major operational risks - misconfigured pins can cause complete outages that are difficult to recover from But just out of curiosity, I'm trying a Firefox add-on that notifies you every time something changes in the certificate of a website that you had already visited. It can be configured to only notify you on a change of the issuer. So if a website goes from Let's Encrypt CA to CCP CA, you should worry xD Here's the extension: ![Certificate Watch configuration](https://m.stacker.news/108129)