| GitHub | https://github.com/steiza |
| Website | https://coffeehousecoders.org |
@george @peterhoneyman I can't pass up an opportunity to bikeshed!
What about a cron that runs once every 12 hours that sleeps a random number of seconds between 0 and 12 hours?
It will post on average every 12 hours, not 10, but you could still end up with posts close together (although then you're guaranteed quite a bit of time before the next one). And the posts would be randomly distributed throughout the day.
Not a good approach if you're using a cloud service that charges by the second!
The number of CVEs GitHub helps open source projects disclose has more than doubled compared to any 30 day period in the past year. Many of these vulnerabilities are being discovered with LLM assistance, and a natural question is "are they slop?" Using the famously uncontroversial CVSS scores, you can see that there are more low severity and high severity scores compared to a year ago. 🤷 It's complicated!
Sources:
- https://cnapulse.org/cna-detail.html?cna=GitHub_M
- https://www.cvedetails.com/cvss-score-charts.php?fromform=1&vendor_id=&product_id=&startdate=2025-01-12&enddate=2025-02-12
- https://www.cvedetails.com/cvss-score-charts.php?fromform=1&vendor_id=&product_id=&startdate=2026-01-12&enddate=2026-02-12
Finished my git-pkgs talk, thanks for having me @fosdem, I had a blast!
See you again next year, fancy another package manager dev room?
Using an age keyserver as a demo, this article demonstrates how to add a transparency log to a centralized service step-by-step.
We use Tessera for the tlog, VRFs for privacy, and the Witness Network. It all takes just 500 lines to integrate!
The result of years of work making tlogs accessible.
Are you a senior software engineer in need of a break this holiday season? When someone asks you for feedback, roll a d6 and respond:
6: "what problem are you trying to solve?"
5: "where is this written down?"
4: "is this on the critical path?"
3: "you need to add rate limits"
2: "what features can we remove for the proof-of-concept?"
1: "we tried that 5 years ago and it didn't work"
🎉 The 2025 OpenSSF Annual Report has officially arrived!!!
We invite you to celebrate another year of progress, creativity, and collaboration shaping a safer, more resilient open source community.
Download the report: https://openssf.org/download-the-2025-openssf-annual-report/