Soy usuario de Delta Chat pero tengo dos necesidades:Es necesario poder configurar dos o más cuentas de correo y chatear con todas ellas.Es necesario poder actualizar, arrastrando la pantalla hacia abajo y soltando, y conocer si hay conexión.Saludos.
Reading the las iOS beta released I realized this:
play voice messages and other audio
I tested that, a friend sent me an audio. I got it and hear it very good.
I would like to answer him but I can’t do that right now. I hope ASAP we will be able to send audios.
I appreciate so much these iOS betas. You are working hard. Congratulation.
coming tuesday, Oct 22nd, we'd like to revive for some time
a weekly "sync" meeting, until we have all platforms released stably.
tuesday 2pm CEST on #deltachat freenode.
If you don't have an IRC client you may try this link:
Main topic will be ongoing release activities. See also here
Probably makes sense to continue our last sync-meeting series practises
where everyone posted a three-point summary aka "LAST/NEXT/BLOCKERS" where
LAST and NEXT are an enumeration of issues/activities since last sync and
BLOCKERS is about things blocking activities.
Rust-core is getting more and more stable and is now part of recurring development
releases for Desktop, Android and iOS. Our overall release is tracked in
this github project: https://github.com/orgs/deltachat/projects/15
Dev releases are generally published to the respective github-releases pages.
and for iOS they also go to Testflight from time to time.
If you can help with testing releases out, filing bug issues/PRs and
checking if things are fixed ... that's much appreciated, also by
the many people who you thus help to avoid encountering the error ;)
below you find a note on the cleanup efforts after Rust-core started
existing from a C2Rust translated code base. We've come a looong way!
Rust-core cleanup effort status
We got rid a few days ago of the last "OK_TO_CONTINUE" patterns
which came from C-level "goto". So that column is gone and we now have
"unsafe fn" which indicate that a whole function is marked as unsafe.
We try to push this down to the actual function parts that are unsafe.
In any case, the current stats now look like this:
dc_tools.rs unsafe: 29 free: 10 unsafe-fn: 11 chars: 100
wrapmime.rs unsafe: 49 free: 1 unsafe-fn: 2 chars: 12
dc_mimeparser.rs unsafe: 22 free: 5 unsafe-fn: 10 chars: 27
dc_receive_imf.rs unsafe: 13 free: 3 unsafe-fn: 13 chars: 12
e2ee.rs unsafe: 27 free: 6 unsafe-fn: 0 chars: 5
pgp.rs unsafe: 1 free: 0 unsafe-fn: 1 chars: 19
imex.rs unsafe: 7 free: 3 unsafe-fn: 0 chars: 3
aheader.rs unsafe: 8 free: 0 unsafe-fn: 0 chars: 3
mimefactory.rs unsafe: 5 free: 2 unsafe-fn: 1 chars: 3
error.rs unsafe: 0 free: 0 unsafe-fn: 0 chars: 5
dc_strencode.rs unsafe: 1 free: 2 unsafe-fn: 0 chars: 2
stock.rs unsafe: 2 free: 1 unsafe-fn: 0 chars: 1
job.rs unsafe: 3 free: 0 unsafe-fn: 0 chars: 0
message.rs unsafe: 1 free: 2 unsafe-fn: 0 chars: 0
configure/mod.rs unsafe: 1 free: 0 unsafe-fn: 1 chars: 0
imap.rs unsafe: 1 free: 0 unsafe-fn: 0 chars: 0
context.rs unsafe: 1 free: 0 unsafe-fn: 0 chars: 0
lib.rs unsafe: 1 free: 0 unsafe-fn: 0 chars: 0
key.rs unsafe: 1 free: 0 unsafe-fn: 0 chars: 0
total unsafe: 173
total free: 35
total unsafe-fn: 39
total c_chars: 192
The incoming-message (mime-parsing and processing) pipeline remains the last
bigger worry. We have overall 4.83% unsafe out of 20538 overall code lines in
rust-core, according to cargo-count.