Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tangled, a Git collaboration platform built on atproto

blog.tangled.org

Post reply on HN
Print view View original

71–80 of 88 posts

Re: Tangled, a Git collaboration platform built on atproto

#71

Post by skybrian »

icy wrote: post #58
skybrian wrote: post #57

Earlier quoted context omitted.

That sounds reasonable, but do your repos get replicated into your PDS? Where else does the data end up?

Git repos don't get replicated anywhere. They live on disk, either on our knot server or yours. Knots are essentially our extension to the AT architecture, allowing user ownership of what's essentially "off-protocol data" (git).

Thanks. What does get replicated?

I'm not sure what I'm looking at, but I see records that look like source code here:

https://ufos.microcosm.blue/collection/?nsid=sh.tangled.stri...

Re: Tangled, a Git collaboration platform built on atproto

#72

Post by electricduck »

xeonmc wrote: post #66
icy wrote: post #50

Hey HN, co-founder of Tangled here! We recently shipped a change to switch out our OAuth library—which introduced a regression, preventing new users from being added to the default knot and spindle (the git hosting server & CI runner). We just discovered this and pushed a fix—please log out and log back in again and you should be able to create repositories! Otherwise, happy to answer any questions!

First Question: is it possible to change your handle or delete your account on the tngl.sh PDS instance? Second Question: how much resource does creating and hosting a new AppView entail? For example let's say I make an appview that's essentially the PDS-hosted equivalent of Cloudflare Pages, where a user upload a folder of a static website and the appview just forwards it verbatim at a hypothetical https://atprotoci…

Since its just a regular ol' PDS, you can simply login to Bluesky and change it there!

Re: Tangled, a Git collaboration platform built on atproto

#73

Post by hamandcheese »

I was pleased to see that this has CI pipeline support, but am saddened to see that it looks roughly GitHub-actions shaped.

I don't see the point in writing a sequence of serial steps in YAML. A bash script can already do that. YAML configuration for pipelines should be focused on expressing the dependencies of a DAG, not the serial execution of a program.

Buildkite got this right.

Re: Tangled, a Git collaboration platform built on atproto

#75

Post by verdverm »

skybrian wrote: post #16

I don't really get it. What if anything gets stored in your PDS, versus somewhere else?

I believe the rough separation is, code in git, all the other stuff around it (like what GitHub provides) as lexicon

iirc, a few things are not in lexicon/PDS yet, but intend to be

Re: Tangled, a Git collaboration platform built on atproto

#76

Post by verdverm »

oblio wrote: post #15
jpereira wrote: post #8

Earlier quoted context omitted.

The fact that all the data is open means not only that you could plausibly exit to other providers and keep all your projects data, (issues, prs, etc), but also that it's dramatically easier to build other tools that work on that same data. Triage, labelers, bots, etc, I know these are all possible on GitHub today with their API, but I think the programming model of ATProto removes a lot of friction in building and c…

I think there is a sort of thing built on top of Git where the wiki and issues are actually part of the repo itself, I forget the name, a bit like the Fossil SCM.

git-annotate uses git notes and embeds a webserver for the frontend

Looks like a hobby project that made it out of Google and into open source. Not really worked on, but very cool concept

Re: Tangled, a Git collaboration platform built on atproto

#78

Post by qudat »

zoobab wrote: post #54
qudat wrote: post #25

This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…

There is stagit as well, but it does not support branches: https://codemadness.org/stagit.html Does Pgit support branches?

Yes it lets you generate a tree for any revision

Re: Tangled, a Git collaboration platform built on atproto

#79

Post by jrm4 »

I'm increasingly becoming convinced that atproto is pointless. Federation is good, but this idea of implementing "take everything with you" at the protocol level is unnecessarily complicated and centralizing. With Bluesky it might make a little more sense, but with Git? So many better, easier options here. Archive your repo and a) learn how to the do the real decentralized thing OR b) make your own centralized thing OR c) just move to Gitlab or similar.

"Take everything with you" is just downstream from "find or be a trustworthy node."

Post reply on HN