Το πρωινάδικο Καφενείο μετακόμισε σε delta Chat!!!
Αύριο τα εγκαίνια :)
Σας περιμένουμε είτε με original #deltachat client
https://f-droid.org/packages/com.b44t.messenger/
Είτε με #arcanechat που μας αρέσει περισσότερο :)
Το πρωινάδικο Καφενείο μετακόμισε σε delta Chat!!!
Αύριο τα εγκαίνια :)
Σας περιμένουμε είτε με original #deltachat client
https://f-droid.org/packages/com.b44t.messenger/
Είτε με #arcanechat που μας αρέσει περισσότερο :)
Hi ha una campanya en marxa a nivell global per a #migrar de Whatsapp a #DeltaChat aquest proper dia 1 de febrer del 2025.
https://mastodon.social/@adbenitez/113895429021642700
Android:
https://play.google.com/store/apps/details?id=chat.delta&hl=ca_ES
iOS:
https://apps.apple.com/es/app/delta-chat/id1459523234?l=ca
#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": https://gultsch.social/@daniel/114012904576436518
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)
#prosody #conversations #gajim #dino #snikket #monocles #monal
To Καφενείο group στο #deltachat με καθημερινό wordle, miniblog σας περιμένει.
Even though #Signal *itself* has sound security - taken in isolation - it's always moored in an ecosystem (that of smartphones which run #iOS or #Android) which, by default, have #AI set up to shoulder-surf Signal, sending reports back to the mothership. In #iOS, that AI is called "#Apple Intelligence", and in #Android, it's called #Google Assistant. Repeat, these are on by default. *Only a small percentage of your family, friends, colleagues, and fellow country-persons will pain-stakingly disable these.*
Sure, Signal itself is secure by default, but "a chain is only as strong as its weakest link". And the weakest link is the ecosystem which Signal is moored in - that of smartphones policed and patrolled by AI, which report back to their respective motherships *in a strong majority of cases*.
Alternatives like #Deltachat (for normies willing to open their wallets/purses to rent an auto-crypt-compatible email address) and #XMPP (easily free to use, however realistic and mature only for non-iOS/#MacOS-users at present) have comparable E2E encryption. Deltachat and XMPP *don't* require smart-phone "moorings" - thereby making it much more realistic to dodge the almost-pervasively AI-patrolled ecosystems.
#Signal took a huge bet that running on US big-tech toxic infrastructure is fine because its groundbreaking and industry-shaping cryptography is crafted to neutralize it and keep users safe.
But is it really feasible to live on toxic infrastructure in the longer run?
#deltachat rather takes a bet on the massive e-mail server network and interoperable protocols, and on #chatmail servers which enforce message encryption and metadata-minimization.
Delta is for when centralization turns sour.
从 @th0mas@pawoo.net 转生
#DeltaChat 邀请请看个人资料短链接
V2 #deltachat is rolling out after weeks of internal testing, a major milestone revising how end-to-end encryption works and bringing more beautiful contact and group profiles, direct access to chat-shared apps in the title bar and a "new email" action with setting a subject for those using a classic server.
Best of all, users and developers don't need to co-ordinate anything for upgrading to V2 despite the massive security rework behind the scenes :)
What if a state tries to mandate us as #deltachat app devs/distributors to shut down a chat profile?
Nothing. It can't be done.
We have no list of chat identities, have no handle or data about them, and don't mediate the message transfer.
However, EU #Chatcontrol politicians and Russian authorities would want us to insert backdoors into our FOSS code. But that is nothing than can happen overnight, and we are fine with friendly forks already. Resilient private internet communication ftw :)