you are viewing a single comment's thread
view the rest of the comments
[–] 52 points 1 year ago* (last edited 1 year ago) (11 children)

We need something like Forgejo, but decentralized and federated, like Lemmy. I don't want to create a new account for every Forgejo instance, just to be able to report a bug...

Edit: Added "and federated"

  • source
  • hideshow 22 child comments
  • [–] 25 points 1 year ago (1 child)

    Git is already decentralized, nothing is stopping you from adding multiple remotes to your repo.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 29 points 1 year ago (2 children)

    The issue tracker is usually the concern

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 year ago (1 child)

    Yeah, that was my point in the first comment... But not only that...

    The development with multiple people is decentralized, yes...

    But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don't have an account on each of these... Try pushing code or making a pull request and see how it fails, because you are not authenticated...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (2 children)

    How would decentralization work for an issue tracker? The issues have to be stored somewhere.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 12 points 1 year ago* (last edited 1 year ago)

    You know, git initially was that kind of thing where people would send diff commits on mailing lists. Git is perfectly decentralized already. And there's no need for federation.

    Forgejo is already decentralized too. You could host your own instance right now, if you'd want.

  • source
  • parent
  • [–] 5 points 1 year ago* (1 child)

    if you are looking for decentralised vcs you can try radicle, I tried a while ago pretty good. FYI Forgejo supports mastodon login

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago* (last edited 1 year ago)

    FYI Forgejo supports mastodon login

    That's interesting. Did not even know, Mastodon supported doing something like this...

    There is still a difference: There is no profile in the end. I might create 2 bug reports, bit they won't be linked to each other.

  • source
  • parent
  • [–] 3 points 1 year ago* (last edited 1 year ago) (1 child)

    Have you heard of ... Git?

    :-)

    Edit: I was jesting, got interesting responses!

  • source
  • parent
  • hideshow 2 child comments
  • [–] 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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -3 points 1 year ago (2 children)

    You mean git inherently requires you to identify yourself?

    Huh, shock

  • source
  • parent
  • hideshow 4 child comments
  • 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.

  • source
  • parent
  • [+] 3 points 1 year ago* (last edited 1 year ago) (1 child)
  • [–] 4 points 1 year ago (2 children)
  • [+] 7 points 1 year ago* (last edited 1 year ago) (1 child)
  • [–] 3 points 1 year ago (6 children)

    I think that's bad (for my personal use) because if I accidentally commit a secret key, how do I claw it back? Basically, how would I claw anything back if it's on a blockchain aka on thousands/millions of computers already (you can't).

  • source
  • parent
  • hideshow 12 child comments
  • [–] 11 points 1 year ago (2 children)

    If you push a secret key you should definitely generate a new one. Way to many bots out there that scan new commits for exactly that reason

  • source
  • parent
  • hideshow 4 child comments
  • I did not mean decentralized hosting of the projects (e.g. your project will be on all instances).

    I meant decentralized account usage (e.g. you can use your example.com forgejo account to create an issue on otherexample.org)... Just like Lemmy... I could use my reddthat.com lemmy account to create a post on your instance lemmy.world without having to register there.

  • source
  • parent
  • [–] 3 points 1 year ago

    that's already a concern. what if someone just cloned your repo? there's also plenty of people that mirror public repos to their personal forgejo server. forgejo makes it very easy.

    the only solution to mitigate such a mistake is to
    1) invalidate the token
    2) remove the commit

    In that order.

  • source
  • parent