<p>Deixo aqui este primeiro rascunho.</p><p>São bem-vindas sugestões, correções...</p><p>Obrigado!</p><p><a href="/tags/xmpp/" rel="tag">#xmpp</a> <a href="/tags/conversations/" rel="tag">#conversations</a> <a href="/tags/monocleschat/" rel="tag">#monocleschat</a> <a href="/tags/quicksy/" rel="tag">#quicksy</a> <a href="/tags/monal/" rel="tag">#monal</a> <a href="/tags/whatsapp/" rel="tag">#whatsapp</a> <a href="/tags/telegram/" rel="tag">#telegram</a></p>
monal
<p><a href="/tags/xmpp/" rel="tag">#XMPP</a> enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?</p><p>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. <a href="/tags/android/" rel="tag">#Android</a> doesn't have that as an allowable field, and <a href="/tags/thunderbird/" rel="tag">#Thunderbird</a> and <a href="/tags/nextcloud/" rel="tag">#Nextcloud</a> 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:"*</p><p>So "[email protected]" is not an OK XMPP address, but "xmpp:[email protected]" is.</p><p>Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": <a href="https://gultsch.social/@daniel/114012904576436518" rel="nofollow" class="ellipsis" title="gultsch.social/@daniel/114012904576436518"><span class="invisible">https://</span><span class="ellipsis">gultsch.social/@daniel/1140129</span><span class="invisible">04576436518</span></a></p><p>It might be a long time before the address synchy-ness ever works again between Android <-> <a href="/tags/davx5/" rel="tag">#Davx5</a> <-> Nextcloud <->Thunderbird</p><p>Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:". </p><p>(<a href="/tags/deltachat/" rel="tag">#DeltaChat</a> gets to gloat hard here, as they have plain-old email addresses)</p><p><a href="/tags/prosody/" rel="tag">#prosody</a> <a href="/tags/conversations/" rel="tag">#conversations</a> <a href="/tags/gajim/" rel="tag">#gajim</a> <a href="/tags/dino/" rel="tag">#dino</a> <a href="/tags/snikket/" rel="tag">#snikket</a> <a href="/tags/monocles/" rel="tag">#monocles</a> <a href="/tags/monal/" rel="tag">#monal</a></p>
Edited 1y ago
<p>Heute ist <a href="/tags/diday/" rel="tag">#DiDay</a></p><p>Der Digital Independence Day ist eine tolle Initiative, deren Werte wir zu 100% teilen. Die Empfehlung für Signal ist allerdings ein Schritt in die falsche Richtung und treibt Nutzer von einem geschlossenen System in ein anderes.</p><p>Zum Glück gibt es auch Wechselrezepte für die Independent Messaging Apps <a href="/tags/quicksy/" rel="tag">#Quicksy</a>, <a href="/tags/monal/" rel="tag">#Monal</a> und <a href="/tags/conversations_im/" rel="tag">#Conversations_im</a>, die wirkliche Souveränität bieten.</p><p>Ein Wechsel zu Quicksy ist genauso einfach wie ein Wechsel zu Signal.</p><p><a href="https://imday.de/de/" rel="nofollow"><span class="invisible">https://</span>imday.de/de/</a></p><p><a href="/tags/didit/" rel="tag">#DIDIt</a></p>
Edited 64d ago