#MonoclesChat will be available for free on the Google Playstore starting this December 24th and up to the 31st ! So get your friends and family together and don't miss out on the opportunity to install and onboard them in one of the most beautiful and featureful #XMPP clients available on Android! Give them the best present ever: set them free from invasive, data harvesting, centralized IM networks!

https://play.google.com/store/search?q=monocles+chat&c=apps

#RunJBR #PrivacyIsAHumanRight #DigitalSovereignty #Decentralization

I’m happy to announce the 12th annual Holiday season Conversations giveaway. 🎄☃️

The federated instant messaging client is now available for free on Google Play until New Year’s Eve. 🧨🎆

Merry Christmas, Happy Holidays. Enjoy #39C3.

https://play.google.com/store/apps/details?id=eu.siacs.conversations

#XMPP #Jabber #Conversations_im #DigitalSovereignty #Fediverse

#MonoclesChat will be available for free on the Google Playstore starting this December 24th and up to the 31st ! So get your friends and family together and don't miss out on the opportunity to install and onboard them in one of the most beautiful and featureful #XMPP clients available on Android! Give them the best present ever: set them free from invasive, data harvesting, centralized IM networks!

https://play.google.com/store/search?q=monocles+chat&c=apps

#RunJBR #PrivacyIsAHumanRight #DigitalSovereignty #Decentralization

I’m happy to announce the 12th annual Holiday season Conversations giveaway. 🎄☃️

The federated instant messaging client is now available for free on Google Play until New Year’s Eve. 🧨🎆

Merry Christmas, Happy Holidays. Enjoy #39C3.

https://play.google.com/store/apps/details?id=eu.siacs.conversations

#XMPP #Jabber #Conversations_im #DigitalSovereignty #Fediverse

"Sharing is caring" said #Whatsapp .. then took all the details from every contact in your contacts list and left ... never to be seen again ... or give you anything in return ...

#RunJBR #XMPP #PrivacyIsAHumanRight #Privacy

"Sharing is caring" said #Whatsapp .. then took all the details from every contact in your contacts list and left ... never to be seen again ... or give you anything in return ...

#RunJBR #XMPP #PrivacyIsAHumanRight #Privacy

@maikel

Maybe it's just me, but:

#XMPP is the protocol, like "HTTP" or "SMTP" etc.

#Jabber is open, federated, standard chat. Similar to "web" or "email".

CiscoJabber™ is that thingy nobody cares about, not even Cisco.

My partner (du-jour) struggles to configure Conversations because there's no Spanish translations of it. He can't disable its nofications on his watch because of this.

And I would be happy using Monocles if WebXDC worked without cumbersome steps in between (read the issue before this toot). I can follow those steps with @surfhosting because we're tech saavy, but most of humanity isn't. Hence they need Whatsapp simplicity.

UX rule number 1 = if users need a manual you've failed. This is pretty much the reason Apple refries tech better. They are a UX-centred company. It's also why it bores power-users.

#XMPP #WhatNeedsDoing

8. Stick to a name either Jabber or XMPP, not both. It's confusing.
9. Make people aware of how many things are Jabber in disguise (Whatsapp, Grindr, Google Hangouts, etc) with a corporation behind monetising it using the people as the product.
10. Incentives for running servers. In Mastondon we're really good at justifying donating to our admins when they run a decent service.
11. RFCs or XEPs written as easy to read an implement as NIPs.
12. Attached directories. XMPP is directoryless same as email, what about searching people by their Mastodon handle, by their email handle, use WebFinger.

#XMPP #WhatNeedsDone

RE: https://gultsch.social/@daniel/115751087451745641

1. Rivaling clients to Whatsapp.
2. Incredible simplification, people don't want, cannot afford to learn what OMEMO is, "this message has been encoded for another device" is a humongous UX failure.
3. Consistency among clients.
4. Consistent "send voice message" button, consisten "send short video" button, consistent "send live location" button. Go to reason 1.
5. Less FOSS now, paid later projects. Why are most free on F-droid and paid-for in Google Playstore?
6. An iOS client that doesn't look as ugly as Shrek doing yoga.
7. Clip button should only be for attachments, not for everything (Conversations)

#XMPP #WhatNeedsDone

I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:

• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.

• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack

• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.

As a community, we often ask ourselves how to attract more users to #XMPP. Yet the real tragedy is that people would rather build something entirely new (loosely based on email or #ActivityPub) than consider XMPP. Need end-to-end encryption by default? If compatibility with existing XMPP clients is a secondary concern, you can implement it in your own solution while still benefiting from our two decades of experience in instant messaging.

I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:

• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.

• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack

• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.

As a community, we often ask ourselves how to attract more users to #XMPP. Yet the real tragedy is that people would rather build something entirely new (loosely based on email or #ActivityPub) than consider XMPP. Need end-to-end encryption by default? If compatibility with existing XMPP clients is a secondary concern, you can implement it in your own solution while still benefiting from our two decades of experience in instant messaging.

@bonfire @swf @sovtechfund @benpate Ooof, just another instant messenger..?

We've already had XMPP since the 90s... and since then it's become pretty reliable.

i hope there'll at least be interoperability. I'm so tired of new waya to communicate that are not interoperable with what's already there.

#xmpp