tangled.org / core
Monorepo for Tangled — https://tangled.org
fork atom

feat: git LFS support #121

open
opened by ralith.com

Git LFS is popular, but forge support sucks:

  • GitHub hosting is unreasonably expensive
  • Self-hosting breaks forge-based access control

Tangled is in a unique position to do better here by starting off with an open identity infrastructure and first-class self-hosting. A good implementation would include deduplication (e.g. FastCDC) and allow users without write access to submit PRs containing LFS-managed data, even to self-hosted repos, without introducing new abuse risks.

This might be moot if git gets better native support for binary files, but that seems unlikely to happen any time soon.

ralith.com (author)

@anil.recoil.org‬ had a look at this already and noted some challenges: https://bsky.app/profile/anil.recoil.org/post/3ll5fituyr22f

anil.recoil.org

The issue with current git-lfs is that it's implemented client side, and so there would need to be an HTTP-level proxy at the PDS to handle the uploads.

There's also an emerging new server-side LFS being merged into git this year in the form of "large object promisers" that would be more transparent to the client; more details at https://tylercipriani.com/blog/2025/08/15/git-lfs/#the-future-git-large-object-promisors

sign up or login to add to the discussion
Labels

None yet.

area

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:k7eqqknea6vitil2jzxcmrmc/sh.tangled.repo.issue/3lqsjhncy3s22