Live data from Hacker News

Gleam Is Now on Tangled

tangled.org

31–40 of 162 posts

Re: Gleam Is Now on Tangled

#31
post #16

Earlier quoted context omitted.

> GitHub's moat is not code hosting Of course not, it’s the number of people who are already signed up. Instagram’s moat also most certainly isn’t a scrollable photo timeline.

There's more to it than the number of people. Actions, GitHub apps/external integrations, identity/permission management The most significant, near-term, non-moaty gap is still private repos, which isn't all that big of a feature on the surface, but will have major work under the surface because of how bluesky is designing private spaces. I also think being primarily nix/jj focussed turns a lot of people away. Those…

I see it attracting more people than it dissuades. You can use jj as just a prefix for Git commands like jj git init. Yet you get supercharged repo navigation abilities. If obscelecene is your concern, jujutsu is VCS agnostic and doesn't have to use Git in the future.

Nix is as simple as it gets, even better than docker. Just 'nix run' whatever flake file someone gives you and everything works magically.

This codeforge going away can't happen for me because I self-host it.

Re: Gleam Is Now on Tangled

#32
post #8

if anyone has more info on tangled would love to hear. been looking for a decentralized git provider for a while. started self hosting but was missing the social element

[Radicle]( https://radicle.dev/ ) gets a wee bit closer. It’s selfhostable and federated. You’ll have a hard time finding something with the same social gravity well as GitHub; it remains to be seen whether that’s a separable element or if it needs to ship as part of the forge itself.

This looks like a much more sensible design for code repos: all the artifacts live in the repo.

Re: Gleam Is Now on Tangled

#33

Earlier quoted context omitted.

Why Tangled instead of something more established like Codeberg, or if f/loss, Forgejo or Gitea? Just because ATProto vibes?

It also has a pretty fundamental design flaw: issue /PR comments belong to the server where the commenter is hosted, not to the repo. I’m sure they will find a workaround but finding that reduced confidence they actually understand the problem they are solving.

this is changing very soon :)

see knot2[0] for some initial experiments: https://tangled.org/oyster.cafe/knot2

> As time goes on we are re-assessing the idea of users owning what is "collaborative data" (issues, PRs, etc.) on their PDSes - soon may come the day that an issue also lives on the knot as a source of truth, with an accompanying pointer record on user PDS to attest that it's theirs

Re: Gleam Is Now on Tangled

#34

Wish a git forge would support both Actions and Gitlab CI pipelines. Reuse community workflows for simple actions, default to Gitlab CI for anything custom.

the way the CI runners on tangled work, you could just plug in your own bespoke runner as long as it fits the interface. we implement two such "engines": nixery and microvm. you can plug an engine like tack[0], which can act like a bridge interface to other CI systems. there is also loom[1], which is a kubernetes based engine. [0]: https://tangled.org/mitchellh.com/tack [1]: tangled.org/evan.jarrett.net/loom

The problem is that interface isn't enough when in Gitlab the CI natively integrates with other systems, like test reports displaying results in merge requests. This would certainly enable hybrid pipelines through.

Re: Gleam Is Now on Tangled

#35

This post needs a bunch more context; right now it's only immediately accessible to people who don't need the announcement [1]. [1] https://knowyourmeme.com/memes/curtains-for-zoosha

Headline reminds me of Poob. https://knowyourmeme.com/photos/3056633-poob-has-it-for-you

The fact that I know what both Gleam and Tangled are in this context means I spend too much time on HN and not enough time doing useful things.

Re: Gleam Is Now on Tangled

#36

Earlier quoted context omitted.

Why Tangled instead of something more established like Codeberg, or if f/loss, Forgejo or Gitea? Just because ATProto vibes?

It also has a pretty fundamental design flaw: issue /PR comments belong to the server where the commenter is hosted, not to the repo. I’m sure they will find a workaround but finding that reduced confidence they actually understand the problem they are solving.

We’re solving for this very issue. Issues & pulls will belong to the repo, backed by a “COB” (collaborative object) system.

Re: Gleam Is Now on Tangled

#38
post #7

Earlier quoted context omitted.

The irony of that linked page dragging a reposted mid tweet into multiple scrollable pages of “content” and in doing so reading exactly like a celeb news article

Yeah, it turns out human culture has a lot of depth and complexity, even so-called "mid" culture. If you think you can write a better explainer, I'd love to read it.

I absolutely could, by removing everything past the first 3-5 sentences in the article. But that probably wouldn’t satisfy the site owner’s desired metrics and SEO targeting.

Re: Gleam Is Now on Tangled

#39
I just tried out tangled for the first time and unfortunately it seems buggy beyond being actually usable. I created a repo but can't look at it because I get a 404 for it. The login was quite painful as well as I needed several attempts to enter my atproto handle (copy-pasted every time, so no typo). But I'm glad more people are working on git hosting options.

Re: Gleam Is Now on Tangled

#40
post #8

if anyone has more info on tangled would love to hear. been looking for a decentralized git provider for a while. started self hosting but was missing the social element

[Radicle]( https://radicle.dev/ ) gets a wee bit closer. It’s selfhostable and federated. You’ll have a hard time finding something with the same social gravity well as GitHub; it remains to be seen whether that’s a separable element or if it needs to ship as part of the forge itself.

I’ve been testing Radicle and it’s more focused on the distributed protocol for federating git repos, I.e. the data plane. The social / coordination control-plane angle is really thin, following users and repos goes by opaque IDs, etc.

It could be a better solution for agents that don’t bounce off such mundane complexity. It could be better for private repo federation (eg private collective or agent swarm.)

I’m interested in Tangled for the OSS/community aspect, it seems to have an advantage there with the richer identity layer for humans.

Post reply on HN