3 ms·

Github star history graph of the batch: https://star-history.com/#trpc/trpc&termux/termux-app&responsively-org/responsively-app&nuxt/framework&spyder-ide/spyde

• nindalf 4y ago
  Yeah, not pasting in my personal access token into a random website.
  • barbazoo 4y ago
    lol, yeah, I guess you can restrict scope but still, nice try
    • jrochkind1 4y ago
      You can't restrict very much/very well. I think you still can't restrict to specific repos? How much do we have to fundraise to give github to implement API tokens for which you can limit auth for more common use cases?
      • charrondev 4y ago
        I know I have access to fine grained access tokens (beta) which let you get very granular on a per repo. I’m not sure if this is generally available or only because we are on Github Enterprise though.
  • tedmiston 4y ago
    You can use the new Fine-grained Personal Access Tokens [1] (as opposed to the original ones, now called "Personal Access Tokens (Classic)". With the fine-grained tokens, you can literally grant this site: - Repository access: none - User permissions: none - Repository permissions: none [Or if you want to be really paranoid, make a burner account... ¯\_(ツ)_/¯.] But also, star-history.com is not a random site — the repo [2] has 4k stars and has been around since 2015 and has been popular for over a year. If you've ever tried to make a public app that depends on GitHub APIs, the limits without taking PATs are very, very low — totally insufficient for an app with any popularity, so there's not really an alternative. [1]: https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/ https://github.blog/2022-10-18-introducing-fine-grained-pers... [2]: https://github.com/star-history/star-history https://github.com/star-history/star-history
  • swyx 4y ago
    its loading without a PAT now for me.. presumably because it was able to cache other people's requests