Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Which already did some things wrong even though Keybase is around for a few years.


Care to elaborate? Just curious...


https://news.ycombinator.com/item?id=22997245 and requiring gnome-keyring on Linux are issues for me.


Does it actually require GNOME Keyring or does it just use libsecret? Because libsecret is dope and has been nothing but a joy to work with.


I've seen some examples of GNOME keyring being required because it implements the freedesktop secrets standard (which I admit to knowing nothing of) where other secret managers do not. Presumably meaning there us no common interface, so we just pick the one that implements the spec. One example:

https://github.com/pithos/pithos/issues/559



It's (dependency on gnome-keyring) been fixed in the latest release [1].

Assuming GNOME shell is Linux users' default desktop environment is very wrong.

However, providing desktop GUI app in AppImage format is great.

[1]: https://github.com/keys-pub/app/issues/6


Those looks like differences and matters of preference not anything "wrong" about it.


Well, there are reasons why Keybase changed from key-centric to identity-centric back in 2015: https://keybase.io/blog/keybase-new-key-model




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: