Currently translated at 4.2% (2 of 47 strings)
Translation: Conversations/App Store Metadata
Translate-URL: https://translate.codeberg.org/projects/conversations/app-store-metadata/gl/
Currently translated at 100.0% (47 of 47 strings)
Translation: Conversations/App Store Metadata
Translate-URL: https://translate.codeberg.org/projects/conversations/app-store-metadata/de/
Currently translated at 100.0% (13 of 13 strings)
Translation: Conversations/Android App (Conversations)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-conversations/vi/
Currently translated at 99.8% (965 of 966 strings)
Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/vi/
This requires not compressing it or cropping it unless we want to do *a lot*
more code, so file must be under 100k or we freeze it and no promises what your
non-square avatars will look like generally.
Currently translated at 99.8% (965 of 966 strings)
Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/vi/
e3a1211
UP: add custom extensions for app<->distributor interaction
Click to expand commit body
On registration the app can pass in a 'Messenger' to get a direct response
instead of having to somehow wait for the broadcast receiver to fire.
The app name can be passed as a pending intent which allows the distributor
to validate the sender.
Some things are banned by resourceprep that a user might wish to use.
If this happens, then punycode the resource so they can at least join the room.
Always send their chosen nick (not a mangled version) as <nick> in presence.
Always save their chosen nick (not a mangled version) in bookmarks (risky, since
if they try to use this bookmark from a client not supporting this it may not
let them join without changing nick).
If we get a <nick> in presence, then we respect it if it matches the punycode
decode of the resource (this is to prevent spoofing or double-naming since MUC
services won't be validating the <nick> at all right now. May relax this in the
future).
Save their actual nick (whatever we're actually showing, so <nick> if we used
that) into conversation attributes instead of assuming it will match the
resource.
Use resource for technical stuff (like PM addressing) and nick for display.
Hilight on both nick and resource so that mentions from legacy clients work.
Currently translated at 95.8% (926 of 966 strings)
Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/vi/
Currently translated at 98.9% (956 of 966 strings)
Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/sv/
Currently translated at 100.0% (13 of 13 strings)
Translation: Conversations/Android App (Conversations)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-conversations/fr/
Currently translated at 99.8% (965 of 966 strings)
Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/fr/
Currently translated at 98.3% (950 of 966 strings)
Translation: Conversations/Android App (shared)
Translate-URL: https://translate.codeberg.org/projects/conversations/android-app-shared/cs/