I see a lot of posts here about why the other social media platforms are terrible & #Mastodon is the one to rule them all*.
Personally, Mastodon is my favorite & I prefer the #fediverse with decentralized servers & open source standards.
But I also don’t mind coexisting with the others. Rather, I think it’s a good thing. All of us should settle in where we feel comfortable & find community.
Overstatement, but a Tolkien reference always seems appropriate.
Recommendations, please, for making an #XMPP audio/video call work between:
a user on iOS and a user on Android
a user on iOS and a user on Linux
Messaging works fine, as does a/v between Linux and Android, but I have yet to find a combination which works for audio / video with an iOS device in the mix.
@neil if you self host (or not), #Snikket works quite well, which is based on #Siskin IM on #iOS and #Conversations on #Android. On GNU/Linux, #Dino is working, otherwise #Movim and #Converse should work (web clients). I believe they all work between themselves (for one2one calls).
Be sure to have an XMPP server with STUN/TURN activated (it's precious to cross NAT/Firewalls).
For the record, I'm implementing A/V calls in #Libervia too, thanks to an #NLnet grant.
Add a friend's contact. For starter, it's OK to add me purplesky@movim.eu.
Start chatting.
Note: #Movim enables you voice and video calls as well as photo and file sharing. On Android phone, you can try #Conversations to login to Movim and chat.
@ilyess that means that it is not open source. how come you believe some software which is dependent on a server which is not open source.. to be open source? i dont understand you.. sorry. end of discussion. btw use #xmpp#conversations :is_this:
@ilyess that means that it is not open source. how come you believe some software which is dependent on a server which is not open source.. and a code that doesn't have reproducible builds.. an unsuable code.. how do you define open source then? i dont understand you.. sorry. btw use #xmpp#conversations :is_this:
Just for discussion. I don't think that #XMPP / #Jabber was killed by big corporations and/or embrace-extend-exstinguish stuff, despite some harm could probably be.
First of all, it wasn't killed. It exists very well, but people rarely use it. I would try to outline a few reasons which could contribute.
The "original" XMPP does not meet any modern requirements. People expect stability in mobile networks and other unstable internet, synchronization over devices and multimedia. All this was introduced only by later XEPs and is barely supported. I can recall only #Gajim on #desktop and #Conversations on #Android among the clients supporting Stream Management + Message Carbons + Message Archive Management + Receipts + HTTP Upload (about Jingle - I wonder if it ever worked at all). Moreover, when you try to adapt it for your needs, you can easily end up as a troubleshooting admin - some things just work wrong or occasionally.