forked from
tangled.org/core
Monorepo for Tangled
blog: vouching on tangled
Signed-off-by: oppiliappan <me@oppi.li>
authored by
oppiliappan
and committed by
Tangled
6e54dc8b
a98f4306
+93
+93
blog/posts/vouching.md
+93
blog/posts/vouching.md
···
1
+
---
2
+
atroot: true
3
+
template:
4
+
slug: vouching
5
+
title: combat LLM spam by building a web of trust
6
+
subtitle: vouching on tangled!
7
+
image: https://assets.tangled.network/vouch.png
8
+
date: 2026-05-01
9
+
authors:
10
+
- name: Akshay
11
+
email: akshay@tangled.org
12
+
handle: oppi.li
13
+
draft: false
14
+
---
15
+
16
+
<picture>
17
+
<img class="h-auto max-w-full" src="https://assets.tangled.network/vouch.png">
18
+
</picture>
19
+
20
+
Tangled now has native support for
21
+
[vouching](https://github.com/mitchellh/vouch/)! You can
22
+
vouch or denounce users that you interact with. Vouched
23
+
users will have a green shield icon beside their profile
24
+
pictures, and denounced users will have a red one. You can
25
+
use this to inform decisions about an interaction. You can
26
+
also see the vouch/denounce decisions made by your circle.
27
+
28
+
## why vouch?
29
+
30
+
Vouching serves as a signal of trust to your circle.
31
+
32
+
The bar to submit code to a project has never been lower
33
+
thanks to LLM based tooling. LLM tools are really good at
34
+
creating "uncanny valley" submissions. Code that looks
35
+
correct but is subtly wrong. The onus is on maintainers to
36
+
now take the time to review such submissions. To ease this
37
+
burden, maintainers from across the Tangled network can now
38
+
vouch for or denounce contributors that misuse these tools
39
+
and create a maintenance burden.
40
+
41
+
## mindful design
42
+
43
+
Such systems need careful consideration. Vouching on Tangled
44
+
includes the following to begin with:
45
+
46
+
- vouching/denouncing with a text-based reason field
47
+
- attenuation: you can only view decisions made by you and
48
+
your circle
49
+
- no consequences to being denounced: at present, denounced
50
+
users aren't blocked from the project, but simply have a
51
+
red warning label in parts of the UI
52
+
53
+
Some additions that I want to put in down the line:
54
+
55
+
- decay of vouches: maintainers and contributors tend to
56
+
move on from projects over time, so vouches should decay
57
+
as time passes, and be renewed every now and then
58
+
- evidence trails: vouching for a user right after merging a
59
+
PR should add the PR to the vouch record as a piece of
60
+
evidence
61
+
62
+
<picture>
63
+
<img class="h-auto max-w-full" src="https://assets.tangled.network/vouching-hats.png">
64
+
</picture>
65
+
66
+
## how it works
67
+
68
+
When you vouch for or denounce somebody on Tangled, you
69
+
create a **public** record on your
70
+
[PDS](https://atproto.com/guides/glossary#pds-personal-data-server).
71
+
The record includes:
72
+
73
+
- whether you vouched for or denounced somebody
74
+
- an optional reason for doing so
75
+
76
+
The Tangled appview then aggregates vouch data from across
77
+
the network, and displays vouch "hats" over profiles at
78
+
points of interaction:
79
+
80
+
- in issues and issue comments
81
+
- in pull-requests and pull-request comments
82
+
83
+
A hat appears over a user only if you have directly
84
+
vouched/denounced them, or if somebody you have vouched for
85
+
has vouched/denounced them.
86
+
87
+
Additionally, there are no consequences for a denounced
88
+
user. Only a hat. You can click on the hat to see who
89
+
vouched/denounced this user in your circle. The consequences
90
+
may change eventually, but for now you can use the hat to
91
+
inform a decision.
92
+
93
+
Start building your web of trust on Tangled today.