XSF Discussion - 2018-03-09

flow: now that MUCs SHOULD retain message @ids, would you remove <origin-id> from 0359? :)

and then we’re gonna burn 0359 and re-integrate stanza-id into MAM?

+ a "Best Practices for Message IDs" informational XEP referenced from all the XEPs which reference message IDs

jonasw: awesome idea

"This document is a patch of RFC 6120" ;)

i.e. "use at least 120 bits of entropy, however you do that. a uuid4 is fine, if seeded from a proper CSPRNG"

"please don't use hex-encoding"

doesn’t matter, in the end. if implementations have easy access to a CSPRNG-seeded uuid4, I prefer them using that over building their own thing which uses rand()

Lazy but effective

I still hate the 50% bit efficency of hex encoding.

I do too

and uuids don’t improve that with their dashes

Right.

getrandom | base64 is my favourite, but yeah.

urlsafe base64 probably

But this is probably a sign of the times, where people bundle a 500KB JavaScript application into a 700MB runtime

or implement IM clients whose core message view component is a browser engine.

it's webviews all the way down

yeah

(tbf, I plan to implement a non-webview thing optionally for the type of folks who prefer compact monospaced things)

no embedded youtube for those then though!

jonasw: you can add another [X] into https://github.com/xsf/xeps/issues/601 ;)

t

so how should a modern client pick it’s resource?

generate a random ID (4-6 chars) and use "$clientname.$randomid"?

jonasw, that's my personal preference these days

(for extra fubar, I could use emoji as random ID :-)) ✏

Even though I spent years telling Ge0rG he was wrong

for this, and for sending to bare JIDs

Yes that's what I'm doing

what did change your mind about the resource thing?

3 bytes random in base64

That's four chars

jonasw, the realisation that the server can override it, so it really doesn't matter - and it's useful for tracking devices

right

My preference would be that bind2 comes along with a device-id built-in

But until that day, this works fine (and is backwards-compatible with all the clients that allow manual resources)

I just use a fixed resource string.

Holy war!

Server developers will always win this one

MattJ: server developers might have the bigger lever, but they don't win by just applying it

They can make life miserable for everyone, but in my book that's not synonymous to "win

and here I thought the definition of "to win" was "to make life miserable for everyone who lost"

MattJ: I'd say "to win" also includes making life better for yourself

Unless you are in for the game.