eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

224
active users

#deltachat

8 posts7 participants0 posts today

Comparing #XMPP against #email protocols is too limited. What sets #deltachat apart is *vertical integration* and being driven by UI/UX considerations. Cross-platform Apps and Bots use the Rust core library which connects with #chatmail relays and classic email servers based on a higher level API -- abstracting over SMTP, MIME, #OpenPGP etc. See chatmail.at

#webxdc apps in turn use an even higher level stable API abstracting over email/xmpp/... see webxdc.org/docs/

chatmail.atChatmailChatmail provides FOSS infrastructure for interoperable, secure, speedy and reliable end-to-end encrypted messaging. Check out clients as Arcane Chat, Bots or Delta Chat today!
Replied in thread

@pixelschubsi @treefit

The point is that DeltaChat didn't invent a new protocol, start something from scratch and write the software for it from the first line. As there is a saying:

Good programmers write programs from scratch. Great programmers find an already existing program and use it as a base.

#DeltaChat didn't invent #Email, #PGP, #autocrypt or new technology for #webxdc. Even WebXDC's real time channels don't use a technology invented by DC.

Considering that both #XMPP and #Matrix re-invented #decentralized communication while #email was already there, makes #deltachat more interesting.

The fact that DC didn't invent a new protocol for #InstantMessaging and just used the protocol which was already there, and also that how far has it gone, is mind blowing.

