272
DRM-Free OnlyFans Downloads See Widevine Project Nuked From GitHub (torrentfreak.com)
submitted 1 year ago by to c/technology@lemmy.world
101 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 year ago* (last edited 1 year ago) (13 children)

How come Git is decentralized?
Doesnt it need a central component so I can pull your changes?

Edit: Thanks to all that explained it to me :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 5 points 1 year ago (7 children)

    Changes can come from anywhere. The Linux kernel itself doesn't use any central repository like Github, it's instead done via emailing patches that are eventually merged into the mainline kernel repository managed by Linus.

    It is 100% decentralized.

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

    mainline kernel repository managed by Linus.

    It is 100% decentralized.

    But... How does that work? The code has to be stored somewhere...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 year ago* (2 children)

    How does that work? The code has to be stored somewhere…

    The code is replicated by everyone who works on it, and on various public and private servers, so you might say it's stored everywhere.

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

    Fundamentally, the repository you have on GitHub is the same thing as the repository you have on your computer when you clone it. Pulling and pushing are shorthands for synchronizing commits between the two repositories, but you could also synchronize them directly with somebody else who cloned the repository. As somebody mentioned, you can also just host the same repository on two servers, and push to both of them.

    The issue is that git doesn't include convenient features like issues, pull requests, CI, wikis, etc., and by extensions, those aren't included in your local repository, so if GitHub takes them down, you don't have a copy.

    An extra fun fact is that git can be considered a blockchain. It's a distributed ledger of immutable commits, each one representing a change in state relative to the previous one. Everybody who clones a repository gets a copy of its entire history and fast forwards through the changes to calculate the current state.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago (2 children)

    But to push/pull you'd in theory need to port forward your git server/workstation, right?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 year ago

    Git works through ssh. So you need the same system as sshing into your machine. You just make a user group git and then let git and ssh handle things. And if you don't need people to push to your repo, then it's a lot easier as it's now similar to hosting a website/file server.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 year ago

    Git exposes a lot of internals through odd commands, so I suspect you could manage synchronization by sending changes over email or something.

    Bonus fun fact: there's a git bundle command that "dumps" the repository into a single file, that can be interacted with as a remote. So if you're ever working with a local repository and want to put it on a server over ssh or something like that, you can just create a bundle, scp it over, and clone from that on the server.

  • permalink
  • fedilink
  • source
  • parent