Add initial metadata registry #244
Conversation
No need to restrict this. I’m already using smaller ones. |
|
Yeah it's a bit interesting. Are we just gonna allow people to use any number there? Do regular image/avatar hosting services that allow receiving a resized image usually support any number, only multiples of 2, etc? |
|
I’ve seen hosts that accept any number (gravatar, IRCCloud) and some that round numbers to the nearest checkpoint (slack I think?) I’m sure others would just ignore unknown numbers. All cases fallback to showing an image at least. |
|
Sounds good, I'll adjust it. If need be we can suggest requesting again with different sizes down the line or w/e |
|
Cool. Might be worth mentioning that it’s a standard URI template that can be filled in with widely available libraries https://tools.ietf.org/html/rfc6570 |
| values: | ||
| - key: avatar | ||
| description: Avatar that graphical clients can show alongside the user's name | ||
| format: URL with an optional `{size}` substitution denoting the size to load in pixels |
There was a problem hiding this comment.
Original issue stated "square dimension" so both.
Based on ircv3/ircv3-specifications#336
Travis fails on this because the yaml checker's a bit silly and fails with emoji (i wil fix dat). Otherwise, this feels like what we want out of a metadata registry yeah?