wetdry.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
We are a community focused on gaming, tech, entertainment, and more.

Administered by:

Server stats:

724
active users

If this lands on your feed, tell me about different features that are just missing in Matrix [matrix.org].

It can be anything, but please don't include memes like "unable to decrypt message" or other things that are already in the works, or maybe has already been merged (e.g media captions). Also, no, I won't "just use XMPP".

Some examples include better forwarded messages, rich profiles, or a live location sharing, just to name a few.

(I am writing something about this, boosts appreciated!)

matrix.orgMatrix.orgMatrix, the open protocol for secure decentralised communications

progress on my post (for which I asked for replies for) is going good

@cyrus Did replying to messages with images get implemented yet?

@newbyte no client apart from Beeper does it, but that's "legal" as per the spec

(An image sent with m.in_reply_to will render fine on most clients)

@cyrus @newbyte not quite correct, even (some of the) element clients implement it

@cyrus @newbyte element web/desktop do it, nheko does it as well, not sure about others

@cyrus The ability to autodelete messages from bot accounts without leaving a deleted message info in the conversation.
In example messages from uptime Kuma.
Or is this a problem with element and other clients?

@Seraphyn most clients have an option to hide the "deleted message" placeholders, including Element :)

Check settings > Preferences > Timeline / Messages

@cyrus
Nice, but what's about an automatic deleting message after a period of time only for dedicated users?

@Seraphyn very specific, I think if you're thinking of doing that for bots then the bot should implement that themselves really 🥴

@cyrus a working read marker that doesn't fuck with my OCD tendencies. I'm losing track which conversation I caught up on while being itchy on the inside...

@gim there's been a lot of work on Read Markers (or rather making them more reliable) since Element started work on Element X on Android and iOS

Whilst on Android there's currently a longstanding bug that makes sync take longer than expected, once sync goes through and gets started, the read markers are VERY reliable now, even upon restarting the app.

I would assume those improvements will come to Desktop/Web once they're fully ready :)

@cyrus Element X won't connect/sync my account at all right now. I canceled the initial sync after several days. Right now I'm using FluffyChat.

@gim That is probably less of an issue with the app and more of an issue with the fact that it uses an experimental way of syncing which has not quite made it into stable yet, as such instead of it being directly in the server, it gets handled by a separate proxy program.

The Matrix Foundation and Element are currently in the process of simplifying Sliding-Sync (turns out the "sliding" bit doesn't work well with encryption) at which point it will go directly into stable versions of Synapse, the most popular Matrix Homeserver Software.

TL;DR: If you're not self-hosting the Sliding-Sync bit, chances are it just hung up. No worries on your end.

@cyrus You say 'live location sharing' - didn't the original Matrix spec including a message type for a location?

@penguin42 there's indeed event types for location, but that's a one-off thing.

Live location would allow you to share and update your location every n seconds.

There is a Labs feature for this in the (old) element Android app, but it isn't fleshed out yet. That's why I put it as an example.

@roland oh, yeah, I think there was something blocking that? Not sure on the specifics, but some clients DO implement the relevant MSCs early

see cinny.in or fluffychat.im

Just hoping that sometime soon we'll see this merged (after so long)

cinny.inCinnyA Matrix client where you can enjoy the conversation using simple, elegant and secure interface protected by e2ee with the power of open source.
@cyrus a matrix homeserver with as much support as synapse and footprint as conduit/dendrite(if not less)
@cyrus state res that actually works
decent homeserver implementations
vcard
rosters
maybe pubsub
semianon
good clients

xmpp has all of these except for the first one, as it doesn't have federated rooms currently
fuck matrix, it has no reason to exist when we have xmpp

@zayd and you're completely the wrong fucking target audience!

Message me when I can do a damn reply in popular XMPP clients.

A reply, not a markdown quote.

@cyrus >Message me when I can do a damn reply in popular XMPP clients.
gajim nightly has them, dino has them, movim has them and monocles has them iirc, it just doesn't look like it from monocles itself
@cyrus and for the record
>you're completely the wrong fucking target audience!
i do use matrix a lot, i just don't like it

@cyrus attaching an image to a text message. currently, they are sent separately. I usually emulate this behaviour by writing my text, adding image, and then sending the text message while the image is uploading.

(at least, I think this is missing in Matrix? I use Element but I think it'd be weird asf if this was a part of the protocol and Element just didn't do it)

@terrain

This got merged into Matrix 1.10 on the 22nd of March this year, from what I'm aware Beeper is the only client that currently allows sending this, but Element X, SchildiChat, Fractal and probably more already had a quick patch to allow viewing, with work being done on redesigning the in-app flow for sending media to allow sending this too.

@cyrus oh awesome! so I'll be able to use this in the near(-ish) future. that's nice.

@cyrus I genunely dislike how detached the idea of rooms and spaces are. Typically when I join a server on discord for example I expect to be able to experience the entire server and then pick out the channels I'm not interested in.

Rooms feel like group chats rather than actual channels in part because they feel seperate from what a collection of community chats if that makes sense???
This is more of a client issue tho.
I also want account migration, better profiles and much better performance

@cyrus Granted I don't use Matrix much (I don't know many people who use it, and everytime I use try myself I'm met with bugs, crashes, network failures and 4 minute waits to sync 2 messages).

I do really want an actually good federated alternative to discord tho, but first impressions matter a lot with chat apps

@cyrus@wetdry.world Spaces need a full revamp. They are unreliable and clunky on most clients.

The Matrix DAG needs to get reworked as well. I've seen so many rooms run into state resets, breaking them completely until everyone joins a new one. GrapheneOS gets this done to their rooms quite regularly, to the point of having left Matrix entirely.
A chatroom breaking is an absolutely insane issue.

While its technically in the works, I'm not seeing any real movement on it: Synapse needs to go. It's slow and a gigantic resource hog.

I don't use Matrix anymore. The sheer amount of tiny and big jank just keeps piling on, and I dont want to deal with it.

@cyrus@wetdry.world Oh, another thing.

Migrations don't exist. That's an absolutely ridiculous oversight.

@cyrus@wetdry.world

Portable Identities is more what I'm thinking of. A federated protocol without account mobility is a big problem.

The EMS tool there, in my opinion, barely counts as migration. You still lose all data and all your contacts cant be sure that the new account is actually you in a fully secure way (unless you tell them, or choose to leave all rooms).

@cyrus@wetdry.world I'd love to be able to group images like this (Signal supports this) while matrix will send a bunch of images.

@AmyIsCoolz oh, media albums!

I should add that to the document, in the meantime, you may be happy to know that MSC3382 [github.com] is working on this :3

Rendered
This is an alternative version of #2881 with all attachments in one event, that is more optimal, but have harder fallback.
Related issues:

Attach multiple images (files) to message
Show a...
GitHubMSC3382: Inline message Attachments by MurzNN · Pull Request #3382 · matrix-org/matrix-spec-proposalsBy MurzNN

@AmyIsCoolz @cyrus interestingly enough, WhatsApp only sends single images too, they are just clustered and combined by the client

@cyrus proper encrypted search that does not need to download my whole message history first and also actually works. Includes also listing all shared files etc.

@HarHarLinks that is...easier said than done

@cyrus I really want image packs to finally land. Much of the ecosystem supports them already and has proven the concept for years(!), except Element.

@cyrus per device push rules would be great. The spec sort of half supports this but synapse doesn't implement it and, I believe, push rule profile tags are slated for removal in the spec. 🫤

Also, do-not-disturb settings for push rules would be great.

@cyrus live location sharing has been in there for over a year, probably multiple years, though it is hidden behind a labs toggle in Element, so: fair enough

@cyrus
Not in Matrix itself but in Element, the reference client for Matrix, I am missing two functions:
- support for multiple accounts
- the ability to switch these accounts on and off temporarily and easily.
In Conversations, an XMPP app, this is implemented in an exemplary way in my opinion.

@oausi @cyrus (please don't call Element a reference implementation, it is not, it does not even implement all features of the protocol, some of which are implemented in competing clients. Element is simply the biggest player on the field, driving most of Matrix development, and implementing features even before they land officially in the protocol because that process requires a proven working implementation to get accepted.)

@cyrus In terms of features it's almost complete IMO. It just needs stability, reliability and performance now.

@fell well a lot of reliability improvements came from Vodozemac (new crypto/encryption implementation) and performance is gonna get a lot better with SyncV3 (which is also very very soon)

@cyrus It has already improved dramatically over the past 12 months, so I have no doubts that it will keep improving.

Of course, there is the neverending story of calls as well.

@fell guess what...

(pretty much) stable MatrixRTC Implementation: call.element.io

relevant MSC: github.com/matrix-org/matrix-s

This is already in the new mobile apps (Element X) and also available as a labs feature in desktop/web Element :)

call.element.ioElement CallYou're invited to join a call on Element Call

@cyrus I just remembered a feature that I missed this week. It would be cool to be able to forward messages with the information where it came from (if public).

@cyrus Maybe the possibility of sending images with description? I've heard there is work in progress on this, but I'm not sure.

@CleoMenezesJr that is what media captions are, they were officially made part of Matrix on the 22nd of March this year, but have been merged for a lot longer.

What we're waiting for is for clients/apps to allow sending that too, because without letting the user send these kinds of events the fact that it's in the spec is kinda useless.

Though, a community member worked on getting this in Element X Android [github.com] and I would bet that some other clients are working on it too :)

…to media/attachments
Fixes #2573
I has too many UX changes for my taste so if one of the team likes it and wants to pick it up that's fine by me :)

Type of change

 Feature
 Bugfix
 Technical
 Ot...
GitHubMove attachment preview above the composer, allowing to add captions … by surakin · Pull Request #2600 · element-hq/element-x-androidBy surakin

@cyrus Thanks for the info. Matrix definitely has a very strong development. I noticed that clients have not been able to follow the implementation of these new features. The closest client is certainly Element. There are clients who have not yet implemented threads for example.

@CleoMenezesJr @cyrus kde's neochat can do that easily
on some other clients you're able to do it with some messing with markdown