you are viewing a single comment's thread
view the rest of the comments
[–] 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
  • [–] 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
  • 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