DE version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
33% Positive
Analyzed from 531 words in the discussion.
Trending Topics
#code#open#pull#prs#https#tokens#account#requests#help#limit

Discussion (24 Comments)Read Original on HackerNews
I'd rather enforce a limit based on the number of PRs that account opened across all public repositories it doesn't have write access to within the last week. And PRs that were closed without getting merged should be held against the account somehow (perhaps via a "close as unwelcome" option for the maintainer).
https://www.hey.com/features/the-screener/
I also like the other features mentioned in the blog post. It won't make a difference to me and my daily work, but I'm glad that they are taking the criticisms seriously.
Though I have to admit that I'm a bit conflicted about this. Part of me also wants more people to move off of GitHub to help break their monopoly on code on the web, but I also don't want the people making and maintaining open source to give up their projects due to burnout and slop spam.
There are some projects where you can provide a PR and they'll just reimplement and I think that's probably adaptive to the world where PR's are cheap and reviews are expensive.
Or donate money. Crazy idea, eh?
Vulnerability reports are not special anymore - https://news.ycombinator.com/item?id=48653216 - June 2026
(also like sibling comment about donating tokens or fiat to buy tokens)