jdev - 2023-06-23

Ok so I'm planning to totally drop the publish-option feature in Movim for now as the support is currently broken on servers (especially ejabberd). I might add it back later.

edhelas, what's the alternative? (I'm not aware of any safe alternative)

Well I'll send a manual configuration of the node each time I publish

😕

https://xmpp.org/extensions/xep-0060.html#owner-configure

Double the traffic but eh 🤷‍♂️

I don't understand... what's the bug? Other clients are using publish-options

https://github.com/processone/ejabberd/issues/3044

So it's just that certain fields aren't working in publish-options

So keep publish-options with those fields, and configure the other fields manually until ejabberd is fixed?

No I'll just configure everything manually

I'll not do half solutions in the code

Okay, but I consider what you're doing to be a half solution :)

You'll want to add publish-options back in the future anyway

or even enable it when the server is known to not be broken

It's safer than manually configuring

🙄

edhelas, which field is it that you need to configure?

A lot of them actually, why should I pick ?

i mean, which field is that important, which ejabberd does not support

there are definitly fields, which are nice to have, but are not essential for some functionality

Oh nothing fancy

<field var="pubsub#persist_items"> <value>true</value> </field> <field var="pubsub#max_items"> <value>max</value> </field> <field var="pubsub#itemreply"> <value>publisher</value> </field> <field var="pubsub#access_model"> <value>presence</value> </field> <field var="pubsub#pubsub#notify_retract"> <value>true</value> </field>

Those fields I can configure them manually with the form config

It's explained in the ticket

and is this all for bookmarks 2?

bookmarks2 you would use access model whitelist I think

you use this for all bookmarks xeps

and its supported by ejabberd anyway

I'm implementing plenty of PEP XEPs

Yeah whitelist for bookmarks, not presence ✏

This is for Microblog

https://github.com/processone/ejabberd/issues/3044#issuecomment-1477384826

and max items you set to "max"?

is this in itself even supported by ejabberd?

It is

Again, this exact form, I can submit it manually using a node config

Can you not fallback to configuring the node manually, when you get this error from ejabberd? Just like you would when publish-options tells you the config differs

yeah seems easier

the node config flow you need anyway

https://upload.movim.eu/files/9d94237298995552fa13436420195fbca436dce7/8cmQObCjXGJK/image.png

its not ejabberds fault

No, what I'll do is reconfigure the node each time I publish for now

its just that it rejects all your publish options requests, and you end up in this flow anyway for ejabberd

yeah but why edhelas, normally you publish with publish options

then you get an error

Because I have to do a big refactoring to handle those multiple request-flow in Movim

and then you go into the reconfig flow

edhelas, and race every other client :(

ah ok

yeah fair enough, but just to be clear, ejabberd not supporting this makes it not really that you have to write more code

all that code that exists now, needs always to be there, it doesnt matter if a server supports publish options or not

Anyway, I'll figure something out

i should look at my bookmarks 2 impl again

i think its not often used

i use it only if the server supports the conversion XEPs

and i think its a rare case that they do

But I can tell you that the state and accessibility of Pubsub in the XMPP realm is really not that great. I've been working with Pubsub for years now and I can get that new comers really don't want to handle this complexity/buggyish experience.

:/

lovetox, yeah that's about what is recommended I guess. Re bookmarks2

edhelas, no discussion about that, but i feel like this with many things in XMPP

like i curse everytime if i have to thinkabout PMs

and MAM

and before MattJ jumps in, i meant PMs in combination with MAM :)

lovetox: at very least snikket has the conversion xep enabled

also the urn:xmpp:bookmarks:1#compat ?

urn:xmpp:bookmarks:1#compat-pep

i think i look for those 2

hm no, just compat-pep and node-max features