Comment on Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.

lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ ago

• hoppolito@mander.xyz ⁨1⁩ ⁨week⁩ ago

  Forgejo is in fact working on being decentralized, just like the underlying git structure is. There are some first federation things in there, but the full implementation is still pretty far out.

  source

  • endofline@lemmy.ca ⁨6⁩ ⁨days⁩ ago

    Git is decentralized itself… You don’t even need forgejo to host your changes

    source
• ftbd@feddit.org ⁨1⁩ ⁨week⁩ ago

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

  source

  • twice_hatch@midwest.social ⁨1⁩ ⁨week⁩ ago

    The issue tracker is usually the concern

    source

    • lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ ago

      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

      • xigoi@lemmy.sdf.org ⁨1⁩ ⁨week⁩ ago

        SourceHut encourages an e-mail based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it.

        source
    • xigoi@lemmy.sdf.org ⁨1⁩ ⁨week⁩ ago

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

      source

      • WhyJiffie@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

        naturally on the instance that hosts the repo

        source
      • pinball_wizard@lemmy.zip ⁨6⁩ ⁨days⁩ ago

        The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances.

        source
• pathief@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Federation is in their roadmap

  source
• kaidezee@lemmy.ml ⁨1⁩ ⁨week⁩ ago

  You know, git initially that kind of thing where people would send diff commits on mailing lists. And that is perfectly decentralized! And there’s no need for a federation too.

  source
• passenger@lemm.ee ⁨1⁩ ⁨week⁩ ago

  There is this, havent tried

  radicle.xyz

  source
• Valmond@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Have you heard of … Git?

  :-)

  source

  • lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ ago

    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

    • prettybunnys@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

      You mean git inherently requires you to identify yourself?

      Huh, shock

      source

      • lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ 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.

        source
      • WhyJiffie@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

        git identification has nothing to do with authentication, as any sane person with git experience knows

        source
• karthie@lemm.ee ⁨1⁩ ⁨week⁩ ago

  if you are looking for decentralised vcs you can try radicle, I tried a while ago pretty good.

  source

  • lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ ago

    FYI Forgejo supports mastodon login

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

    source
• DasSkelett@discuss.tchncs.de ⁨1⁩ ⁨week⁩ ago

  Gitea has basic federation, I believe

  source

  • wewbull@feddit.uk ⁨1⁩ ⁨week⁩ ago

    Gitea is where Forgejo forked from.

    source
• LemonBreezes@lemmy.world ⁨1⁩ ⁨week⁩ ago

  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

  • holdstrong@lemm.ee ⁨1⁩ ⁨week⁩ ago

    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

    • LemonBreezes@lemmy.world ⁨1⁩ ⁨week⁩ ago

      Yeah it’s not an insurmountable problem but it has happened to me where I push some commits and I realize “oh lemme remove this code because it leaks a little info about me personally” etc

      source
    • tehfishman@lemmy.world ⁨1⁩ ⁨week⁩ ago

      Yeah please just rotate the secret if that happens. Doesn’t matter what platform it is, this is true of GitHub as well. Secrets that are accidentally published are no longer secret.

      source
  • fallingcats@discuss.tchncs.de ⁨1⁩ ⁨week⁩ ago

    Obviously you go and change the key?

    source
  • WhyJiffie@sh.itjust.works ⁨1⁩ ⁨week⁩ 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
  • lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ ago

    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
  • zarkanian@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

    You are correct in principle, but Lemmy isn’t on a blockchain. It’s much less permanent.

    source
  • JuxtaposedJaguar@lemmy.ml ⁨6⁩ ⁨days⁩ ago

    You can make commits on your system without pushing them to the remote server, and that’s the default behavior.

    source
• elrecoal19_1@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Wouldn’t it be the other way around, having someone centralized so with one account you can report bugs in any public project?

  source

  • BoJackHorseman@lemm.ee ⁨1⁩ ⁨week⁩ ago

    Do you know how lemmy works?

    source

    • elrecoal19_1@lemmy.world ⁨1⁩ ⁨week⁩ ago

      I do, what I don’t know is how Forgejo works. Doesn’t having to make an account for every project mean it’s already decentraliced, but just doesn’t communicate between instances?

      source

      • lemmydividebyzero@reddthat.com ⁨1⁩ ⁨week⁩ ago

        I agree that it’s already kind of decentralized, so I also added the word “federated” to my original post.

        source

        • -> View More Comments
• MonkderVierte@lemmy.ml ⁨1⁩ ⁨week⁩ ago

  Rather have it on IPFS or something like OrbitDB, so no one can just lock/delete stuff.

  source