Yes, but the requirement of said frontend are very small.
and a frontend needs an account.
Not required at all actually. For example, mirror a github repo in gitea. You’ll see all the commits, their messages, and who made them. Yet that gitea instance isn’t accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a “real” account.
You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don’t have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn’t require accounts. You could email someone your git diff’s and it will function the same.
I feared as much, because the same could be said about your comment above.
I already mentioned git send-email in my comment. But the ux of that is terrible. So if you want good UX you’re in account hell, having to create a new profile for every hosting site.
You can have a nice, terms of service free but read only forge, or you have terms of service and account bullshit or you can have the dev experience of git send email. Choose one of the three and until we have federation they are all terrible in some aspect.
Yes, but the requirement of said frontend are very small.
Not required at all actually. For example, mirror a github repo in gitea. You’ll see all the commits, their messages, and who made them. Yet that gitea instance isn’t accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a “real” account.
Would you call that open source? A read only gitea instance?
If you want to get away from GitHub a mirror won’t cut it, it has to be the main dev platform.
You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don’t have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn’t require accounts. You could email someone your git diff’s and it will function the same.
I feared as much, because the same could be said about your comment above.
I already mentioned
git send-emailin my comment. But the ux of that is terrible. So if you want good UX you’re in account hell, having to create a new profile for every hosting site.You can have a nice, terms of service free but read only forge, or you have terms of service and account bullshit or you can have the dev experience of git send email. Choose one of the three and until we have federation they are all terrible in some aspect.