success:
true
identity:
@context:
alsoKnownAs:
verificationMethod:
type:
"Multikey"
controller:
"did:plc:l3rouwludahu3ui3bt66mfvj"
publicKeyMultibase:
"zQ3shbzd9YoCFQrzfdw2AGpxUHTjUhh69MXRh7hHBavx9wQon"
service:
id:
"#atproto_pds"
type:
"AtprotoPersonalDataServer"
serviceEndpoint:
"https://morel.us-east.host.bsky.network"
cid:
"bafyreigde4l2gadnz422fnu5oyypoxim4t2bo5hajx5pb777f3dr5wsj3i"
value:
text:
"yes! though i also think @tom-sherman.com might be on to something here. we could still bidirectionally link client metadata with a published record (optionally). then perhaps we could safely show developer details in the oauth flow. only concern i have is that it overloads the use of domains a bit."
$type:
"app.bsky.feed.post"
langs:
"en"
reply:
root:
cid:
"bafyreicjtt6cr6ow72hw3bjps5qggdxdnnfps26h7esojs23lm6r6biagm"
parent:
cid:
"bafyreicbrinkd2h2ofbczulmyqyss42w44bmhzkwtecivxbww5jyx4n2di"
facets:
$type:
"app.bsky.richtext.facet"
index:
byteEnd:
41
byteStart:
25
features:
$type:
"app.bsky.richtext.facet#mention"
createdAt:
"2024-09-11T14:33:22.424Z"