That's nice if you are genuinely paranoid on this front (rightfully or otherwise) but really sucks if you want people to share links with each other (one of the big use cases we seem to have for using tools like this).
Related to that, a side effect of all the e2e encryption is that it's really hard to give people or agents access to the full history of a channel. It's not impossible but it involves jumping through some hoops. And of course a primary reason for us switching away from Slack was using AI agents in our chats more and experimenting with running some of our own bots and something that is sometimes referred to as a company brain.
Instead of fighting the tool we switched the tool. We picked Zulip around the same time the founders of that project were hired by Anthropic. For the migration, I gave AI access to my matrix keys and it moved over most of our channels to Zulip. Since Zulip has topics, I also made it group messages by topic.
I like Zulip so far. They could use a UX refresh in the client. It looks a bit dated and meh. But otherwise it does the job. With both Zulip and Matrix, I orchestrated the rollout and hosting with AI, including giving admin privileges to manage the whole thing. Works surprisingly well with both. But jobs like add this person to that channel and given them such and such rights are working flawlessly. We had some openclaw thing running for a while but we gave up on that (too much issues with that). But we have a lot of chatgpt scheduled automations and some scripts and skills that allow it to search through and post in Zulip channels. Very useful.
If you don't want to self host, Zulip has a generous freemium tier as well in their managed hosting. Haven't tried it but looks like a decent starting point if you want to try it out. You can migrate to self hosted later, if you want.
Off the top of my head we've:
- Changed the settings so you can now opt in to URL previews both for unencrypted and optionally encrypted rooms (so if you don't mind the exposure over usability, that's an option for you)
- We support bundled previews where the sender can send through the link preview via the message, avoiding recipients having to leak any information (if you trust the sender over your homeserver). This has just landed in the spec and will be part of the stable app shortly.
- We've added previews atop the composer before sending so you can check what is going to be sent, and choose to remove obnoxious previews.
- Numerous rounds of redesign on the design of previews themselves to be less ugly.
- The spec now allows you to send messages that explicitly state not to preview, so bots are less noisy.
It's actually good. I do not want someone to know that I saw their link. Furthermore, link previews destroy one-time auth links (if you want to send such link to someone). Furthermore, the server can serve different misleading content to a preview request and to the actual user. So I do not understand why someone even needs this dangerous and useless feature.
If you want to disable link previews for personal reasons or for organizational policy reasons, that should of course be possible. But imposing that being disabled as a default for everyone that requires explicit opting in on every channel is a bit user hostile. It's a pretty common feature too.
> this dangerous and useless feature.
I don't think we are going to agree here. But I do note that this does not seem to be a widely held view. Many chat clients and social networks have it and it seems inoffensive to most of their users.
https://matrix-org.github.io/synapse/latest/setup/installati...
It's not just about privacy. To me, this is more usable - it always annoys me, the default habit of taking up half a (phone) page with a giant site card. If it just resolved title (and used normal chat-sized font) it would probably be good, but nothing seems to do that.
E.g. my wireguard network has an isolated/non-federated Matrix server all my AI agents to talk to me over. It's great for that, but I have no interest in using it to talk to people.