XSF Discussion - 2022-03-09

jonas’, Sam, how to delete these? https://xmpp.org/registrar/compress.html https://xmpp.org/registrar/alt-connections.html :)

moparisthebest: It is not up-to-date since several years, it is linked to: https://github.com/xsf/registrar/issues/31 + https://github.com/xsf/xmpp.org/issues/422 I have informed that it is very very old: "Last Updated: 2011-02-22".

jonas’: making PRs would imply that if know what the right values are

does one really delete registry entires? I'd expect that they stay registered forever for documentation purposes (but potentially get marked accordingly) ✏

I agree, for the same reason we don't delete XEPs

+1

MattJ: can you make use of https://op-co.de/tmp/namespacemap.txt for jabber.org?

I'm still not sure what to do with the anomalies (which I've excluded from this list)

Ge0rG: yes, I think so. I will look at it very soon (next day or two), it should be an easy copy/paste/reload job

MattJ: awesome, thanks.

I hope somebody else is going to give the list a look. My first heuristic was to link to the XEP that has the most mentions of the namespace, but that didn't work out well

Instead I used the earliest XEP number that mentions the namespace, had a bunch of false positives like '30 that mention too many things, fixed them manually

perfect is the enemy of good

Maybe we could add an XML tag to the XEPs that contains all the namespaces defined within that XEP

There are 2 problems here too: - https://github.com/xsf/xmpp.org/issues/421 (redirections do not work) - https://github.com/xsf/xep-attic/issues/3 (a lot of missing)

> I feel like for people in russia who are chatting with people from abroad, now is possibly a good time to activate disappearing messages when talking about certain topics / naming certain events I always thought it's helpful while cheating wifes or something like this. But damn politics everywhere.

rion: yes!

rion: I've argued before, that the xmpp ecosystem, as currently implemented, is by far not the smartest choice for people with a risk of being killed by their government.

require e2ee, store as little as possible

Ge0rG, but is that a reason to not improve it in that direction?

jonas’: no. All we need is a decade and an army of security specialists.

jonas’, flow MattJ but if no XEPs point to those registries anymore, why keep them around ? Isn't it just confusing?

moparisthebest: if nothing points there, it's only relevant for the legacy users anyway

they are security issues, there shouldn't be legacy users

Better to update the registry to clarify that, than just remove it

moparisthebest: well. where should I start?

I'd be ok updating the registry to clarify that too...

the compression one is still pointed to by obsoleted XEPs, so I get keeping it and updating it, the DNS entry one isn't pointed to by any XEP (it was removed from '156) so it's pretty confusing to keep it at all I think ?

moparisthebest, we still keep old versions of XEPs around

I think the right thing to do is simply note that certain registries/entries are not to be used for whatever reason

so how do I add a note to registries then? :)

moparisthebest: you need to fix the registry deployment

I thought Sam was doing that? :D

In case anyone's interested, goffi is giving a talk on bridging XMPP with ActivityPub *now*: https://meet.in-berlin.de/XMPP-ActivityPubGateway

Holger, will there be a recording?

I don't think so, sorry.

Hi folks, reminder to take the chance to talk and present at our XMPP Office Hours! https://xmpp.org/community/officehours/ and have a look at xmpp.work too!