At first when I was chatting with @treefit, I already was developing a Matrix client(#chooj) for #KaiOS and it was the only decentralized IM which I was using and investing resources into. I was skeptical but then I thought it would be a good idea to invest into DeltaChat, as well as Matrix. His argument, of course, wasn't good. He was arguing that we need multiple options in the case one of decentralized IMs fail. However this convinced me to give DC a try.

But now, I see that DC has very unique advantages no other messenger has. Their moto is "playing the long term" game. Unlike Matrix which suddenly exploded, DC moves very slowly. As an advantage, DC is much more consistent, hassle free, has less bugs(in my experience) and has better UI/UX than many Matrix clients. But it has got several disadvantages. Matrix has tons more features which DC hasn't got or has added them just recently such as editing messages and reactions. And it is not yet suitable for public groups, like the ones we've got in the Matrix network.

Overall, if you want secure chat with friends or family or other people you trust, DeltaChat is a very good option and the experience is very good. And I haven't seen something like #webxdc in any other IM. However if you want something like #Discord guilds for a community, Matrix is the way to go.

BTW, DC currently lacks funding, thanks to what #Trump did with #OpenTechnologyFund(#OTF). If you can help in anyway, financial or otherwise, it will be extra valuable at this point.

Edit:

BTW, here are websites of webxdc and DC:

delta.chat
webxdc.org/

#IM#FOSS#Messenger

our friends over at @rpgp just published a monster milestone, humbly tagged 0.16 😍 with

- streaming decryption and encryption

- post-quantum-cryptography

- API streamlining.

#rPGP is a full Rust implementation of #openpgp which counts among the fastest and most compliant implementations today, and includes security audits. Note: #deltachat uses a restricted subset of OpenPGP, and follows best practices (eg using the same ed25519 keys implementation as #signal) github.com/rpgp/rpgp/

OpenPGP implemented in pure Rust, permissively licensed - rpgp/rpgp
GitHubGitHub - rpgp/rpgp: OpenPGP implemented in pure Rust, permissively licensedOpenPGP implemented in pure Rust, permissively licensed - rpgp/rpgp

Mensajería instantánea

De una conversación tecnológica:¿Da WhatsApp (WA) información a la policía?

El entendimiento general es que WA no da contenido de comunicaciones a la policía.

Da metadatos de comunicaciones a la policía, y los metadatos que da son sustanciales, ya que cosas como el nombre del grupo, descripción e icono son considerados «metadatos» por WA (no por Signal), e incluso contenidos de su agenda (y las agendas de sus contactos) se consideran metadatos.

Les defensoras de Signal señalarán que Signal no considera «metadatos» cosas como el nombre de grupo, la descripción o el contenido de la agenda.

La gente acostumbrada a servicios decentes como los de riseup, autistici/inventati, nadir, sinodminio, disroot o aktivix, siempre preferirán protocolos descentralizados donde cualquiera puede configurar su propio servidor federado, como delta.chat o xmpp; son los mejores.

Idealmente hospedados por colectivos decentes.

anatemas.noblogs.org/mensajeri
#General #BigTech #cifrado #deltachat #deltachat #GrandesTecnologicas #GrandesTenologicasNo #MensajeriaInstantanea #NoBigTech #privacidad #signal #Tech #tecnologia #WhatsApp #xmpp

anatemas.noblogs.organatemas : Mensajería instantánea
More from anatema
Replied to Tanja 🔜 GPN23

@tanja yes, there is a pre-discussed concept for sealed sender maybe along with sealed recipients while we are at it. Base idea is to use fixed-format alias chatmail addresses for recipients and allow unauthenticated sending from noreply@chatmailserver to such fixed-format alias addresses (which #deltachat devices learn about through chatting).

Replied to Delta Chat

@delta thank you so much for responding :3

Are there any plans for something like sealed-sender?

I imagine that'd be rather difficult with existing mail standards.

At least for me, Signals sealed-sender has never failed me yet (apart from the first message in new conversations), at least the sealed-sender icon appears in every message I've sent in the info screen.

(How) could this be implemented in #deltachat ?

Replied in thread
Esto es agotador. Tu experiencia de pasarse a Telegram y no perder demasiados contactos es bastante singular. Lo normal es que pasen de ti porque es raro que alguien quiera tener otra aplicación de mensajería, especialmente el grueso importante, que es tu familia más "mayor". Algunos sí, otros no.

La idea de pasarse a XMPP ya como que me remata, porque todo el trabajo de pasar a tu entorno recae en el que lidera la propuesta y para eso hay que tener entusiasmo y fuerza.

Tuve una época en la que estuve usando #deltachat con el correo electrónico y si hay que hacer esfuerzos en promocionar sistemas (en mi opinión) es en el correo electrónico. Mecanismo que empezamos a perder porque todo el mundo tiene uno, todo el mundo lo necesita, pero nadie quiere pelear por el suyo. Igual que con el fediverso.

When I send a message using @delta, can people in control of the chat server see who sent it?

Can people in control of the chat server know what group I'm sending to, if it's a group chat?

As far as I'm aware, @signalapp prevents at least the first one, and has mitigations for correlation attacks (where one user sends a message, and the same 5 others happen to receive one at the exact same time, every time). Does #deltachat have that?

Am I missing something here? :breadthink:

Replied in thread

@rohden Heh, you caught it :) Indeed bots running some LLM for audio transcription or image generation exist. But they are not part of the UI/UX of #deltachat itself, or of its #chatmail core Rust library. Bots and #webxdc apps are behind extension points where we intentionally don't control or even know what people use.

Replied in thread

@vascorsd I had something similar to that happen to me recently as well. I'm using a #prosody server, and I have my:

archive_expires_after = "5w"
... set in /etc/prosody/prosody.cfg.lua

Messages should be archived for 5 weeks.

Then messages sent in Gajim on one linux laptop were lost, when a second #Linux laptop who was subscribed to the same group, was turned off (absent from receiving messages) for 3 weeks. 2.75 of the 3 weeks worth of the group messages (where the laptop was turned off) silently never showed up, when #Gajim was re-opened on the second laptop.

This bodes very badly for me recommending XMPP to others. I now consider #DeltaChat to be a secondary choice, should something happen to #Signal (which is currently my privacy-respecting Messaging app goto).

Other clients who chatted in that same group, BTW: the latest stable #Monal in #iPadOS, and #Conversations in #Android

Prosody version is 13.0.0-1~bpo12+1, backend is sqlite, Gajim is 2.1.1. It was a private MUC, and OMEMO was used as much as possible.

By design, end-to-end-encrypting #deltachat and #webxdc apps only need ephemeral transport. It's a big deal. Let's compare:

- #matrix home servers maintain a cryptographic forever-chain of cleartext social-graph metadata.

- #WhatsApp servers maintain cleartext metadata visible to Meta.

- #Signal keeps encrypted metadata, hosted at GAFAM

#chatmail relays do not persist any social graph state, also not in encrypted form. A key goal of our designs: chatmail operators can sleep well at night :)

The last two days saw the number of push notifications spike. Sometimes 80K Google Play push notifications happened per hour, while the baseline was more around 10-20K. These spikes probably indicate Internet availability. #deltachat is offline-first: you can write messages and attach media, create groups, use #webxdc apps, setup a second device etc. all without any Internet. Once it returns queued messages are sent out and cause push notifications. #OfflineFirst is crucial for resiliency.