tangled.org
anirudh.fi
+94
pages/blog/6-months.md
+94
pages/blog/6-months.md
···
1
+
---
2
+
atroot: true
3
+
template:
4
+
slug: 6-months
5
+
title: 6 months of tangling
6
+
subtitle: new domain, a quick recap, and notes on the future
7
+
date: 2025-09-17
8
+
image: /static/img/logo_with_text.jpeg
9
+
authors:
10
+
- name: Anirudh
11
+
email: anirudh@tangled.sh
12
+
handle: icyphox.sh
13
+
- name: Akshay
14
+
email: akshay@tangled.sh
15
+
handle: oppi.li
16
+
draft: true
17
+
---
18
+
19
+
Hello Tanglers! It's been over 6 months since we launched Tangled, so we
20
+
figured we'd do a quick retrospective on what we shipped and what's
21
+
next.
22
+
23
+
But before that, we've got a big announcement!
24
+
25
+
## tangled.sh is now tangled.org!
26
+
27
+
Yep! We managed to get the tangled.org domain thanks to [Chris
28
+
Maytag](https://bsky.app/profile/cpm5280.bsky.social) who very kindly
29
+
let us have it!
30
+
31
+
We're still in the process of migrating and there may be stray
32
+
references to the .sh domain in places so bear with us. Rest assured:
33
+
your current links to tangled.sh will be redirected to tangled.org.
34
+
35
+
## new logo and mascot: dolly!
36
+
37
+
Tangled finally has a logo! Designed by Akshay himself, Dolly is in reference to the first ever *cloned* mammal.
38
+
39
+
40
+
41
+
## major platform highlights
42
+
43
+
One of the first major features we built was our pull requests system,
44
+
which follows a unique round-based submission & review approach. This
45
+
was really fun to innovate on -- it remains one of Tangled's core
46
+
differentiators, and one we plan to keep improving.
47
+
48
+
In the same vein, we're the first ever code forge to support [stacking
49
+
pull requests](/stacking) using Jujutsu! We're big fans of the tool and
50
+
we use it everyday as we hack on
51
+
[core](https://tangled.sh/@tangled.sh/core). Ultimately, we think
52
+
PR-based collaboration should evolve beyond the traditional model, and
53
+
we're excited to keep experimenting with new ideas that make code review
54
+
and contribution easier!
55
+
56
+
CI was our most requested feature, and we spent a *lot* of time debating
57
+
how to approach it. We considered integrating with existing platforms,
58
+
but none were good fits. So we gave in to NIH and [built spindle
59
+
ourselves](/ci)! This turned out great -- we could go all in on Nix and
60
+
make it "atproto native". It also attracted a chunk of the Nix crowd,
61
+
which we're very happy about!
62
+
63
+
Spindle is still early but designed to be extensible. The current
64
+
Docker-based engine is limiting -- we plan to switch to micro VMs
65
+
eventually. Meanwhile, if you've got ideas for other spindle backends
66
+
(Kubernetes?!), we'd love patches!
67
+
68
+
A rather large change we recently introduced was a complete migration of
69
+
the knotserver to an [XRPC](https://atproto.com/specs/xrpc) API.
70
+
Alongside this, we also decoupled the knot from the appview by getting
71
+
rid of the registration secret, which was centralizing. Knots (and
72
+
spindles) simply declare their owner, which any appview can verify. Once
73
+
we stabilize the [lexicon definitions](lexicons) for these XRPC calls,
74
+
building clients for knots (or entire appviews!) should become much simpler.
75
+
76
+
[lexicons]: https://tangled.sh/@tangled.sh/core/tree/master/lexicons
77
+
78
+
Issues got a major rework too! They are now threaded: top-level comments
79
+
with replies. This makes Q/A style discussions much easier to follow!
80
+
81
+
82
+
83
+
## the future
84
+
85
+
We're working on a *lot* of exciting new things and possibly some big
86
+
announcements to come. For the next 6 months, the primary focus will be
87
+
on these fronts:
88
+
89
+
* labels support for issues
90
+
* notifications: both in-app and emails
91
+
* preliminary support for issue and PR search
92
+
* total federation and network playback
93
+
94
+
That's all for now; we'll see you on the atmosphere!
static/img/issue-threading.webp
static/img/issue-threading.webp
This is a binary file and will not be displayed.
static/img/logo_with_text.jpeg
static/img/logo_with_text.jpeg
This is a binary file and will not be displayed.