In diesem Video erkläre ich euch, wie ihr durch das Hinterlegen einer Mail-Adresse eine Möglichkeit für einen Passwort-Reset für eure XMPP-Adresse bei conversations.im schafft.
yep, I have similar feeling of it. Still using #xmpp with my family members. It's much simpler to host and it just works. It has good android app #conversations and pc apps #dino and #gajim
Even as a non-developer, I found this well written article of great interest. It explained a few things about #UnifiedPush I wasn't aware of, and has given me better insight into how it functions.
It's clear now that there simply isn't any excuse for developers to use #FCM for notifications. I sincerely hope UnifiedPush will gain traction, not only amongst #FOSS developers, but the Android developer community at large.
It's perhaps worth noting that users of #Conversations (and its forks) already have a distributor included in their client, thus further lowering the bar of entry.
Message retraction is a good thing but not supported by others clients (for example #conversations for Android). I wish you implement audio and video calls like @dino does... #XMPP
That story began with a friend of mine that had got a XMPP group chat where they shared updates and pictures of their latest travel adventure. Now chat is rather ephemeral and they wanted to preserve those memories in an easy accessible format that is PDF. And so I put something together.
* actually any chat as long as you can get the raw data in the expected format
My grandmother recently got locked out of #WhatsApp because her phone broke, and the spare one we had on hand is one WhatsApp has decided is too old to run on 💀
Fortunately, #XMPP has no such qualms! She's currently keeping up with the family group chat on #Quicksy while others of us use #Conversations, #DinoIM, and #Gajim. (Of course, extended family and friends are another matter 😔)
This serves as a reminder that closed apps may close you out—but open protocols have your back forever!
Why don't you include the federated #XMPP (aka Jabber) protocol as an alternative? There are plenty of good clients for the phone and PC, like #Conversations, #gajim, or #dino. With the modern extensions like Omemo E2EE and various improvements for mobile use, it is very useable even on phones, while keeping the flexibility and resilience of a federated service (just like the Fediverse).
@Peter Vágner @Dieguito 🦝🧑🏻💻🍕 How conversations work is not unified all across the Fediverse. Even how connections work is not unified.
Mastodon has taken over the follower/followed principle from Twitter which is always illustrated with arrows with one point. A following B is illustrated with an arrow from A to B. A being followed by B is illustrated with an arrow from B to A. A and B following each other mutually is illustrated with one arrow from A to B and one arrow from B to A.
It appears to me that Friendica has adopted this to become more compatible with Mastodon. But its several descendants, created by Friendica's own creator, starting with Hubzilla, haven't.
Hubzilla, (streams) and Forte still have the bidirectional "connection" or "contact" as the default. It's illustrated with one arrow, but with one point on each end.
Also, all three understand a threaded conversation as an enclosed contruct entirely owned by the conversation starter. Everyone on these three who has the start post on their stream always actually has the whole thread on their stream.
In fact, all three have Conversation Containers implemented. This feature was originally created in the streams repository in 2022. Forte has had it from the get-go as it started out as a fork of (streams). It was eventually turned into FEP-171b and backported to Hubzilla last year.
All three make sure that everyone who has a post on their stream also always has all comments on that post, at least those that are made after they have received the post.
This works on two basic principles:
All comments go directly to the original poster because the original poster owns the thread.
Those who have the post automatically receive all comments from the original poster.
In a pure Hubzilla/(streams)/Forte system, your above example would look like this:
User 1 and User 2 are connected.
User 1 and User 3 are connected. (This doesn't even matter.)
User 2 and User 3 are connected.
User 2 and User 4 are connected.
Much simpler than explaining everything with "following" and "being followed", isn't it?
Now, the conversation works like this.
User 2 sends a public post, thus creating a Conversation Container of which they are the owner. User 1, User 3 and User 4 receive the post.
User 3 comments on User 2's post. The comment goes from User 3 to User 2, who is the owner of the conversation, and it is automatically forwarded to User 1 and User 4 who already have User 2's post on their streams.
User 4 comments on User 3's comment. The comment goes from User 4 past User 3 straight to User 2, who is the owner of the conversation, and it is automatically forwarded to User 1 and User 3 who already have User 2's post on their streams.
The only mentioning that occurs here, if any, is User 4 mentioning User 3. This is not necessary for User 4's post to reach anyone. This is only necessary to make sure on Hubzilla (which doesn't have a tree view) that User 4 is replying to User 3's comment and not to User 2's post.
On Mastodon, for comparison, everything depends on who follows whom, who mentions whom and whose instance knows whose instance.
#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?
My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*
So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.
Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": gultsch.social/@daniel/1140129…
It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird
Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".
(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)
Werft mal einen Blick auf die Messenger-Matrix. Trotz aller Bemühungen kann es sein, dass nicht alle Informationen zu den Messengern aktuell sind. In diesem Fall bitte ich um Rückmeldung, damit ich die Matrix anpassen kann. ❤️ 👇
Die Messenger-Matrix bietet einen Überblick über die verschiedenen (technischen) Merkmale diverser Messenger.
Die Matrix wird auf www.messenger-matrix.de gehostet.
I've noticed that, for me and my wife at least, #Signal isn't always reliable for time sensitive messages. Even after exempting it from the Android power saving and everything it's almost like it goes to sleep sometimes and notifications don't pop until we open it up. The #XMPP app Conversations.im however is very reliable. Running a packet capture on my phone shows that when switching networks #Conversations immediately reconnects, but Signal doesn't, sometimes for several minutes.
#Monal 6.4.0 #xmpp client for iOS just got released 🥳 (the macOS build is still pending Apple's review).
Notable changes are: - support for channel management - a complete rework of group management ui - SVG support for received images and avatars - complete restructured settings menu resembling #Conversations' new settings menu - many bugfixes and better translations
With Message Displayed Synchronization Conversations is now able to synchronize the read state (displayed) state of public conferences across multiple devices.
Auf fast jedem Smartphone läuft heute ein Messenger, meist die Datenschleuder WhatsApp. Für alle, denen Privatsphäre wichtig ist, beschreiben wir Alternativen
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
I don't use monocles, but I suspect it uses the same approach than Cheogram and display reactions as replies indeed. It should get better once #Conversations 3 is out I suppose.
In den fünf Jahren seines Bestehens setzt der Android Jabber/XMPP client immer wieder Maßstäbe in Sachen Bedienbarkeit und Zuverlässigkeit. Doch was steckt eigentlich dahinter? Nutzen wir die Gelegenheit um mit dem Entwickler zusammen hinter die Kulissen eines neuen Features zu schauen; Wie tief muss man in die XMPP Trickkiste greifen und wo steht sich XMPP manchmal selber im Weg? Nach der Vorstellung des Features (der Vortrag ist gleichzeitig der Zeitpunkt an dem die neue Version veröffentlicht wird) geht es jedoch nicht nur um XMPP sondern auch um grundsätzliche, architektonische Fragen die sich potentiell auf andere Instant Messaging Dienste übertragen lassen.
Der Datengarten ist eine regelmäßige Veranstaltung des CCC Berlin.
Der Datengarten ist eine Vortrags- und Projektreihe im Rahmen des Club Discordia. Regelmäßige Datengärten finden an jedem 2. Dienstag im Monat ab 20 Uhr statt (der Dienstag nach dem Netzpolitischen Abend der Digitalen Gesellschaft).
#XMPP #CertWatch said that »[My] settings are correct and no MITM was detected.« That's great.
It then continued with some #PubSub stuff and finally said »If you do not have a pubsub-capable client you can subscribe for text notifications by opening a chat with certwatch.xmpp.net and sending the message “subscribe <my xmpp server>”«.
My question is now: How do I open a chat with a hostname and not a JID?
@🆃🅸🅼🆃🆃🅼🆈 @Snikket @thomholwerda #XMPP is excelent choice although unfortunatelly #Dino is not keyboard and #screenreader accessible on linux and windows thus it may not suit some people. For majority I think it's awesome. #Conversations is fully accessible and hopefully it'll stay like this in the future.
The Android XMPP client Conversations.im can now act as a UnfiedPush¹ Distributor. This means apps like Tusky can use XMPP as a transport for their push mess...
