jdev - 2026-02-12

> clients could do that, but how far do you go? just because a turn server exists doesn't mean you'll be able to connect to it perhaps give an error if you cant connect, and then have a explainer on why such as because none could be discovered ↺

> I don't know if this is still the case but I know conversations used to refuse to show the call button unless there was a turn server I feel like that could cause a misunderstanding of supported features in the client ↺

hence leading to the impression that xmpp doesnt have calling

perhaps have it greyed out and say no turn server found when hovered/tapped

Well, xmpp doesn't have anything. Or else has everything 😉 but it would give them the impression their setup doesn't have calling, which would be true

well i guess the impression that that client doesnt have calling at least

like if you have it greyed out or show an error then its a very clear transfer of blame

I think most clients have moved away from that now thankfully

The point is _discoverability_ - if you hide a feature that you actually support, because e.g. it's not supported by the current server, a user looking for that feature will assume you don't support it because they can't find it; whereas showing it, but disabled, indicates that it is available (just not right now; ideally, with some indication/explanation why)

Except if their server doesn't support it then showing them the disabled button is just annoying? There's nothing they can do about it. It effectively isn't supported and can't be for them

Vs "contact offline hide call button" where I would completely agree with you disabled is better

singpolyma, what biboumi version are you running on irc.cheogram.com

it returns invalid disco info

It's my own fork. It's possible I broke something what's it doing?

``` <iq from="irc.cheogram.com" id="8e95b784-d4b3-4c90-b8c7-cf63a6fd94d7" node="https://biboumi.louiz.org/#URGCt+50NTdI6Ifcm1/YYNVxSjc=" to="someone" type="result" xml:lang="en"> <query xmlns="http://jabber.org/protocol/disco#info"> <feature var="http://jabber.org/protocol/disco#info"/> <feature var="http://jabber.org/protocol/caps"/> <feature var="http://jabber.org/protocol/muc"/> <feature var="http://jabber.org/protocol/commands"/> <feature var="urn:xmpp:ping"/> <feature var="urn:xmpp:mam:2"/> <feature var="jabber:iq:version"/> <feature var="http://jabber.org/protocol/muc#stable_id"/> <identity category="conference" name="Biboumi XMPP-IRC gateway" type="irc"/> <identity category="gateway" name="Biboumi" type="irc"/> </query> </iq> ```

the node attribute, needs to be on the <query> element

not on the iq

Aha. That's almost certainly a typo in my work. Thanks for letting me know

and another weird thing is, i have a user and a log, where they join a irc channel successful, i request MAM successful, and 5 seconds later they write a message, and the IRC MUC answers with an error "you are not currently joined"

does that maybe ring a bell?

Hmm. Not sure. I haven't changed anything in those areas and haven't had that issue myself

Most of changes are around disco