Procedural game-sound CLI for AI agents: synths, drums, sfx, car engines, formant speech (robot/evil robot/monster…), effects, loops. Includes a Claude Code skill. - ogomez92/genny

New AI Models Just Dropped.

The first 508 audit that actually listens. Drives real screen readers across your mobile app, captures what they speak, and emits evidence transcripts plus a draft OpenACR. - IRS-Public/aloud

Fill out PDFs independently using only your keyboard and screen reader.

Free video magnifier apps for Android phones and tablets that don’t have advertisements, perfect for low vision users and visually impaired students

I recently built a Python library for the first time in a while, and to make it available in PyPI I followed the official Python packaging guide. But it turns out there’s some rough edges in the suggested tools.
Namely, the build backend hatch puts all the files in the project directory into the built sdist, except from some files it chooses to exclude, which led to a gitignored file as well as VCS metadata getting packaged and uploaded to PyPI. This really surprised me, and I think most Python users new to packaging would be better served by choosing a conservative build backend like uv_build, which puts only the Python source modules and some specific project-level files into the sdist.

Open, Jev-compatible System One decision server on DiffusionGemma - razorback16/openjev

An Archive of Our Own, a project of the Organization for Transformative Works

Thirty years of voluntary funding schemes haven't paid open source maintainers because asking doesn't scale. The real money already flows — to JFrog, Docker, Sonatype — at the registry layer. The fix: registries charge companies for supply (they already do), then route a slice automatically to the maintainers who make that supply worth having.