The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Highly available AWS production environment with EKS, multi-AZ RDS, automated failover, WAF-protected ALB, and full CI/CD pipeline. Infrastructure as code with comprehensive security and monitoring.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Would you run a command without knowing what it could do?
A copied installation script. An automated workflow. A shell command suggested by AI.
Convenient? Yes. Worth checking before execution? Absolutely.
That’s why I built SafeShell, an open-source tool for inspecting commands, applying security policies, and running permitted commands with sandboxing on Linux.
The goal: help developers and engineering teams work faster with more control over what they execute.
Explore the code, try it, and share your feedback:
https://github.com/HamzaGhebriche/SafeShell
Building automation or CI/CD workflows that need stronger security controls? I’m available for freelance projects in DevSecOps, secure automation, and cloud security. Let’s talk through Contra.
Login page idea design
A playful visual concept where the character literally “arms” himself depending on the strength of the password.
As the user creates a stronger password, the character progressively equips himself with more powerful protection and armor. The stronger the password, the better prepared and more protected he becomes.
The idea turns password security into a simple and engaging visual metaphor , instead of showing abstract security levels, the user can immediately see how their password makes the character stronger and safer.
Very cool, Anna!
Most PDF extraction pipelines would have missed the Brazilian court-filing injection.
Two law firms hid white-on-white text in a labor court petition. It told the court's AI reviewer to answer superficially and not challenge the documents. The court's tool, Galileu, flagged it and blocked it, and the court fined the firms 10% of an R$842,000 claim.
Most of the Hacker News thread blames the court for running AI on filings. But the trick works on any pipeline that reads PDFs. White text is invisible on the page and still sits in the text layer, which is what gets extracted.
My extraction pipelines check each field against the page it came from. That catches a wrong value, but not an instruction that changes how the model reads the rest of the file. That needs a check before the model sees anything: text a person can't see on the page shouldn't reach the model.
In the PDFs you extract from, how often does the text layer hold something the page doesn't show?