>Codeberg supports account creation and sign-in with GitHub login, so there really are no excuses IMO.
One extra click for any existing GitHub user to comment on a Codeberg repo.
Your simplification of the steps is incorrect. I just did this "sign-in with Github" workflow and it's not just 1 click. After using Github to authorize Codeberg, it still requires new users to enter a valid email. Codeberg then requires verification of that email address by the user clicking on the url in the email.
(And the email address step above also adds more behind-the-scene steps for me since I always create email aliases for every service to manage spam.)
Not sure what friction is removed by signing in with Github rather than just registering a new account email address directly with Codeberg.
Your simplification of the steps is incorrect. I just did this "sign-in with Github" workflow and it's not just 1 click. After using Github to authorize Codeberg, it still requires new users to enter a valid email. Codeberg then requires verification of that email address by the user clicking on the url in the email.
(And the email address step above also adds more behind-the-scene steps for me since I always create email aliases for every service to manage spam.)
Not sure what friction is removed by signing in with Github rather than just registering a new account email address directly with Codeberg.