True, but adding more passwords does not solve that. However my main password store is really just my head. I tend to employ complex (nonsensical, generatd) passwords and remember those.
I have severall computers, and while I do use ssh keys I have a really hard time figuring out on which computer exactly i store any secrets I need. effectively the more of these I need the more likely it is that I will be locked out.
If in theory Haiku implemented by iteself a synched password manager which does webauthn, provides totp, tokens instead of passwords etc that can be revisited.
I don’t accept the counter argument of what boils down to “lol just use this software and this backup technique”. I’m not on the business pf running hacky bash or python scripts on my Haiku installation for anything.
So yes, for me personally this is accelerating the process somewhat
I offered that above, atleast to try and see if this is feasible.
I think there are way more problems with github than just those you listed, the maintenance effort of haikuwebkit beeing one of them. I’m kind of sick of github requiring “state of the art” apis and not having a fallback for somethibg that worked last weeks for complex topics like “rendering a combobox”.
Another is the hard to learn complex UI and the workflow.
As one example for a PR on webkit you commented on it. I could tell because I received an email for it, but finding the comment took about half an hour because it was not in the “PR view” of the commit but the “source repo” commitview, something you baically never need otherwise when dealing with PRs
I agree only slightly. Staying on github is the opposite to this, using Haikus sso and allowing those third party logins with a self hosted instance would accomplish the goal.
(Of those listed I only have github, and basically only because I was forced to get one to contribute to Haiku… but that is now no longer a reason, So I might aswell delete it at some point. The other reason: to be able to work effectively with you on haikuwebkit also seems to be jepordized by this situation, so I wills have to set up a new git regardless. )