l4.pm / atvouch
dev vouch dev on at. thats about it atvouch.dev
8
fork

Configure Feed

Select the types of activity you want to include in your feed.

tangled labels #1

open opened by
isabelroses.com

i like the idea of the bot that adds the comments, but i prefer the idea of adding labels. similar to what ghostty does since i care less about who's vouched for who but rather if they have been vouched for. maybe a tiering system could go with that like C-vouch for 3 vouches and A-vouch for like 10 or something.

l4.pm

the problem here though is that the amount of remote vouches someone has is completely useless from a trust perspective, it has to be computed from the maintainer dids. from the design decisions part of https://atvouch.dev

(1) no counters on people

because remote vouches can be created by anyone for any reason, they cannot be trusted at all. this is also why trust decisions must always be made in the context of the current logged in user (you), using a vouch chain that is localized to your specific immediate graph.

do you think it would still be useful in that case? there isn't a lot of scale at the moment

second question is how to attach labels to a pr. i would prefer tangled to get their ingester bits working properly in a way where if someone adds atvouch.dev as a collaborator (very risky op but it would be the requirement here!) it would be able to create some record that would add the label on a pr, rather than doing the current integration with the appview requiring simulated oauth flow

isabelroses.com (author)

my personal take here is that I don't particularly care whom has vouched for whom as long as they are not entirely removed from my own tree. like friends of friends on steam or akin. not sure on the complexity of that however

sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:qxichs7jsycphrsmbujwqbfb/sh.tangled.repo.issue/3mhr244zwrg22