Index labels #9

initial thoughts https://bsky.app/profile/bad-example.com/post/3maljpxicgs2w

terminology mapping, label spec -> constellation

• source -> linker DID
• subject -> subject (at-uri of labeled record or DID of labeled account)
• value -> no direct analogue

colliding constellation terminology

• source: combination of collection NSID and and record path to the location of a link

at a high level, constellation should put the labeler DID in the source position, with value in the backlinks list (a single labeler can put multiple labels on one account or piece of content)

low-level details still tbd.

labels can mostly use the same exposed APIs as backlinks. where they will need special treatment:

• discovery: labelers need a special DID document; we can look for those in PLC and in the firehose
• firehose: rksy-relay implements label relaying (how does it do discovery?)
• consumer: translate labels into the fields constellation uses? validate label signatures? turn negation into deletion
• APIs: join labels into responses that include record references? obey some basic labelling stuff like bsky appview does?