jdev - 2022-05-28

how can it be that in decades of xmpp, we still dont have a mechanism to search some service with paged results

Talking about `disco#items` + RSM?

is this a xep?

or xep 0055, also has no paging

https://xmpp.org/extensions/xep-0059.html has example use with 0055 even

oh thats nice

Whether this is implemented and deployed, I have no idea.

Didn't we discuss the difficulty in determining which combinations of other XEPs and RSM were available a while ago?

and https://xmpp.org/extensions/inbox/disco-feature-attachment.html

Something like pubsub#rsm, the 'rsm' feature not meaning much by itself

hm its just important for me that the spec exists

if a user complains that his client locks up because the server spams us with 5000 entries

i guess i point them to the server project to complain

:D

How many entries fit in the common stanza limit?

Which number did the newer MUC search have again?

https://xmpp.org/extensions/xep-0433.html

Well you could avoid querying that many results if you could know you won't be able to do rsm. If it were the case I'd blame gajim not the server

does this mandate RSM?

(or you could tell the user beforehand)

I see, that my PEP node uses type "headline" for its messages. I don't have a problem with that, but I wonder, if other types would make any difference?

debacle, that's for notifications

debacle, pubsub#notification_type is a thing you can search xep0060 for

_transient_ notifications, where you don't care about storage (in the receiving users's archive) ✏

i guess nobody implements the channel search

client? search.jabber.network does it, but it also has a HTTP variant which might be better for privacy

yeah jabber.network is fine for global search

what im trying currently to solve is local muc search

I once started on a very basic implementation of xep-0433 for local MUC search. Don't think it has RSM tho, but I would have to go check.

Oh, no, it's based on the protoXEP 🙁

i dont instantly see what the advantage over 0055 is

the advantage is not having to deal with `<reported>` like in https://xmpp.org/extensions/xep-0055.html#example-9

and a nice feature is the "types" field

this allows the client for example to query matrix / muc / irc room via the same endpoint

Maranda, ^ i want to make local muc search better, but especially with servers like yours which offers matrix bridge for example thats also searchable this xep would be a much better fit than xep-0055

which one?

https://xmpp.org/extensions/xep-0433.html

🤔

notice the types field, which should be implemented on server side, to show all queryable muc services

and of coruse RSM is a must

Implementing RSM pagination is rather complex but I'll have a look

.

Might get weird if you don't have a stable order to go by

pep. Zash I see, thanks! The only alternative to `headline` is `normal`, but the former is just fine for me, because "most existing server implementations will prevent offline storage", according to XEP-0060.

Other types might make sense for certain applications.