Discussion
Loading...

Discussion

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Daniel Gultsch
Daniel Gultsch
@daniel@gultsch.social  ·  activity timestamp 2 weeks ago

@ableijs The Matrix ecosystem is primarily dominated by one VC funded company. The server that everyone uses is developed by them. The client that everyone recommends is developed by them.

There are some baby steps towards a slightly more diverse ecosystem but for now it's a toss up between whether that's going to happen and enshittification once the VCs want their money back.

XMPP on the other hand is a healthy diverse ecosystem with various stake holders.

  • Copy link
  • Flag this post
  • Block
Océane
Océane
@oceane@gotosocial.social replied  ·  activity timestamp 2 weeks ago

@daniel Signal is an E2EE’d concurrent to Telegram and WhatsApp, whereas XMPP is a concurrent to MSN, Facebook, and ICQ. Recommending XMPP to someone looking for state-of-the-art E2EE and asserting Signal on every use case are both unacceptable.

  • Copy link
  • Flag this comment
  • Block
Kris
Kris
@kris@outmo.de replied  ·  activity timestamp 2 weeks ago
@oceane @daniel You knowledge about XMPP is very outdated. It literally uses the Signal encryption algorithm for it's OMEMO e2ee. There are a few things that can be still improved about it (mostly clients catching up to the latest version of the OMEMO specs), but it is very much a viable alternative to Signal in regards to e2ee.
  • Copy link
  • Flag this comment
  • Block
antoniovr
antoniovr
@antoniovr@mastodon.social replied  ·  activity timestamp 2 weeks ago

@kris @oceane @daniel i was an xmpp user 20 years ago.But the fall wasnt only due to defederation. It was also cause it wasnt working properly when u had several devices connected simultaneously(depending on priority &connectivity messages were arriving to one device or the other).There was a fix(some server storage) but not all servers implemented it.With the encryption most are using omemo but there is still no encryption and pgp based...I think its easier to attract people to signal&matrix

  • Copy link
  • Flag this comment
  • Block
Daniel Gultsch
Daniel Gultsch
@daniel@gultsch.social replied  ·  activity timestamp 2 weeks ago

@kris @oceane @antoniovr Those fixes have been widely implemented about a decade ago https://gultsch.de/posts/the-state-of-mobile-xmpp-in-2016/

Daniel Gultsch

The State of Mobile XMPP in 2016

XMPP is not suited for mobile devices. That’s a myth that has been around for ages. It is mostly spread by people who want to sell you their own proprietary instant messaging solution. But it also gained some popularity through a blog post entitled The (Sad) State of Mobile XMPP in 2014 by Georg Lukas. While Georg wasn’t wrong with his status report per se, it is important to understand that he describes a temporary problem. There was a brief period of time where XMPP actually had some catching up to do. XMPP was fine before, when we had different requirements—In fact I was using an XMPP client on my Nokia E71 back in 2008 (That’s more than two years before WhatsApp was even invented)—and it’s fine now in 2016.
  • Copy link
  • Flag this comment
  • Block
Arne Bleijs
Arne Bleijs
@ableijs@mstdn.social replied  ·  activity timestamp 2 weeks ago

@daniel
Agree. Signal is not federated, so all of it is subject to the US cloud act.

Any advise about #Matrix?

  • Copy link
  • Flag this comment
  • Block
Daniel Gultsch
Daniel Gultsch
@daniel@gultsch.social replied  ·  activity timestamp 2 weeks ago

@ableijs The Matrix ecosystem is primarily dominated by one VC funded company. The server that everyone uses is developed by them. The client that everyone recommends is developed by them.

There are some baby steps towards a slightly more diverse ecosystem but for now it's a toss up between whether that's going to happen and enshittification once the VCs want their money back.

XMPP on the other hand is a healthy diverse ecosystem with various stake holders.

  • Copy link
  • Flag this comment
  • Block
