@kai Well, I do like the #Prosody !XMPP server--easy to set up and works very well, except when it doesn't--but I think I'm going to use #ejabberd next time I set one up.
Please can you quantify what makes IRC/XMPP as protocols, free to implement as anyone wants, worse than the centrally controlled Discord, only implementable as Discord allows?
Also: please explain something about !XMPP or IRC that is "hard to use" where Discord excels, but avoid anything that is so because Discord is centrally controlled (your desire was to have something federated, so be constructive).
@amic #Prosody is mostly very easy and reliable, but when it doesn't work, there's no easy solution besides waiting for several months until it miraculously starts to work again. You can try #ejabberd, #OpenFire, or (according to a certain account here) #Tigase in those situations. !XMPP
There are multiple #Matrix clients under development. I don't know whether they use the outdated proposal or just do what Riot does.
I don't know why so many pro-Matrix people are anti-XMPP and against every other attempt to build federated communications. With their emphasis on bridges to other services, they should be saying "sure, we can co-exist and interoperate with !XMPP and #IRC and whatever else, as long as bridges are allowed".
Work together to build something better than the #corpocentric solution of the day instead of squabbling over which one is right or better.
@rw A few family members complain that I can’t see their calendar events, but the biggest annoyance I have with not being a #Facebook user is all the people that say “did you see what cousin so and so just said?” and then stick their phones in my face.
If I wanted to see all that random garbage, I would still have an account.
Yes, but how can we get in touch with you?
Let me count the ways:
* call
* text
* !XMPP
* #Wire
* #Ring / #Jami
* e-mail
* in person
* contact any of my sons, nephews, siblings, my youngest niece, the cousin that lives in TX, or my mom and ask them to forward
Oh, the #Tigase !XMPP client’s #iOS version is now called #Siskin_IM. I will probably try it out soon. #Monal, my current client, appears to only operate when in the foreground. (Likewise for the #Mutter #IRC client, so that may be an #Apple restriction.)
@tigase You misunderstood my post from December. One individual asked another individual which !XMPP server software the second person had used. I responded with the names of the two that I usually see in the “single user or small group” context. No one was “recommending” software, nor was anyone seeking recommendations. In that context, mentioning #Tigase #XMPP server would have been the wrong thing to do.
Like most iOS software, my reaction while using it is “F*ck! F*ck! F*ck!” until I close the app. Tell the #CIA that they can legally waterboard any #iDevice user, since they are already used to torture and seek it out.
That was the #Yaxim !XMPP service and the Yax.im client. I never did figure out whether it was their server or the client which auto-accepted those requests and disallowed rejecting. I just abandoned both the service and the client entirely.
Years ago, I was able to make voice calls to #sonOne and #sonTwo using #Jitsi (the !XMPP and SIP client, not the #WebRTC service), but setup was agony, and I'm not 100% sure whether we used #XMPP or SIP as the transport.
@infernalturtle !XMPP
.
I also noticed that chatme.im is not working. First, my mobile client complained about an unannounced certificate change. Then, a few days later, it seemed completely down.
. xmpp:lnxw37@xmpp.is or xmpp:lnxw37@404.city
@bob @moonman @anachosaurus@social.fsck.club I've said for years that the XSF should endorse a bundle of XEPs, integrate them into !XMPP and release it as version 1.1. That way, all updated and compliant servers and clients once again have a common base to interoperate on.