XSF Discussion - 2019-11-01

still feel we should do something about the MAM stanza-id rules

right now it says the id must be unique within an archive

which is good, i hope all server implementations considered the case that the server database is wiped or server is new setup

the new ids in the new installation must not clash with old ids from the old installation

because only because i wipe a database on the server does not mean its wiped on the client

i know ejabberd uses a timestamp

dont know what prosody uses

probably a uuid so also fine

jonas’: do you relay on roominfo_occupants or do you do a disco items on the room or something?

I would guess the former

Related: Prosody doesn't return occupants on disco#items anymore for privacy reasons.

Daniel, asking because the number is not what you expect?

> Daniel, asking because the number is not what you expect? I'm about to find out

It's a floating number, it's not accurate at all times

That's on purpose

Moving average iirc

Right that

Ah. On the search you mean. No thats fine.

I'm discoing my own server and are wondering if I can actually do something useful with that number

> Related: Prosody doesn't return occupants on disco#items anymore for privacy reasons. All rooms or just private ones?

All.

Code deleted is best code.

sight. i never wanted to implement 'local muc' discovery because I thought it would be 95% garbage/empty or unaccesible mucs. however it might be useful for some very special in-house deployments and therefor I implemented it; now i’m frustrated about seeing 95% garbage mucs on the servers that i've tested this with…

Mmmmmmmmmmmyeah.

I had toughts about garbage collection

Can I discover that I have admin priveleges on the server?

Maybe

Thinking out loud over a 'destroy channel' in the context menu of that search

Without having to join first

In theory, I think there's something in xep-0030 for admin accounts

Also I'm wondering if disco#items on ejabberd lists unlisted rooms that I created

Just because I'm wondering why there are so many in my own server

https://xmpp.org/registrar/disco-categories.html#account

Doesn't look like Prosody does that tho :(

I don't know about ejabberd

Daniel: Prosody does however expose an ad-hoc command on MUCs to admins for destroying rooms

Is that different to normal destroy?

Daniel: It allows destroying multiple rooms at once. Does the same thing internally tho.

Why are there so many rooms on various public servers that look like the ones auto generated by Conversations. Does the unlisted thing not work?

Hm?

To people deliberately use gajim to make them listed

What is going on

Example?

Conversations create group chat has a way of creating random local parts

Daniel, public_list is a custom setting on ejabberd

i dont think prosody even has one

What?

Now I'm confused

at least my code uses "public_list" in room creation

maybe i missed a official option for that?

Daniel: Can you (ev privately) point me at a public server that shows this?

It's called publicroom

I'm not seeing a lot on the random few I looked at

muc#roomconfig_publicroom

indeed

whats public_list then on ejabberd

something different probably

(Fun fact: It's called 'hidden' internally in Prosody and set to the opposite of muc#roomconfig_publicroom)

Zash, never mind. maybe it wasn’t that many after all. on a mobile screen even ~5 look like a lot

Heh.

ah public_list on ejabberd is to hide the member list

so you can make the room searchable but dont query who is in it

https://xmpp.org/extensions/xep-0045.html#disco-roomitems MAY for a somewhat redundant thing, you get all that via presence when you join ✏

i mean browse through the last pages of muclumbus https://search.jabber.network/rooms/29 and you see a few of them (vowel and consonant alternating) - but in the grand scope of things it's probably 'ok' to see a few

Can it be changed trough Conversations?

If it's at all possible to flip the 'public' switch then some people will find out and do it.