Benedict
Benedict
@benkuly@dresden.network replied  ·  activity timestamp 2 weeks ago

@daniel @ableijs
I could say the same thing about XMPP. But if I'm uninformed, I don't publicly write down any assumptions or information that is 10 years out of date.

There are a bunch of server and even more client implementations. Yes, @element still has a lot of influence, but The @matrix Foundation is doing it's best to get independent and is funded by a really diverse ecosystem.

For example I'm the founder of a company based in #Dresden building on #matrix. Our Open Source client SDK #trixnity is used in the TI-Messenger of every public health insurance company but one - so possibly millions of users. We also have an Open Source client #Tammy. Yes, we still have the problem, that Element is recommended by a lot of people but the same problem applies to a lot of Open Source ecosystems including #xmpp.

I'm pretty sure the ecosystem would survive without Element despite the fact that Element is doing a good job in pushing the ecosystem in the right direction despite the VC.

  • Copy link
  • Flag this comment
  • Block
Daniel Gultsch
Daniel Gultsch
@daniel@gultsch.social replied  ·  activity timestamp 2 weeks ago

@ableijs I develop a client for Android and I basically can't make any unilateral decisions without involving two client developers (Desktop + iOS) and/or two different server developers from the two major server implementations. And that's a good thing!

  • Copy link
  • Flag this comment
  • Block
Arne Bleijs
Arne Bleijs
@ableijs@mstdn.social replied  ·  activity timestamp 2 weeks ago

@daniel
Thnx. This is what I wanted to learn.

  • Copy link
  • Flag this comment
  • Block
Alexandre Oliva
Alexandre Oliva
@lxo@snac.lx.oliva.nom.br replied  ·  activity timestamp 2 weeks ago
nod

remember when every gmail account got an associated XMPP account, and regular people would chat with other XMPP users until Google broke federation?

XMPP was already more than good enough back then. and the users were there.
  • Copy link
  • Flag this comment
  • Block
Râu Cao ⚡
Râu Cao ⚡
@raucao@kosmos.social replied  ·  activity timestamp 2 weeks ago

@daniel Yeah, similar to recommending silo-to-fedi bridges for example. As long as others can find your content in the silo, there's no incentive to use the open alternative.

  • Copy link
  • Flag this comment
  • Block
Zash
Zash
@zash@fosstodon.org replied  ·  activity timestamp 2 weeks ago

@raucao @daniel@gultsch.socia Indeed! But on the other hand, bridges allow early adopters to move, so they're a double-edged tool if anything.

  • Copy link
  • Flag this comment
  • Block
Nicoco
Nicoco
@nicoco@pouet.pas.la replied  ·  activity timestamp 2 weeks ago

@zash @raucao anecdotical data point to support this: I started using XMPP because it had good bridges to silos. It lead me to (modestly) contribute to slixmpp, gajim and write some prosody modules. I very much doubt bridges between proprietary silos and open networks hinder adoption of the latter. Of course, this is very hard to quantify objectively.

  • Copy link
  • Flag this comment
  • Block
CryptGoat
CryptGoat
@cryptgoat@fedifreu.de replied  ·  activity timestamp 2 weeks ago

@daniel Yes. But if the messages they might mover over too is way less convenient and fun on the feature and UI aspects. None of the XMPP based messsengers come even close to Signal, Telegram or WhatsApp in this regard.

People really like stories, proper voice message handling, GIFs, stickers, polls and so on and often decide to stick with the service which provides these fun, usability and convenience features - or abandon the inferior alternative rather fast.

  • Copy link
  • Flag this comment
  • Block
CryptGoat
CryptGoat
@cryptgoat@fedifreu.de replied  ·  activity timestamp 2 weeks ago

@daniel Just not true for too many people.

People really like stories, proper voice message handling, GIFs, stickers, polls and so on and often decide to stick with the service which provides these fun,usability and convenience features.

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.7 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct