jdev - 2022-06-20

one of the more weird things is that server put requested mam messages into offline storage

was there not a possibility to turn that off?

something to clear the offline cache on connect or something

I have a question for client developers. How seriously do you take service discovery? Do you always check for support, or do you sometimes YOLO? I'm specifically thinking of carbons. So far, I didn't check for carbons support and just always sent the IQ. I now am thinking of checking for support first, but I wonder if that might cause breakage. ✏

checking for support has the advantage that you don't have to rely on the service sending an understandable error back in case it doesn't support it

for server features, I usually do discovery; for client features, I don't care (as I can't know which client I'll be talking to anyway, thinking carbons and MAM)

Can't you cache disco#info and thus checking should normally be a check without roundtrip?

yup

I'm more worried about some servers not advertising support but indeed supporting carbons. I guess that's a bit silly

And I then don't enable carbons and then get bug reports

Also, carbons being an iq is silly, sasl2+bind2 when?

So really what I want to avoid is bug reports 🙂

So you want it to just work, even if everything is horribly broken, so that nobody notices and reports the bugs?

If simply sending an IQ without checking for support results in less bug reports, then that's what I'd prefer

I am conflicted

I guess I'm a bit paranoid. I can just assume server developers are sensible and will properly advertise support

🙂

:-)

and if they're not its likely an easy fix

Yes, but to figure out that that's the problem takes time (which is what I'm trying to avoid)

that should be easy with proper logging and diagnostics?

warn, no carbons advertised, server is totally outdated, abort()

yep, I'll warn

otherwise this seems like the kind of thing that results in more annoying bug reports sent to someone else

its a fucking pandemic

seems the whole world has MUCs added to their roster

im the idot who writes code that assumes a roster contact is not a muc

contagious roster-MUCs?

> otherwise this seems like the kind of thing that results in more annoying bug reports sent to someone else yep ok.

I don't think I've ever encountered someone having a MUC in the roster ✏

I'm not sure what Converse would do, I'm pretty sure it also assumes roster entries are contacts

> its a fucking pandemic > seems the whole world has MUCs added to their roster 😅

its funny that Discovery is XEP number 30

they they added 20+ other XEPs until they reached the conclusion, its probably good if we know what we are talking to