-
Link Mauve
(Moving from council@) “17:19:29 jonas’> we do have the luck to have a huge stash of disco#info replies from both servers and (a bit outdated) clients if you want to make a survey”, where can I find that? I also have the ones collected by poezio, but at least one third doesn’t validate, most likely because poezio forgot to put the @xml:lang in it…
-
jonas’
Link Mauve, https://github.com/xnyhps/capsdb/
-
Link Mauve
Oh, nice.
-
jonas’
aioxmpp has native support for reading and writing that format ;-)
-
Link Mauve
I guess I’ll merge mine into it.
-
jonas’
sounds like a plan
-
Link Mauve
jonas’, none of them have an @xml:lang, do they still validate correctly?
-
jonas’
at least one does have one (a grep on it shows it)
-
Link Mauve
Should I contribute only the ones from poezio which do validate, then?
-
lovetox
what this could be used nicely is to test your hash algo
-
Link Mauve
Or try to guess the @xml:lang?
-
jonas’
Link Mauve, I am confused, why guess it?
-
Link Mauve
jonas’, because we apparently didn’t store it.
-
jonas’
Link Mauve, or it wasn’t present
-
flow
I'm not sure if capsdb would give a realistic picture of the disco#info feature in disco#info replies situation: It appears to contain mostly non-node query results from clients, wheras, for example, ejabberd does not include it in its MUC component, and, while Smack would include the feature in non-node queries, it does not enforce that it is included in disco#info queries against nodes
-
jonas’
flow, for server-side things, I’d fire a search using the muclumbus crawler
-
flow
+1
- Ge0rG read that as "non-nude query results"
- Maranda doesn't wanna know.
-
Neustradamus
https://twitter.com/neustradamus/status/1065328474922061825