this post was submitted on 27 Jan 2026
368 points (98.9% liked)
Technology
79473 readers
5894 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think this was posted 3 times in this community already, from different sources
That's low. I anticipate 7.
... and on many of them I complain again that they made a whole new project instead of just using and contributing to Jitsi , which the FSF created expressly to counter Zoom/Teams :/
Actually, there's also an official Jitsi server (called Webconf). And there's another Big Blue Button one. I think Visio has features not available in Jitsi though, like AI-produced transcript of the call.
It is actually not hard to extend the software. I, for example, set up automatic uploading of cal recordings to a Peertube instance.
I guess. There must be a reason for them turning to something else than Jitsi given they already had that running (and the French service responsible for that, DINUM, is surprisingly extremely open-source friendly for a state service), but I don't know which one.
It is always either that the license is not permissive enough, too many changes are required that upstream wouldn't merge and its would be hard to keep rebased, showing the world that they can be absolutely independent, or not having enough experience and experts for given stack. Maybe I missed some reasons, but that'd be all I think of.
Either way, if it's open sourced our company might switch.
You may be new to modern software development. Switching proverbial horses is massively common, usually for no benefit (or to lock people in). It's everywhere, and especially in the corps who want that lock-in (ohai apple).
For a 2 week overlap, people on gtalk, Facebook and a regular jabber server could chat with one another as easy as addressing an email message. Then both Facebook and Google switched to their own homebrew replacement and made up some compelling-sounding, feature-laden but implausible reason. Gtalk has never sucked less than those two weeks with a working discreet client app and interoperability, though. It was actually adequate.
It's not a new project, it's just skinned Element. Jitsi does not have the features of Element.
Tchap is the Element-based server. Visio is a different thing. Although you can trigger Visio from Tchap (like you can do it with Jitsi from Element).
No such thing as an Element based server. The server is Matrix. Element is the app. Visio is not a different thing, it's just Element Call.
At first, I wrote "Element/Matrix" and decided to not be too pedantic... But if you want to be complete: the messaging protocol is, of course, Matrix. You could say there is actually no such thing as a Matrix server either, because it's a protocol. The server must probably be Synapse-based, I guess. But there is an "Element-based server" in the sense that the web interface of Tchap (and phone apps) are very clearly forked from Element, which is what I meant.
Visio is based on LiveKit, which Element Call is also based on (as far as I understand). It lives outside of Tchap. The DINUM never mentioned it was based on Element Call. Do you have additional information? (Not that the difference matters much I think)
A Matrix server is a server that uses the Matrix protocol. You could be more precise and say Synapse but that excludes community-developed forks like Continuity, Contunuwuity, Tuwunnel, etc. etc. So yes, I maintain that is the "correct" terminology.
Sure, if you want... ¯\_(ツ)_/¯
Aww, man... I just got þe popcorn out.
The irony is they used teams to notify all the sources.