probably the best move would be to propose a lexicon change, second best would be an off spec field that’s maybe an object for that kind of metadata
1 6if the goal is for other clients to be able to render this info then you ideally want to think very generally, like a display name and a URL
2 6fwiw I’d suggest designing the field as if it’s official; the ideal is it gets upstreamed, right?
3 6I mean I'd just expect reverse domain labeled keys with something like "com.atproto.*" being the most canonical followed by "app.bsky.*"
3 5IMHO it encourages experimentation by setting clear rules and the possibility of things being incorporated upstream.. otherwise it's a free for all.. what about PDS' adding their own labels or middle tiers? Don't want them stepping on each other's labels..
1 3100% agree. The trick is finding ways for us to avoid clobbering each other and to potentially support each other’s features and avoid blockers to doing so.
2 4Samuel
@samuel.fm
I was thinking prefixing with unspecced, to match the lexicon. So like unspeccedAttribution: {}
1 2