XSF Discussion - 2022-03-22

xsf should add reply feature

al1r4d, https://xmpp.org/extensions/xep-0461.html ?

MattJ, how to reply ?

The XSF doesn't develop any software. How to reply to a message depends on the software you use.

Is there anyway to puplish aphoto along with its description in one shot ... like in telegram

What client are you using? Many of them work differently.

I think yes but most clients don't let you

iirc with Conversations and derivatives it's explicitly an Android UI limitation

I don't think so, lots of other apps let you attach things and send messages

But I'm not sure what "Android UI limitation" really means, so I might be wrong

It's an internal database structure issue

3.x will do massive refactore of how everything is stored and will allow a message to have more than just one media

> It's an internal database structure issue This looks reasonable

I tried conversations,blabber,monocles, and c0nnect in android Also pidgin and gajim under linux debian No chance any of them could do it

I believe it is about the internal data structure of the xmpp

it's not, it's just how most clients are implemented

I'm not sure why clients don't do this, but it's not a restriction in XMPP. I really dislike that clients don't let me do this too.

But I thought some client that focuse on telegram similarity for news channels might do some work around for this

Even the very old and simple method (called out-of-band data) by which media is sent does support a description, but clients don't implement support for that

> I'm not sure why clients don't do this, but it's not a restriction in XMPP. I really dislike that clients don't let me do this too. I believe all of the currently available clients can do it if the developers are asked to

Zash, Gajim used to support that, but it got removed to align with Conversations’s ways.

Great 🙁

The internal data classes might not support it but I can imagine workin around it in a way or two

> Zash, Gajim used to support that, but it got removed to align with Conversations’s ways. This is strange ... Antideveloping features

> تجارب wrote: > This is strange ... Antideveloping features Yeah. Lets just say that the whole xmpp ecosystem has shifted to align with conversations a lot. Hopefully that will start changing with snikket and dino

why would it ? both are modelled heavily after Conversations

people who used telegram don't want the 80,000 options gajim provides

Well تجارب wants news channels/moderation and descriptions. Gajim provides both. Telegram is pretty advanced despite how deceptively simple it looks

what's the downside of just sending a picture in 1 message immediately followed by a description in another?

moparisthebest: my thinking was that dino will push for more normie features and calls. And snikket will push for more security, self hosting and invite stuff

In a MUC there's a race condition. Lots of other messages might have been sent.

close enough...

Maybe. Maybe not. If you've ever tried to do it in a busy room it can be quite annoying.

Or the problem of accessibility. We can put descriptions in pictures to accomodate it

There is a huge push for it in Mastodon which is pretty great

don't get me wrong, I think including them both in the same message is a good idea, push for the change

I don't buy it's "the one thing (tm)" keeping XMPP from mainstream adoption :P

> what's the downside of just sending a picture in 1 message immediately followed by a description in another? This is the only option I have, apparently

تجارب, just ask the client devs for the change

> تجارب, just ask the client devs for the change I will

> moparisthebest wrote: > don't get me wrong, I think including them both in the same message is a good idea, push for the change > I don't buy it's "the one thing (tm)" keeping XMPP from mainstream adoption :P Of course its not :) Just nice to have xmpp more featureful

in a news channel with one user having voice, it's a non-issue, even :)

no races when you don't have concurrency