XSF Discussion - 2018-09-07

Would it be a stupid idea to have the muc server include the caps hash in room configuration change messages?

I have a poezio plugin that pulls the config and diffs, when there's a configuration change :x

Meanwhile, in Isode chat: Edwin I shall not mention PRECIS, shall I Kev PRECIS is a story told to frighten young children.

If you don't behave, you'll have to investigate how IDNA2003, IDNA2008 and PRECIS interacts.

😲

Do I want to know..?

there is a caps hash for rooms? Oo

didnt know that

caps hash is a function of disco#info, so why notq

Good idea imho

the benefit is not that great though

Hm, where did that come from?

are there many muc config changes that dont affect the disco?

I thought I saw an email but now I don't

if you mean why i brought up that topic, daniel asked in this room if the hash could be in the 104 status message

Ah there, hidden in a ton of joins and parts

i would say its useful if there is a common case where the hash is not changed although a 104 message was sent

There are some settings that have status codes, some that just change in disco, others that might not have anything in disco at all.

I think(?)

yeah what are those that are not in disco

for the others is a hash not useful because it would be different anyway

Duno

You wouldn't be able to get stuff by discoing anyways

wut

if i disco i expect to get a disco, what do you mean? ✏

what is the "stuff" you are talking that i dont get

If something isn't in disco, you wouldn't get it via disco

i doubt there is much in a room config, that does not affect the disco

thats why i would be interested about what frequently changed option daniel thinks

where this would allow him to skip a disco

lovetox, well first of it was just a random thought i didn’t think it all the way through. i just thought that muc configs are probably very similiar. for example most users (on my client) will probably just have the conversations default config

daniel: Name and stuff goes in there tho, so I'm assuming every room will be unique

yeah name is a problem with that

and you still have the problem to discover the hash

so it probably doesn’t buy you much

Probably doesn't hurt much either?

Benchmark or it never XEPs!! :)

would would be cool would be a way to discover the caps hash on join or something

then i don’t have to do a disco query again and again

thats to late daniel, you have to put stuff into the join presence that depends on disco

like history query if there is no MAM

yeah i know. i also run the query anway to have a reliable way of telling whether a room exists

every muc publishes the hash in a pep node, and clients subscribe :D

but anyway it feels stupid to again and again do disco#info on 10s of rooms that all have very similiar if not the same config

https://xmpp.org/extensions/xep-0230.html :D