tangled.org
engineering blog at https://blog.tangled.sh
minor rewording
Signed-off-by: oppiliappan <me@oppi.li>
oppi.li
+1
-1
input.css
+1
-1
input.css
+26
-26
pages/blog/6-months.md
+26
-26
pages/blog/6-months.md
···
16
16
draft: true
17
17
---
18
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.
19
+
Hello Tanglers! It's been over 6 months since we first announced
20
+
Tangled, so we figured we'd do a quick retrospective on what we built so
21
+
far and what's next.
22
22
23
23
But before that, we've got a big announcement!
24
24
25
25
## tangled.sh is now tangled.org!
26
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!
27
+
[Chris Maytag](https://bsky.app/profile/cpm5280.bsky.social) very kindly
28
+
let us have the tangled.org domain!
30
29
31
30
We're still in the process of migrating and there may be stray
32
31
references to the .sh domain in places so bear with us. Rest assured:
···
34
33
35
34
## new logo and mascot: dolly!
36
35
37
-
Tangled finally has a logo! Designed by Akshay himself, Dolly is in reference to the first ever *cloned* mammal.
36
+
Tangled finally has a logo! Designed by Akshay himself, Dolly is in
37
+
reference to the first ever *cloned* mammal.
38
38
39
39
40
40
41
-
With that, let's recap the major platform highlights so far!
41
+
With that, let's recap the major platform improvements so far!
42
42
43
43
### pull requests
44
44
···
61
61
how to approach it. We considered integrating with existing platforms,
62
62
but none were good fits. So we gave in to NIH and [built spindle
63
63
ourselves](/ci)! This turned out great -- we could go all in on Nix and
64
-
make it "atproto native". It also attracted a chunk of the Nix crowd,
65
-
which we're very happy about!
64
+
make it "atproto native".
66
65
67
66
Spindle is still early but designed to be extensible. The current
68
67
Docker-based engine is limiting -- we plan to switch to micro VMs
69
68
eventually. Meanwhile, if you've got ideas for other spindle backends
70
-
(Kubernetes?!), we'd love patches!
69
+
(Kubernetes?!), we'd love to [hear from you](https://chat.tangled.sh).
71
70
72
71
### XRPC APIs
73
72
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.
76
-
Alongside this, we also decoupled the knot from the appview by getting
77
-
rid of the registration secret, which was centralizing. Knots (and
78
-
spindles) simply declare their owner, which any appview can verify. Once
79
-
we stabilize the [lexicon definitions](lexicons) for these XRPC calls,
80
-
building clients for knots (or entire appviews!) should become much simpler.
73
+
We introduced a complete migration of the knotserver to an
74
+
[XRPC](https://atproto.com/specs/xrpc) API. Alongside this, we also
75
+
decoupled the knot from the appview by getting rid of the registration
76
+
secret, which was centralizing. Knots (and spindles) simply declare
77
+
their owner, and any appview can verify ownership. Once we stabilize the
78
+
[lexicon definitions](lexicons) for these XRPC calls, building clients
79
+
for knots, or alternate implementations should become much simpler.
81
80
82
81
[lexicons]: https://tangled.sh/@tangled.sh/core/tree/master/lexicons
83
82
84
83
### issues rework
85
84
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!
85
+
Issues got a major rework (and facelift) too! They are now threaded:
86
+
top-level comments with replies. This makes Q/A style discussions much
87
+
easier to follow!
88
88
89
89
90
90
91
-
### tngl.sh PDS
91
+
### hosted PDS
92
92
93
93
A complaint we often recieved was the need for a Bluesky account to use
94
94
Tangled; and besides, we realised that the overlap between Bluesky users
···
105
105
## the future
106
106
107
107
We're working on a *lot* of exciting new things and possibly some big
108
-
announcements to come. For the next 6 months, the primary focus will be
109
-
on these fronts:
108
+
announcements to come:
110
109
111
-
* labels support for issues
110
+
* labels
112
111
* notifications: both in-app and emails
113
112
* preliminary support for issue and PR search
114
-
* total federation and network playback
113
+
* total federation
114
+
* network playback
115
115
116
-
That's all for now; we'll see you on the atmosphere!
116
+
That's all for now; we'll see you in the atmosphere!