forked from
tangled.org/core
Monorepo for Tangled
1---
2atroot: true
3template:
4slug: newsletter-01
5title: newsletter 01 — hello!
6subtitle: kicking off our newsletter!
7image: https://assets.tangled.network/blog/newsletter-01.png
8date: 2026-04-16
9authors:
10 - name: Anirudh
11 email: anirudh@tangled.org
12 handle: anirudh.fi
13---
14
15*This was originally sent as an email.*
16
17
19
20Hello Tanglers! We're excited to kick off the first ever issue of our
21newsletter. We haven't settled on a cutesy name for it yet --
22"untangled"? Or simply "tangled weekly"? Let us know!
23
24If you're new here (how'd you end up on our list?!), Tangled is a new
25social coding platform. You can host Git repositories, collaborate with
26friends, and self-host your git remotes
27([knots](https://docs.tangled.org/knot-self-hosting-guide.html)) and CI
28runners (spindles). We recently raised €3,8M ($4.5M) in [seed
29financing](/seed) and have been heads-down building.
30
31With that out of the way, here's what we shipped recently.
32
33## Repository search is live
34
35
37
38We finally have it. You can now search for your favourite slopware at
39[tangled.org/search](https://tangled.org/search) (or from the 🔍 icon in
40the top nav).
41
42## Fresh new OpenGraph images
43
44
45
46[Étienne](https://tangled.org/eti.tf) helped us ship `ogre` -- the new
47OpenGraph Rendering Engine. It's what's behind our lovely link previews
48that you may have seen elsewhere already.
49
50## PR review improvements
51
52
53
54[Lewis](https://tangled.org/oyster.cafe), our most recent addition to
55the team (based out of Helsinki!), shipped these handy PR review
56improvements! You can multi-line select to reference relevant code in
57review comments, and mark files that you've already looked at as
58"reviewed". Nifty!
59
60## knotmirror and other planned features
61
62[Seongmin](https://tangled.org/boltless.me), our engineer from South
63Korea 🇰🇷, built our new repository indexer service: knotmirror.
64
65Knotmirror is our first of many performance optimizations for repo
66viewing & fetching on tangled. It attempts to fetch and index all known
67git repos across knots, allowing the appview (the main service at
68tangled.org) to serve repos much faster, regardless of where your knot
69lives!
70
71Up next, we're working hard towards:
72
73* First implementation of **VM-based CI** to enable more advanced
74 workflows. This will be a new spindle engine likely backed by QEMU. At
75 least initially. We'll let you know when we ship it!
76* **Vouching**: Tangled aims to be foundational infrastructure for the
77 future of open source dev -- and having first-class tooling for the
78 slopocalypse is paramount. The web-of-trust model has proven to be
79 rather powerful here and that's coming to Tangled very soon.
80* Fully achieve full **AT Protocol compliance**. One of our internal
81 goals is to have a Tangled appview that anyone can run, with complete
82 backfill and ingestion -- dubbed the "ephemeral appview". We're not quite
83 there yet: repos are the tough part. We recently swapped to using DIDs
84 to identify repos, which gets us one step closer to being able to
85 rename them, transfer them between knots, and finally ingest them
86 through the firehose.
87
88That's all for now! We'd love to hear your thoughts on this newsletter
89-- you can reply to this email or join our
90[Discord](https://chat.tangled.org) to let us know. We'll also publish
91this on our blog for those that prefer RSS.
92
93-- Anirudh