i was more thinking like, if i am working on project ABC for org XYZ it's understandable that if my dev vm gets owned that ABC is leaked. it's not that acceptable if all of org XYZ's repos that i have access to get leaked. and especially not acceptable if everything i have access to, including other orgs, and the admin ability to do destructive operations on them, gets exposed. but status quo is that that's absolutely the case, and you basically need org specific github accounts to reduce the risk of that. or use the knee-capped fine grained PATs that github offers but don't work for common things like seeing if your PR is green.
agree generally with what your getting at though: doesn't solve this problem. but even just a basic reduction in blast radius would be nice.
i'd love to be able to use fine grained tokens with gh and not expose every repo and org that i am connected to on github, but you can't see the results of a github actions check that way (no 'Checks' permission available). hoping these breaches push things in the direction of access being less annoying to manage.
why does cloudflare not allow existing users to create new accounts? you basically need to use a burner email and transfer it afterward. makes it awkward to use this on new projects that you want independent of your existing accounts.
mine was originally on sunday, then got moved to thursday (which i disliked), and it is still on thursday. so them resetting my weekly limit on the same day it was scheduled to reset feels like a joke.
as an exe customer i'm really happy to see this. i don't even use half of their features (such as the https proxy, or the LLM agent) but it's just a reliable computer that i can ssh into from my laptop or phone. i use hetzner too in the same way for a bit of redundancy but exe seems less likely to delete all my machines and data.
every time i've had an issue or question, it's been the same sympathetic people helping me out. over email, in plain text.
hey thanks for sharing this and the kind words :-)
it's my second most used CLI tool after git. thrown together to support my own (and my colleagues') use cases, i'm glad other folks find it handy. would be nice to support more features in it when i find the time.
keystatic supports editing mdx files. keystatic is basically a frontend to update files on github, so if e.g. you want to write a blog post from your phone it can let you do that kind of thing.
is this secure by default in rails yet? i find it surprising that these techniques are promoted at the same time vulnerabilities are being publicly disclosed:
started one this weekend, it lets you put image directories in _galleries/ and provides you with resized images. needs work yet before it's generally useful but might be a helpful start:
agree generally with what your getting at though: doesn't solve this problem. but even just a basic reduction in blast radius would be nice.