jdev - 2026-05-15

I wanted to ask if there are ways for fine-grained control over message synchronisation, like "fetch only the last n messages over MAM"

Is there a discussion room for borogove?

badrihippo: not really exactly as far as I know, but one can request all messages, flipp the result https://xmpp.org/extensions/xep-0313.xml#query-paging-flip And then stop requesting more pages when it's over what you wanted.

Hm for one set it can be set with paging <max>10</max> As long as it isn't bigger then the server limit.

Oh, that's nice

Yeah that's basically what I was looking for

> Is there a discussion room for borogove? yes the Sopranica project discussion room ↺

Is there a client that lets you disable Message Styling when sending a message?

i guess every client that supports message styling?

just not use the message styling functionality

i guess what you are searching is a client on the receiving side, which lets you disable interpreting messages as styled

there is also this https://xmpp.org/extensions/xep-0393.html#disable

That's not the same thing - how would one send "a message containing *not-bold* or similar incidentals?" The XEP has <unstyled/> but do any clients actually support sending it? (And how many support receiving it)

I *can't* disable Message styling

>_>

**** Like that'd be so easy

because it something the receiving client does, not the sending client

> there is also this https://xmpp.org/extensions/xep-0393.html#disable I'm talking about clients that let you send <unstyled> ↺

along with your message, to disable formatting

im not aware of any, and im strongly against implementing that

> just not use the message styling functionality Anyway in all seriousness, you can't just "not use" the Message Styling functionality, because it acts on the content of the message ↺

It's not just some XML you can just stop sending

correct because its something the receiver does not you

so your question is .. weird

how can i stop people interpreting * as a styling directive

you cannot ..

Only the sender knows the intention of their message, so whether that * was intended for styling is their choice, not the recipient's

Yes I can't but I'd like to tell them that this isn't meant to be styled

If I send emoticons, I don't want the client to interpret it as a quote/bold/etc.

yeah but its the wrong solution to the problem

the right solution is clients implementing XEP0394

and then you dont have that problem

Inline styling is the wrong solution to the problem, but we're already there

Yes, XEP0394 handles this better

correct and im not adding more functionality so the wrong solution can be extended more

But I haven't seen any client convert inline styling to XEP-0394

Or even display it

Dino supports it for example

not sure what you mean by converting, why would there need to be something converted

maybe check the Dino UX out

> If I send emoticons, I don't want the client to interpret it as a quote/bold/etc. can you name an example where this would happen? sounds only possible if you by accident never make spaces in your sentences ↺

ok i take this back, probably there are a million ascii art things that trigger this

Yes

Ah okay, thanks singpolyma

For ASCII art I use code blocks. It's the only way to display it right anyway. Because normally receivers don't have mono fonts in use for their chat app.

> Is there a client that lets you disable Message Styling when sending a message? Cheogram WWW now sends unstyled if the message wasn't explicitly styled ↺

>> Is there a client that lets you disable Message Styling when sending a message? > > Cheogram WWW now sends unstyled if the message wasn't explicitly styled WWW? ↺

``` ._ _ (.\( ) * (_Y|_/ /_\ L ``` ✏

> ``` > ._ _ > (.\( ) * > (_Y|_/ > /_\ > L > > ``` I still don't know what that's meant to be ↺

Seems some clients strip whitespace if its the first in line

😑

>>> Is there a client that lets you disable Message Styling when sending a message? >> >> Cheogram WWW now sends unstyled if the message wasn't explicitly styled > > WWW? The pwa / "web app" ↺

> Seems some clients strip whitespace if its the first in line The leading whitespace shows in your original code snippet, but the quoted version isn't displayed well ↺

I guess my iOS alpha also does this actually. If I send *this* I think you'll get an unstyled xml

should, but how many clients take note of the <unstyled/> element?

I also take note of it but yeah I don't know about others

many clients have subtle bugs in their message styling parser also. Not usually catastrophic but there it is