XSF Discussion - 2020-08-08

XEP-0084 historical thread: https://mail.jabber.org/pipermail/standards/2005-April/007439.html

Doesn't explain the PNG-only change, but clarifies that other formats were expected to be fallbacks

this must be an oversight or mistake, maybe it was by accident

I haven't read it as png only. Rather that one of the possibility multiple formats must be png, but you can publish alternative formats

The first point in section 3 says: "1. User publishes avatar data for "image/png" content-type to data node and optionally publishes other content-types to HTTP URLs."

That sounds very much like only PNG data is welcome in the PEP node, and the rest of the doc seems to back up such an interpretation

Meh.

Pointless limits, let's remove them. Mandating that at least one format be widely supported is good, but today jpeg and gif should be fine along with png.

serious question: why would you want to have your avatar in multiple formats? shouldn't png just always be fine?

Jpeg deals better with photos

webp

But you could also have a higher resolution available as alternative version

webp doesn't work everywhere

You could have it as alternative format if you wanted

Or you could have png+svg.

heif

make svg required and then don't base64 encode the svg, but just embed it. If you still wanted to use other image formats, you can embed them in svg

larma, why though seems complicated

i read a file from my harddisk in bytes, pass it to the b64encode and im finished, i dont have to care if that svg is valid xml at all

i dont want to care if something is a svg, then i have to read, decode it, add the xml to as child etc, and if its another format i have to base64 encode it .. make everything just more complex

for a bit less size on a payload which is rarley requested at all

also png is fine as almost all supports it

its the other way around, publish png, and if you want something more add other formats

flow, on desktop we often deal with hidpi displays

we need to scale the avatar x2 or even x3

svg solves that nicely

So why not have the ability tp publish a higher resolution along with the mandated 96x96 png or whatever

you have this ability already Zash

its just that other formats are not allowed than png

for me the optimal case is

Wasn't it just argued that you could only have one item?

user selects a svg, i publish a png in 100x100 or something, and add the svg in a second avatar info, so clients that support svg can use that

where Zash?

The XEP says the <data> node is only for PNG

That. That's silly.

i know

and mostly ignored anyway

The part MattJ quoted

So let's update it to be sane?

i remeber a time when C only published in webp

yes the part that MattJ quoted, says other "content-types"

The way we usually handle this is "You must publish X, you may optionally publish other things"

you can post image/png in 100 resolutions if you want to pep

but not another content type

What's the point of a info/@type attribute if the only option is png?

I'd be happy with even a SHOULD support PNG, it's tricky hard-coding something here that may evolve over time (when the rest of the documented protocol would hold up fine)

MattJ, yes, that

Like with hash algos

but it already has a MUST

> and one of the formats MUST be "image/png" to ensure interoperability

can we not just remove the word "only"

its not normativ language

so i guess the creator didnt think this is important anyway

we just remove that part "and only for the "image/png" content-type"

from 4.1

Sounds good to me

“12:35:32 flow> serious question: why would you want to have your avatar in multiple formats? shouldn't png just always be fine?”, SVG is much smaller for vector data, and can work at arbitrarily high resolutions.

“12:43:45 Daniel> heif”, all desktop clients will soon support it with AV1 inside (AVIF), when the user has libavif installed. :)

Alex, I did it, >24h before the period ended!!

Alex, many thanks for the reminder 🙂

,👍👍

!XSF_Martin, oh we're applying together. So you gotta change your nick once your application is accepted.

!!XSF_Martin.

Link Mauve, don’t forget your application :)

Have any xmpp based tech companies ever donated back to xmpp?

I.e. WhatsApp kik etc.