Gleam Is Now on Tangled

Original Article ↗ Hacker News Discussion ↗

A new mirror of the Gleam programming language on Tangled, a VC-funded, ATProto-based Git hosting platform, is prompting debate over decentralized alternatives to GitHub. Commenters weigh Tangled’s promises of federation, self-hosting, Nix-based CI, and separation of storage from identity against its current shortcomings, including missing features, confusing signup flows, bugs, and reliance on Bluesky-style authentication. The exchange highlights broader questions about sustainability, business models, and whether social, federated forges can realistically match GitHub’s ecosystem and reliability.

What Tangled Is and How It Works

  • Described as a decentralized GitHub-like forge built on ATProto (same protocol as Bluesky).
  • Separates git storage (“knots”) from identity and social data (ATProto PDS).
  • Gleam repo is now mirrored there; project remains on GitHub.

Federation, Identity, and Self‑Hosting

  • Tangled federates across instances; users can run their own knots, CI runners (“spindles”), and appviews (“bobbin”).
  • Some commenters initially thought it wasn’t self-hostable; others point to blog posts and third-party deployments as proof it is.
  • ATProto handles identity; users can self-host PDSes and are not strictly tied to Bluesky or Tangled’s infra.

Feature Set vs Other Forges

  • Compared to Codeberg/Forgejo/Gitea: Tangled is newer, missing private repos and protected branches but has a UI some prefer.
  • Compared with Radicle: Radicle focuses on protocol/data; Tangled on social/identity for OSS communities.
  • Unique features mentioned: federation, native stacked PRs, and a vouching system.

CI and Nix‑First Design

  • CI is based on Nix and microVMs; “spindles” run pipelines via pluggable engines.
  • Bridge engines can integrate with other CI systems, but deeper UI integration (e.g., test reports in MRs) is noted as missing.

Issues/PRs Data Model Debate

  • Current/early design tied issues and PR comments to the commenter’s PDS, not the repo, seen by some as a “fundamental flaw.”
  • Maintainers say this is being redesigned: issues/PRs will belong to the repo via a collaborative-object (“COB”) system.

User Experience and Stability

  • Several report signup/login friction, confusing ATProto handle formats, and password manager problems; some get outright signup errors.
  • Reports of transient 404s on newly created repos and networking issues (IPv6-only knots needing IPv4/NAT workarounds).
  • Others say login via existing Bluesky handles works smoothly.

Funding, Business Model, and Trust

  • Tangled is VC-funded with a sizable seed; some worry about lack of a clear business model and potential code-training on hosted repos.
  • Possible monetization paths speculated: paid tiers for hosting, CI, binary caches, PDS hosting, and SLAs.
  • Some argue VC funding “doesn’t matter” because everything is open source and self-hostable; critics say it still shapes incentives.

Bluesky/ATProto Dependence and Moderation

  • Concern: if Bluesky moderates/bans an account, users might lose access to their code/identity.
  • Counterpoints:
    • Moderation labels usually don’t block login.
    • Users can move to other PDSes or self-host; identity is controlled via DID and PDS, not Bluesky alone.
    • Tangled moderation is independent of Bluesky’s unless the PDS itself deletes the account.
  • Some still view tying source control to a social login provider as risky for “mission critical” use.

Perceptions, Naming, and Context

  • Many readers unfamiliar with both “Gleam” and “Tangled” find the headline opaque or satirical.
  • Others respond that HN readers can click through or search; the page and prior posts give context.
  • Mixed sentiment overall: curiosity and enthusiasm about federation/ATProto vs skepticism about complexity, buzzwords, and real-world reliability.