Update 2.2 schema to support atprotocol protocol and record usage #100
Conversation
|
Yes! Great idea and contribution. Bridgy Fed added |
| "minProperties": 0, | ||
| "additionalProperties": { "type": "integer", "minimum": 0 }, | ||
| "properties": { | ||
| "app.bsky.feed.post": { |
There was a problem hiding this comment.
Hmm! This sounds the same as localPosts, right? Seems like it'd maybe be better to keep all of these stats protocol-independent and unified...? I know that means we might not get as much nuance about each specific protocol, but the goal here probably isn't to be comprehensive or exhaustive anyway.
There was a problem hiding this comment.
Maybe this denotes a 2.3 change, but I think limiting metrics to just post types should be deprecated. It's time to push for an expanded and more generic record-type container.
There was a problem hiding this comment.
Sure! More metrics sounds great, and I'm with you that ideally they should be generic, like you mention, instead of protocol-specific like this.
This PR introduces two changes to the 2.2 schema to support atprotocol nodes.
The
atprotocolenum was introduced to allow ATProtocol Data Repositories to announce themselves usingGET /.well-known/nodeinfo.The
usagestructure was updated to include therecordsobject which is a string to integer key/value pair object for reporting collection statistics. Within ATProtocol, namespaced identifiers are used to identify collections of records. This structure allows personal data server (PDS) instances to self-report the number of records it contains across all repositories (account) across collections.