XSF Discussion - 2022-09-23

Hello everyone, can anyone help me with creating the wiki account?

Alex perhaps^

You can send me an email with your preferred nickname to gnauck@gmail.com and I can create an account later today in my evening

Alright, thank you.

I can do it _right now_

I just need your preferred nickname and an email address

> : I can do it _right now

Now I am confused, I already sent the details to sir @Alex

Should I send it to you too right now sir @Guss ? ✏

bhavy: I have created a new account for you on the wiki. You should have received a confirmation email in your mailbox.

Alex and me can both create these accounts. I just thought I'd help you immediately, since I was available now.

But then, I got dragged into a meeting and failed to respond to you, causing confusion. Apologies :)

Ok, thank you.

> bhavy: I have created a new account for you on the wiki. You should have received a confirmation email in your mailbox. Yes, I did thanks once again :)

goffi, I just had a look at Event

It's quite interesting but I'd really prefer to break it down in several small xeps, lots of features seems to be a bit optional and I'd prefer to have different namespaces for those features

I'm always afraid of big xeps like that because you tend to have many different implementations level in the wild

edhelas: it's not like pubsub, except <start/>, <end/> and <name/>, everything is optional. It's just metadata that your client show or not, but it doesn't really hurt to not have them. While I agree that some feature could be split in sepate XEP (mainly RSVP actually), the issue with doing many XEPs is that it increases the workload, and I have already an heavy enough load.

and in the case of events, I'm not convinced that it really worth it.

for pubsub attachments it may make more sense

Is there an XML of vevent like for vcard4?

singpolyma, https://www.rfc-editor.org/rfc/rfc6321

On my side I was more thinking of simply attaching xCal to Atom publications, quite simple to do

edhelas: yeah, that sounds ideal

That would be perfect for https://mov.im/?node/pubsub.movim.eu/berlin-xmpp-meetup

You create a publication and configure an event for it, like attaching a picture or a link

And that's it

In Movim I was planning to convert the xCal to iCal and allow then integration with mobiles/desktop agendas

But it doesn't solve many of the topic addressed by goffi Event xep

Oh, new XEP?

I will have to read the xep before having an actual opinion

this XEP convert what I've been experimenting for years with libervia, and was necessary to convert ActivityPub events (from Mobilizon) in the gateway

it's staighforward to convert it to iCal or whatever, not a problem.

anyway I have to go now, afk

goffi, were you aware of RFC 6321?

Zash: RFC 6321 is IMHO making the whole thing far more complex and difficult to implement, with its own set of data types and metadata. My proposal uses XMPP mechanisms and data specifications: geolocation is XEP-0080, file references are XEP-0447, RSVP is XEP-0004 + XEP-0470 comments are simply a link to a XEP-0277 node, permission are managed with pubsub permissions. Most of that is probably already implemented by clients and specified, no need to find a xCal/iCal parser (and it's easy to convert if necessary is ones want to export data).

Also RSVP mechanism is based on existing XEPs and extensible with data forms. It would be more complicated to adapt an other xCal IMHO.

Reusing is good, which is the main thing about using xcal. Reusing other xeps is also good. Main thing is to avoid new xmlns strings where possible

All I want is a motivation to explain why existing things were not reused.

Sometimes it makes sense. Sometimes we just end up extending it until the prior existing thing has been reinvented.