Notices tagged with xmpp

If clients like this were developed for mobile GNU/Linux like #PureOS, #eOS, #PostmarketOS, as well as for #Android and #Sailfish, it could be a game changer. Although it would work better if creating a webmail account on a community-hosting service automatically created Jabber and Jami accounts associated with them. Which would require hosts to run an #XMPP server and a Jami ID #blockchain node.
https://jami.net/the-jami-blockchain-switches-from-proof-of-work-to-proof-of-authority/

In fact, the ultimate comms #UX might be a native client that could speak #email, #XMPP, and #Jami protocols. It would accept messages from either #Jabber or email servers, and deliver them to either a chat UI or a long-form email, depending on message length (a sane default # of characters that users can change in settings). When XMPP presence protocols and/or Jami protocols told users contacts are online, they could make a voice/video call using Jami protocols.

@kaniini I can't help but notice these talking points coming up repeatedly, about the existing *public* #fediverse not protecting privacy. What part of public are people not getting? If folks want fully private federated messaging, they can use networks running #Diaspora, #Zot, #SSB, #XMPP with #OMEMO, or #Matrix with encryption turned on. #OStatus can't do private, and although #ActivityPub can, nobody has implemented it well yet, and its meaningless without encryption (#E2EE).
@hellpie

Next time someone wants to create a web-based Jabber client, they would be better to make something different, eg a #Riot-like team chat UI, and again, have it warn users when they're connecting to a client/server that can't fulfill all its UI promises. That way the flexibility of #XMPP actually serves an asset, not a liability (user confusion), and the existence of multiple clients serves a useful purpose, rather than just reinventing the wheel and then dying.
@jcbrand
@Muto @debacle

@jcbrand flexibility is great, but what it means in practice is that while all sorts of things can be built with #XMPP core and different #XEP
combinations, those things don't automatically exist. They have to be defined as meta-standards, sets of XEPs that are compulsory to properly serve Use Case X (eg personal IM, team chat, social media).
@Muto @debacle

I'd really like to see a group of #Jabber champions take the #Riot source code and modify it to connect to servers using #XMPP, #MUC, and #OMEMO, instead of the #Matrix protocol. This would conclusively prove their constant claims that their preferred protocols can do everything Matrix can do. I would be curious to know what proportion of existing Jabber servers such a modified client could connect to without losing any functionality.
@bortzmeyer @imacrea

@bortzmeyer @imacrea
in theory, either protocol can be used for any kind of chat. But while the #Riot client is great for team chat, I haven't seen a #Matrix client with an instant messenger UI I would recommend for friends and family use. #Jabber (#XMPP) is the opposite. Apps like #Conversations (Android) and #Pidgin (desktop) are fine for one-to-one IM but I have yet to see a Jabber client that does group chat as well as Riot. This piece explains the differences well:
https://blogs.gnome.org/tbernard/2018/05/16/banquets-and-barbecues/

@imacrea if you can afford it, paying for an account on the conversations.im server is a good way to support the work on the app. Otherwise, Disroot.org, Riseup.net, and many other community-hosting groups offer #XMPP accounts. I believe the #Librem.one paid service does too.

@imacrea the best #XMPP app I've used in almost 20 years of testing is #Conversations on #Android. If there were XMPP apps with a similar or better level of polish for iOS, GNU/Linux, MacOS, and Windows, *and* the web, so users could sign up for a service and use a branded fork of the web interface without having to learn about server and client choice right away (as with email), it might be useable by mere mortals.

@404_city
Secure encryption is absolutely necessary. Thanks for coming up with a manifesto!

#privacy #encryption #xmpp

Unfortunately we were ridiculed by the community Disroot for making a manifesto https://github.com/E-404/Manifestos/blob/master/1.md According to some, secure encryption is unnecessary #xmpp

" #Telegram Messenger: We’re currently experiencing a powerful DDoS attack, Telegram users in the Americas and some users from other countries may experience connection issues"
Back go to decentralized Jabber aka XMPP https://xmpp-servers.404.city
Welcome to https://404.city/ Public #XMPP server

@kaniini maybe from a dev or sysadmin POV. From the POV of a user looking for a drop-in replacement for #Discord or #Slack, #XMPP currently offers nothing comparable with the #UX of #Riot.
@danyspin97

@dajbelshaw thank you! You mentioned #Framasoft on same episode where you mentioned the article about #WaldenPonding, and #Disroot is a similar swiss army knife of digital services using #FreeCode apps. They have email, #NextCloud, #XMPP and many other services.
@disroot

Let go! Manifest to disable any communication with servers that have untrusted certificates! #xmpp #jabber https://github.com/E-404/Manifestos/blob/master/1.md

@vector @calm

Maybe #Mastodon could move toward supporting built-in encrypted #XMPP, like Diaspora does.

It appears that #Diaspora have quietly dropped their buggy, awkward #XMPP chat feature. I just logged into my D* account for the first time in a while and I can't see any sign of it. Anyone know what happened there? If they have given up on integrated chat, that's a shame considering that @jcbrand made a pull request to replace their half-finished #JSXC integration with one based on #Conversejs *and* maintain it.
https://github.com/diaspora/diaspora/issues/7336#issuecomment-280913242

It appears that #Diaspora have quietly dropped their buggy, awkward #XMPP chat feature. I just logged into my D* account for the first time in a while and I can't see any sign of it. Anyone know what happened there? If they have given up on integrated chat, that's a shame considering that @jcbrand made a pull request to replace their half-finished #JSXC integration with one based on #Conversejs *and* maintain it.

What would the simplest single-user #XMPP server that could possibly work look like?

@tootbrute
> wish more stuff had built in mesh server functionality...

I want to see a serverless app like #Jami with a UI like #Conversations (#XMPP app for #Android). That way, the #UX is as seamless as that of an app for a centralized service, but as with #BitTorrent, everyone who's running the app is also "running a server", in the sense of sharing bandwidth and processing power with the network.