XSF Discussion - 2022-02-16

emus: eh, you can send me a postcard with your details on it, I guess?

There's only so much burning hoops I'm willing to jump through, though.

If only someone would come up with a protocol for communicating that optionally supports e2ee

Doesn't Matrix have that?

I hear good things about Signal.

OG (OpenPGP over Gmail)!

On another topic, I don't suppose there's XEP search functionality on the website, with support for OpenSearch, is there? Being able to look up xeps by numbers or numbers by names right from browser's search bar is an itch that's steadilly building up for me

mjk: there isn't yet. Are you volunteering? :)

wurstsalat: Not yet, I don't think I'm up for backend coding, especially when there doesn't seem to _be_ a backend (the site is 100% static, right?)

Lua on the backend would be nice though :)

It is 100% static, but since everything is in docker it's easy enough to change that, especially if the backend is just reading static files

Yeah, no database needed for sure :))

I guess you can hook into the xep sorting thing if it's just title/number filtering you want to do

wurstsalat: you mean, in js? Well yeah, filtering on that page would be good as well, just not as perfect as opensearch would be :))

mjk: yes. That would keep complexity down :)

Right. For my personal itch I may just write a script for searching in xeplist.xml locally

And maaaaybe put it on a personal web server... which I don't have yet

mjk, if you are on firefox, I can highly recommend to make a wildcard/shortcut bookmark for xeps

that helps with the "lookup by number" use case a lot

Oh, a keyboard shortcut? That a thing? Unfortunately I'm most of the time on Android, so..

hmm

at least on firefox desktop, you can make a bookmark so that typing `xep 1234` in the address bar will get you to XEP 1234

not sure if and how that works on android

Guus: Yes, xmpp for sure but I dont have your ID :/

That is cool, I'll look in that direction. Ty jonas’

emus: https://wiki.xmpp.org/web/User:Guus (my company website lists an address in the footer, that you can use)

mjk, http://johnbokma.com/firefox/keymarks-explained.html

Guus: great

Guus: sent

emus: to what? I've _just_ restarted my home XMPP server, so chances are that something got lost.

ah, nevermind

does the mailinglist allow for attachments?

"maybe"

ghee, thanks! :D

I'll just try.

Sent to the mailinglist. No bounce so far. Did someone receive it with the attachments? I'm just realizing that I included nice keywords like 'order' 'price' with an email that includes pictures. If that doesn't set off some spam filters...

I have attachments.

Thanks. Apologies for the precedent.

Ge0rG, as author of XEP-0410, would you consider adding an opt-out of some sort for the server taking care of things for you so pings aren't needed?

Zash: yes

I thought this Firebase thing is dead. Wasnt it based on XMPP? https://www.kdab.com/qt-allstack-ii-adding-firebase/

It's... complicated

😅

Ge0rG, I imagine I should take that as a "PR welcome"

Zash: yeah

Zash: we can also discuss the details in advance once I have some energy

These days Firebase is more of a brand name covering a range of APIs that developers might find useful. This includes the push stuff, which is one of the oldest parts. I'm not sure if Google is still exposing an XMPP interface, but they might well be.

MattJ: Thanks

MattJ: IIRC they are, for two-way firebase push

> The XMPP Registrar [9] shall include 'urn:xmpp:alt-connections' in its registry of protocol namespaces (see <https://xmpp.org/registrar/namespaces.html>).

hrm, well I guess *that* never happened...

very likely

:)

what's our process for deleting https://xmpp.org/registrar/alt-connections.html ?

type "The XMPP Registrar [9] shall remove 'urn:xmpp:alt-connections' from its registry of protocol namespaces (see <https://xmpp.org/registrar/namespaces.html>)." into a XEP?

no, we want 'urn:xmpp:alt-connections' defined, we *don't* want the TXT record tags defined

Last I heard there was no active registrar and the registries weren't being updated, whether added to or deleted, so that's probably a first step :) I think I volunteered to help maintain them but never heard back from anyone (if not, I volunteer as tribune, I mean, registrar again)

Sam, make a PR which fixes all the things I guess?

unless you did and nobody looked at it, that's entirely plausible

I made several and nobody looked at them IIRC :)

I too made one IIRC

they need more docs then, possibly, or a resend somewhere

Yup, 5 PRs open. Feedback on any of them would be appreciated.

Who even has permissions there?

I do

I see they take security very seriously https://pidgin.im/news/security/

hm, possibly a remaining question was where to get the image built

given that all the options suck

moparisthebest, Given that migrated to a new website not too long ago, I imagine if that's an URL you expect to work then please report it to xmpp:devel@conference.pidgin.im?join

Zash, followed from https://developer.pidgin.im/wiki/SecurityVulnerabilityProcess but yep will do

I tried to volunteer to do that too, but just submitted a PR with the dockerfile that's similar to what's already deployed instead, neither received a response :) not your fault, I'm just saying, we have the people willing to do the work if you're willing to utilize them

(or whomever is in charge of this)

Sam, I am in charge, so I'm the right one to shout at

moparisthebest, as it says at the top, migration

but what's your plan for building the image?

yolo build everything on the same VM? also iteam topic?

jonas’: *shouting* I VOLUNTEER TO HELP :)

Zash, building on the VM is the thing which has been ruled out in the past

But now we do it for at least the website and possibly the wiki

and yes, kind of iteam topic, but iteam has no answer to that, hence the editor has found a different "solution" for xeps and xep-attic

We can still keep the repo up to date even if it's not building right away

new year, time for a new CI chain?

Sam, so I think the best way would be to have you join editor team again so that I can grant you +w on registrar so that you can do the cleanup, and then we can coordinate with iteam how to get the stuff deployed

forever, until you roll your own

I'm perfectly happy with fully delegating /registrar/ to someone else

(in this case, you)

That sounds fine, I don't think I ever officially left, I just stopped doing the work

you're not on https://xmpp.org/about/xsf/editor-team/ anyway

which has the same source of data as the github permissions

I think you dropped out of XSF membership for a term or so

ah yes, Q2-2021, hence you got removed from the team

I guess I volunteer for that then

IIRC team memberships go through board

so writing to board today would probably be good to get it done tomorrow

I happen to be on board@ so I can give my OK to that

Done