4 ms·
With self-hosting you don't get the broader community... With node, for example, most modules have source on github and it's easy to fork, fix/enhance something
by tracker1 11y ago
With self-hosting you don't get the broader community... With node, for example, most modules have source on github and it's easy to fork, fix/enhance something and submit a PR... with everyone self hosting, how many logins do you have to create.
I know, tracking, federation, etc... but it's much nicer only having a couple logins (google, fb, twitter, github) for most sites I access regularly.
- carussell 11y agoSSO is a separately solvable problem, and even so, I'm not sure it's a solution that needs applying here. It's not clear why any form of sign-on is needed—SSO or not. Almost everybody in this space is already using public-key crypto for authentication.
- tracker1 11y agoBut not for signing into the website, and adding notes for a pull request, or filing a bug/issue/feature request.
- deleted 11y ago[deleted]
- carussell 11y agoI don't even know why I bother trying to have discussions with GitHub users.
- tracker1 11y agoHow does public key crypto let me use multiple website, similar to github's, so that I can create a PR, and update/edit notes/comments on issues? It's a demonstrably broken experience in the browser. Having one key to rule them all, so to speak is far easier than having to sign into every project's own issue tracker. I understand the risks (ie: sourceforge), but have some level of trust in GH's founders.