Programming @programming.dev Simplest hash functions
Opensource @programming.dev I accidentally started a green screen revolution... - Corridor Crew (YouTube, 19min) (Repo-Links in desc)
Programming Languages @programming.dev C3 Programming Language
Programming Languages @programming.dev EYG - A programming language for predictable, useful, and confident development
Security @programming.dev Trivy Under Attack Again: Widespread GitHub Actions Tag Compromise Exposes CI/CD Secrets
Security @programming.dev Compromised telnyx on PyPI: WAV Steganography and Credential Theft
cybersecurity @infosec.pub Delve - Fake Compliance as a Service
Security @programming.dev Delve - Fake Compliance as a Service
Web Development @programming.dev Deno 2.7: Temporal API, Windows ARM, and npm overrides | Deno
Programming Languages @programming.dev Uiua — an extremely terse programming langauge
Game Development @programming.dev inputlag.science: latency issues and how to tackle them
Game Development @programming.dev I'm quitting my Indie Game after 5 years - Codeer (YouTube)
Programming Languages @programming.dev KORE Programming Language
Web Development @programming.dev Fully automatic updating Spotify status... without JavaScript?
Programming @programming.dev The Scapegoat Mechanism - mmagueta
Programming @programming.dev The lost art of XML — mmagueta
cybersecurity @infosec.pub Breaking Bitlocker - Bypassing the Windows Disk Encryption
Jenkins @programming.dev Google Summer of Code 2026: Volunteers Needed to Mentor Future Jenkins Contributors - The Jenkins Blog
.NET @programming.dev How We Synchronize .NET's Virtual Monorepo - .NET Blog
Opensource @programming.dev Why users cannot create Issues directly – ghostty













I assume it's not against GitHub terms, but I find it inappropriate and unfitting. Smells like marketing for discoverability with no content, just forwarding. Which is a thing of course, but if you're asking me as a developer and personally, I'd prefer the project not do that. A repo as a pure landing page uses nothing of what makes a repo a repo.
If it's a developer creating their portfolio and linking their distributed projects to their developer profile, I think I can see some value in that. But in that case, all of them should be in one repo.