Gert

https://mastodon.gamedev.place/@gertkeno

Game developer! I love programming!

Home-Served Website: https://gerthouse.com
Github: https://github.com/Gertkeno
itch.io: https://gertkeno.itch.io/

Public Key

npub12a0fg2gdfemp5nvfs3vpytlk2l279wvznyqv3k747vnsawpntuesp6x3wp

NIP-05 Address

gertkeno_at_mastodon.gamedev.place@momostr.pink

Profile Code

nprofile1qqs9wh559yx5uas6fkycgkqj9lm9040zhxpfjqxgm02lxfcwhqe47vcprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyf8wumn8ghj7mmxve3ksctfdch8qatzqyv8wumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdsyhlpcv

Publishing to

relay.momostr.pink

offchain.pub

relay.snort.social

Author Public Key

npub12a0fg2gdfemp5nvfs3vpytlk2l279wvznyqv3k747vnsawpntuesp6x3wp

Show more details

Last Notes

2025-04-27 16:21:48 UTC

- reply

because the server is in charge of allowing you to checkout previous commits. With lfs a git repo is no longer decentralized, someone has to keep all of the files for previous commits and that duty rests on the lfs server.

2025-04-27 16:12:40 UTC

- reply

Locally you are only storing one version of the file. git-lfs is a git hook that swaps out your specified binary file for a small hash and commits that instead; the lfs side of things uploads your binary file to a different service under the same hash. Your local git only keeps the hash files stored in each commit, when requesting a previous version it asks lfs to download the large file for that hash.

2025-04-27 15:48:33 UTC

- reply

git lfs has to be able to checkout previous versions just like git, so all previously committed lfs files are stored. If you do not care about previous versions maybe you would prefer Syncthing?
Binary files do not benefit from diff compression so it stores the full file, maybe compresses it individually but a .blend is already compressed.