91–100 of 390 posts
Edit: And of course big congrats to Matt and Brendan on the launch! It's been a lot of work and a long time coming. You've built a great product!
Earlier quoted context omitted.
I love your concept and wish to cheer you on, but this statement > You can run `fig settings app.disableTelemetry true` to disable all telemetry except for one daily ping. contains such a blatant lie (disableTelemetry does _not_ disable telemetry) that I've already lost a lot of trust, in an area I am not willing to play trust games. I hope you rethink this, soon and loudly.
So what does it do? Is it just about the daily ping?
Iterm can do this for you as well
Earlier quoted context omitted.
You shouldn't feel bad for opting out of telemetry!
We just want people using Fig and enjoying it! That's our top priority. Don't feel bad at all about opting out of telemetry :)
Even if it stays honest and never dark-patterns me, i expect at the very least the service will change in some way. Failing entirely, dark patterns, etc. My preference for simple products i can purchase gives me confidence that it will just work as long as i need it.
No criticism towards you - just giving feedback.
Very smooth, downloaded it and played around a bit. My first thought is why not use built-in shell autocompletion functions instead of redefining them in JS? Zsh completions are super powerful: https://github.com/zsh-users/zsh-completions/blob/master/zsh... Typing `git a ` yields this in my terminal: ~ git add add -- add file contents to index am -- apply patches from a mailbox apply -- apply patch to files and/or to…
This is something we definitely should add as a fallback when a Fig completion spec doesn't exist! The reason we created our own standard is because traditional shell autocomplete doesn't always provide metadata, like descriptions, priority or icons. Also it is a little tricky to write by hand, unless you're pretty familiar with shell scripting.
For python argparse, there is argcomplete in the same vein
Just chiming in on the telemetry issue, there are definitely situations where you could accidentally paste/type sensitive data into the terminal, so you'd need to treat any user data from terminal sessions as toxic waste.
Earlier quoted context omitted.
Do you consider your email to be all that private?
In the context of an app that requests accessibility access (read: everything I do on my computer, without restriction), absolutely!