tangled.org
engineering blog at https://blog.tangled.sh
some rewording + pds mention
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>
anirudh.fi
+24
-2
+24
-2
pages/blog/6-months.md
+24
-2
pages/blog/6-months.md
···
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
···
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
···
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
···
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.
···
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
···
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-18
8
image: /static/img/logo_with_text.jpeg
9
authors:
10
- name: Anirudh
···
38
39
40
41
+
With that, let's recap the major platform highlights so far!
42
+
43
+
### pull requests
44
45
One of the first major features we built was our pull requests system,
46
which follows a unique round-based submission & review approach. This
···
55
we're excited to keep experimenting with new ideas that make code review
56
and contribution easier!
57
58
+
### spindle
59
+
60
CI was our most requested feature, and we spent a *lot* of time debating
61
how to approach it. We considered integrating with existing platforms,
62
but none were good fits. So we gave in to NIH and [built spindle
···
68
Docker-based engine is limiting -- we plan to switch to micro VMs
69
eventually. Meanwhile, if you've got ideas for other spindle backends
70
(Kubernetes?!), we'd love patches!
71
+
72
+
### XRPC APIs
73
74
A rather large change we recently introduced was a complete migration of
75
the knotserver to an [XRPC](https://atproto.com/specs/xrpc) API.
···
81
82
[lexicons]: https://tangled.sh/@tangled.sh/core/tree/master/lexicons
83
84
+
### issues rework
85
+
86
Issues got a major rework too! They are now threaded: top-level comments
87
with replies. This makes Q/A style discussions much easier to follow!
88
89
90
+
91
+
### tngl.sh PDS
92
+
93
+
A complaint we often recieved was the need for a Bluesky account to use
94
+
Tangled; and besides, we realised that the overlap between Bluesky users
95
+
and possible Tangled users only goes so far -- we aim to be a generic
96
+
code forge after all, atproto just happens to be an implementation
97
+
detail.
98
+
99
+
To address this, we spun up the tngl.sh PDS hosted right here in
100
+
Finland. The only way to get an account on this PDS is by [signing
101
+
up](https://tangled.sh/signup). There's a lot we can do to improve this
102
+
experience as a generic PDS host, but we're still working out details
103
+
around that.
104
105
## the future
106