Earlier quoted context omitted.
How did you find these changes?
I used the Unix "locate" command-line tool. I just searched for "keybase". Note that you have to build up a locate DB first by calling "sudo /usr/libexec/locate.updatedb". Type "man locate" in Terminal to learn more.
Introducing Keybase Chat
131–140 of 201 posts
Re: Introducing Keybase Chat
#132Earlier quoted context omitted.
How did you find these changes?
I used the Unix "locate" command-line tool. I just searched for "keybase". Note that you have to build up a locate DB first by calling "sudo /usr/libexec/locate.updatedb". Type "man locate" in Terminal to learn more.
Re: Introducing Keybase Chat
#133Earlier quoted context omitted.
It's a backup key in case you lose access to all your other devices. That way, you don't have to rekey all your services if you lose it and access to all your devices, like I did. Protip: Use the paper key. Keep it safe. You never know when you'll have to use it.
I actually keep it in my keepass password manager, so it is encrypted and on my phone.
Re: Introducing Keybase Chat
#134Warning to all OS X users: The Keybase Chat desktop app does a number of shady things that ultimately led me to delete it from my system. I am writing this purely as a public service announcement, to those who worry about installing unknown apps on their Macs. The Keybase Chat app: (1) Requires administrator privileges to launch on first run, to install a "Helper Tool". The app does not explain what this tool does, w…
https://github.com/keybase/client
As far as I know, it asks for root because the Keybase filesystem runs on Fuse, and the menu bar app can be quit from its menu.
It's hard to balance making a simple, self-contained app with providing easy installation, a custom filesystem, automatic updates, and a command line tool… if you have ideas on how to improve things, I think they'd be open to issues/PRs. (I used to work on Keybase. I personally trust the devs, but, really, you can build from source if you want.)
Re: Introducing Keybase Chat
#135Earlier quoted context omitted.
To play devil's advocate, steps 1, 2, 4, 5, and 6 are all fairly standard behavior for a Mac app that is installed "for all users on this system". https://developer.apple.com/library/content/samplecode/SMJob... Step 2 and 7 are fairly standard behavior for an application that is meant to be running at all times, eg a persistent chat app. Even something like GPG installs files into /Library/LaunchAgents. The location…
I accept your devil's advocacy, but I would argue that the app should have simply asked permission before doing these things, especially installing itself as a startup item and adding a Finder favorite. Also, if the app is going to install things as an administrator, it should tell the user exactly what it plans to do. Just my $0.02. I know that Keybase the company is not shady, but their chat app sure feels off to m…
Re: Introducing Keybase Chat
#136Warning to all OS X users: The Keybase Chat desktop app does a number of shady things that ultimately led me to delete it from my system. I am writing this purely as a public service announcement, to those who worry about installing unknown apps on their Macs. The Keybase Chat app: (1) Requires administrator privileges to launch on first run, to install a "Helper Tool". The app does not explain what this tool does, w…
By default, unless absolutely necessary, your app should install with only user-level permissions and should not attempt to insert itself into the boot process. Just let me click on the app when I want to open it. I don't need toolbars, I don't need a launch daemon, I don't need a global install. If you think those features are really great for some reason, let users opt into them later on.
Re: Introducing Keybase Chat
#137Re: Introducing Keybase Chat
#138This looks absolutely amazing! Any plans for a web client for chat?