4 ms·
Yes GitHub has this problem, but it's not a GitHub problem, it's an oauth problem. Oauth is better than the previous state of the art (either app-specific pass
by philsnow 6y ago
Yes GitHub has this problem, but it's not a GitHub problem, it's an oauth problem.
Oauth is better than the previous state of the art (either app-specific passwords that can do anything you can do or else literally just your own username and password), but it has a huge UX problem around least privilege.
In general it's very opaque what the requested permissions can be used to do. Some companies get this pretty right but there are tons that don't.
Let's say the requested permission is very straightforward like "append rows to your existing spreadsheets". It's also generally impossible to grant access using oauth to just a subset of whatever resource it is, like only spreadsheets A, B, and C, but not X.
I wish sandstorm had caught on much bigger than it had, it brings a fine-tune grained capabilities-based auth system.
- deleted 6y ago[deleted]
- pdimitar 6y agoIs there a problem using Sandstorm today? I followed it some years ago but never actually tried it, always too busy. :(
- philsnow 6y agoOnly the same problem as using any other open source thing that didn't catch on: you have a smaller community to get support from, newer things won't be ported to your platform quickly or ever, and your chosen platform gets less adoption and becomes less compatible over time. I stopped using Slackware when I got married / got a job / had kids, because debian made all my day to day management tasks easier and I no longer cared about knowing deep details about every single package that lived on my system. I'll still install it and toy with it, but I'm not going to push my kids towards using a sandstorm word processor over google docs etc.