▲ 2268 ▼ Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft. (programming.dev) submitted 1 year ago* by Tea@programming.dev to c/technology@lemmy.world 279 comments fedilink hide all child comments Post New Git Repo.
[–] Valmond@lemmy.world 3 points 1 year ago* (last edited 1 year ago) (1 child) Have you heard of ... Git? :-) Edit: I was jesting, got interesting responses! permalink fedilink source parent hideshow 2 child comments replies: [–] lemmydividebyzero@reddthat.com 10 points 1 year ago (1 child) There is no command git issue create [hostname] [title] [description] and if there was such a command, it'd require authentication on the specific instance to prevent spam. You still need to create an account on each Forgejo instance to report a bug there... And even, if you commit code or make a pull request... Git might be decentralized (you can develop with your friend independently from each other and merge it), but try to commit code to a GitHub project, GitLab instance or Forgejo instance without having an account there to authenticate yourself... It won't work. permalink fedilink source parent hideshow 2 child comments replies: [–] prettybunnys@sh.itjust.works -3 points 1 year ago (2 children) You mean git inherently requires you to identify yourself? Huh, shock permalink fedilink source parent hideshow 4 child comments replies: [–] lemmydividebyzero@reddthat.com 8 points 1 year ago I'm not sure what you are trying to say. My point was from the beginning that I don't want to create 2 accounts when I report a bug a bug on Forgejo instance 1 and on instance 2. The suggestion whether I have heard about git does not solve anything about that... Some one else here mentioned that it's possible to login with Mastodon on each of the instance, which is the correct direction (allows to report a bug on both instances via an external account). Disadvantage is still: My 2 bug reports are not linked to each other, because there is no shared Forgejo profile, which would actually require something like federation. permalink fedilink source parent [–] WhyJiffie@sh.itjust.works 5 points 1 year ago git identification has nothing to do with authentication, as any sane person with git experience knows permalink fedilink source parent
[–] lemmydividebyzero@reddthat.com 10 points 1 year ago (1 child) There is no command git issue create [hostname] [title] [description] and if there was such a command, it'd require authentication on the specific instance to prevent spam. You still need to create an account on each Forgejo instance to report a bug there... And even, if you commit code or make a pull request... Git might be decentralized (you can develop with your friend independently from each other and merge it), but try to commit code to a GitHub project, GitLab instance or Forgejo instance without having an account there to authenticate yourself... It won't work. permalink fedilink source parent hideshow 2 child comments replies: [–] prettybunnys@sh.itjust.works -3 points 1 year ago (2 children) You mean git inherently requires you to identify yourself? Huh, shock permalink fedilink source parent hideshow 4 child comments replies: [–] lemmydividebyzero@reddthat.com 8 points 1 year ago I'm not sure what you are trying to say. My point was from the beginning that I don't want to create 2 accounts when I report a bug a bug on Forgejo instance 1 and on instance 2. The suggestion whether I have heard about git does not solve anything about that... Some one else here mentioned that it's possible to login with Mastodon on each of the instance, which is the correct direction (allows to report a bug on both instances via an external account). Disadvantage is still: My 2 bug reports are not linked to each other, because there is no shared Forgejo profile, which would actually require something like federation. permalink fedilink source parent [–] WhyJiffie@sh.itjust.works 5 points 1 year ago git identification has nothing to do with authentication, as any sane person with git experience knows permalink fedilink source parent
[–] prettybunnys@sh.itjust.works -3 points 1 year ago (2 children) You mean git inherently requires you to identify yourself? Huh, shock permalink fedilink source parent hideshow 4 child comments replies: [–] lemmydividebyzero@reddthat.com 8 points 1 year ago I'm not sure what you are trying to say. My point was from the beginning that I don't want to create 2 accounts when I report a bug a bug on Forgejo instance 1 and on instance 2. The suggestion whether I have heard about git does not solve anything about that... Some one else here mentioned that it's possible to login with Mastodon on each of the instance, which is the correct direction (allows to report a bug on both instances via an external account). Disadvantage is still: My 2 bug reports are not linked to each other, because there is no shared Forgejo profile, which would actually require something like federation. permalink fedilink source parent [–] WhyJiffie@sh.itjust.works 5 points 1 year ago git identification has nothing to do with authentication, as any sane person with git experience knows permalink fedilink source parent
[–] lemmydividebyzero@reddthat.com 8 points 1 year ago I'm not sure what you are trying to say. My point was from the beginning that I don't want to create 2 accounts when I report a bug a bug on Forgejo instance 1 and on instance 2. The suggestion whether I have heard about git does not solve anything about that... Some one else here mentioned that it's possible to login with Mastodon on each of the instance, which is the correct direction (allows to report a bug on both instances via an external account). Disadvantage is still: My 2 bug reports are not linked to each other, because there is no shared Forgejo profile, which would actually require something like federation. permalink fedilink source parent
[–] WhyJiffie@sh.itjust.works 5 points 1 year ago git identification has nothing to do with authentication, as any sane person with git experience knows permalink fedilink source parent