zlacker

[return to "Vouch"]
1. abraco+nt1[view] [source] 2026-02-08 17:42:48
>>chwtut+(OP)
Isn't it extremely difficult problem? It's very easy to game, vouch 1 entity that will invite lots of bad actors
◧◩
2. dboon+8v1[view] [source] 2026-02-08 17:53:28
>>abraco+nt1
You can't get perfection. The constraints / stakes are softer with what Mitchell is trying to solve i.e. it's not a big deal if one slips through. That being said, it's not hard to denounce the tree of folks rooted at the original bad actor.
◧◩◪
3. anupam+zA1[view] [source] 2026-02-08 18:30:12
>>dboon+8v1
> The interesting failure mode isn’t just “one bad actor slips through”, it’s provenance: if you want to > “denounce the tree rooted at a bad actor”, you need to record where a vouch came from (maintainer X, > imported list Y, date, reason), otherwise revocation turns into manual whack-a-mole. > > Keeping the file format minimal is good, but I’d want at least optional provenance in the details field > (or a sidecar) so you can do bulk revocations and audits.
[go to top]