upvote
We tried it out for a few weeks earlier this year with a small team. It's alright but there are some annoying defaults (no link previews by default being one of the more annoying ones). You have to opt in to that on every channel for every user. I get why they did that but basically usability and UX is thrown under the bus here because of some hypothetical privacy issues.

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.

reply
Hey, eng lead for integrations at Element. Link previews in Element specifically is something we've specifically spent more time on this year, because up until recently it reeeeeeally sucked. There are literally 10s of changes made, so suggest having a look through our https://github.com/element-hq/element-web/blob/master/CHANGE....

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.

reply
Good to hear.
reply
> no link previews by default

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.

reply
My simple view is that I don't want to have to micromanage this setting in every channel, for every user just because some people want this off. I think that's a reasonable view.

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.

reply
Link previews should ideally be fetched server side and then you would get the best of both worlds. I wish synapse would support that.
reply
> no link previews by default being one of the more annoying ones)

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.

reply
Out of curiosity, what's so bad about it? I haven't used it myself, but it looks like (just) a chat app?
reply
It's not about better, its about incentives. Someone will be incentivised to move to a paid platform as it will look better on their CV (I sucessfully implemented a major 15 million euro project), and Slack will of course help them with the finance case
reply
Could they not also say "I saved 15 million euros by moving to an open platform"
reply
It's the public sector. No one is incentivised to save any money. In fact, saving money may make someone think it's okay to reduce your budget, which is bad.
reply
Hard disagree - at least in France and now. We are asked to make economies (I work on French transportation open data) yet deliver more.
reply
Same in the private sector, the incentives are to increase your headcount and budget, as it progresses your career
reply
Someone who saves the government money by decoupling it from the private sector is probably not going find many friends in said sector after their tenure ends. Revolving doors, like any machine, needs greasin'...
reply
Someone will have done, then they move on, and the next owner needs to make their mark, meanwhile the sales people are explaining how much better their proprietary system is over nice lunches, people who come in who are used to slack/teams/etc are whining that this is different and therefore worse, and someone says "where's the piece of paper which stops me being held accountable if it breaks"
reply
The piece of paper is the contract they have with Element. You don't self-host at this scale unless you're a highly technical org.
reply
I've found Matrix really nice for isolated setups, funnily enough.

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.

reply
I also want to like matrix and maybe even more xmpp, but my experience with those is until now suboptimal to say the least. Trying delta chat now....
reply
Do you have a better alternative in mind?
reply
xmpp?
reply
They said "better".
reply
I have been using xmpp successfully now for couple of years. It works reliably both on ios and android, don't see any problem with that solution.
reply
I have been using xmpp for decades, but unless it gets its act together, it cannot be a serious competitor. The ecosystem and protocol spec is too disorganized and the user onboarding process is years behind Matrix (and Matrix' is quite bad to begin with).
reply
Correct! which XMPP is.
reply
deleted
reply
I'm so sad XMPP never took off. I remember being annoyed by the fragmented state of support for pretty vital "extensions" though. Has anything changed in that regard? I remember there was talk of consolidating a bunch of must-have extensions, like E2EE, into a single highly recommended one – did that go anywhere?
reply