You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on #48, it seems to be impossible for some developers to authenticate themselves by decrypting with age, particularly for those who sign with a yubikey.
Using oauth to authenticate against Github is a lot more user-friendly, more developers would be able to claim their rewards (those that now can't) and also would seem less dangerous for those worried about exposing their private keys.
The text was updated successfully, but these errors were encountered:
So let get me get this straight: contributors that strive to run a tight ship and use good security practices are the ones that you choose to penalize? That doesn't really make any sense. A better answer would be "We are looking into alternative solutions for our yubikey using contributors and will report back asap."
Github deleted my ssh keys for inactivity yet people commit a Readme to some shitcoin get to participate simply bc they used ssh instead of https? Not great planning. Will get ready for influx of shit prs too from farmers loading up for the inevitable fork of this project and their airdrops.
Oauth should definitely be the way to authenticate. Everything is wrong with the current setup as we all basically need to audit your code before doing anything. It's also just showing bad practices to other projects...
Following up on #48, it seems to be impossible for some developers to authenticate themselves by decrypting with
age
, particularly for those who sign with a yubikey.Using oauth to authenticate against Github is a lot more user-friendly, more developers would be able to claim their rewards (those that now can't) and also would seem less dangerous for those worried about exposing their private keys.
The text was updated successfully, but these errors were encountered: