<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks!</p>
<p>I guess it doesn't read the old chats that are in the "DeltaChat"
folder? <br>
</p>
<p>What's the intended usage of the video/phone buttons at the top?
I also posted on <a moz-do-not-send="true"
href="https://support.delta.chat/t/webrtc-for-communicating/410/12">Delta
Chat's forum</a> about maybe using Jitsi as a video calling
server. That way it can work with anyone.<br>
</p>
<p>>></p>
<p style="margin-top: 0px; color: rgb(34, 34, 34); font-family:
Helvetica, Arial, sans-serif; font-size: 15px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">I was just trying Delta
Chat yesterday and wondering about a WebRTC video call button,
too. Right now, I can type something like<span> </span><a
href="https://meet.jit.si/WHATEVER" rel="nofollow noopener"
style="background: transparent; color: rgb(0, 136, 204);
text-decoration: none; cursor: pointer; overflow-wrap:
break-word;">https://meet.jit.si/WHATEVER<span> </span><span
class="badge badge-notification clicks" title="3 clicks"
style="display: inline-block; font-weight: normal;
white-space: nowrap; border-radius: 10px; padding: 0.21em
0.42em; min-width: 0.5em; color: rgb(145, 145, 145);
font-size: 0.7579em; line-height: 1; text-align: center;
background-color: rgb(233, 233, 233); top: -1px; position:
relative; border: none;">3</span></a>, send that, and everyone
on the email list will be able to join a WebRTC video call by
clicking that link as long as their browser supports WebRTC or
they proceed to install the Jitsi Meet app when prompted on iOS
and Android.<br>
Why not make a button that does that? A preference could allow the
user to enter any Jitsi server. Another preference could allow
supporting other types of WebRTC servers. The button could:</p>
<ol style="clear: both; color: rgb(34, 34, 34); font-family:
Helvetica, Arial, sans-serif; font-size: 15px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">
<li>Create a random Jitsi conference room link or allow the user
to type their own. (Maybe random by default to make it easier?)</li>
<li>Send the link to all recipients</li>
<li>Auto-deep-link into the Jitsi Meet app so you’ll join the
video conference room right away.</li>
</ol>
<p style="color: rgb(34, 34, 34); font-family: Helvetica, Arial,
sans-serif; font-size: 15px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width:
0px; background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">Is there any advantage
to integrating video calling within the Delta chat app versus deep
linking to a separate dedicated app like Jitsi Meet? I suppose it
would mean one less app to download, but having it separate means
you can switch video call providers more easily.</p>
<p><<<br>
</p>
<div class="moz-cite-prefix">On 5/20/2019 8:35 AM, Daniel Böhrs
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d16dcfce-829d-6e99-9591-127fe58c1377@open-xchange.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="UTF-8">
<div>
<div class="default-style"> Hello everybody, </div>
<div class="default-style"> <br>
</div>
<div class="default-style"> the OX-Talk team just released
another technical preview version. Version 0.6.0 is a feature
release for the Android platform. It's downloadable via our
GitHub repository. </div>
<div class="default-style"> <br>
</div>
<div class="default-style"> Download link + full release notes:
<a class="moz-txt-link-freetext"
href="https://github.com/open-xchange/ox-coi/releases/tag/0.6.0"
moz-do-not-send="true">https://github.com/open-xchange/ox-coi/releases/tag/0.6.0</a></div>
<div class="default-style"> Repository link: <a
href="https://github.com/open-xchange/ox-talk"
moz-do-not-send="true">https://github.com/open-xchange/ox-talk</a>
<br>
</div>
<strong><br>
</strong>
<p><strong>Important:<br>
This release will create a new app and doesn't update the
current installation, if one exists. This happens due to the
renaming of the app, which also affects the package name.
Android detects a different package name as a new app.</strong></p>
<p><strong>New features:</strong></p>
<ul>
<li>A message action menu was added in the chat view (one tap
for text messages, long press for attachments)</li>
<li>Forwarding (text and attachments) and copying (text
messages) is now possible via the new message action menu</li>
<li>Local notifications were added (If the app is active and a
new message is received in a chat which isn't visible a
notification is shown. Only active while the app is in
foreground)</li>
<li>A new settings menu was added</li>
<li>Importing and exporting existing security keys is now
possible</li>
<li>Verified contacts are now shown with the corresponding
icon</li>
<li>A logo was added</li>
</ul>
<p><strong>Adjustments:</strong></p>
<ul>
<li>Renamed the app to OX Coi</li>
</ul>
<p><strong>Fixes:</strong></p>
<ul>
<li>Fixed group invite problems</li>
</ul>
<div class="default-style"> <br>
</div>
<div class="io-ox-signature">
<div class="text-wrap tlid-copy-target">
<div class="result-shield-container tlid-copy-target"> <span
class="tlid-translation translation">Regards, </span> </div>
<div class="result-shield-container tlid-copy-target"> <span
class="tlid-translation translation">Daniel</span> </div>
</div>
</div>
</div>
<div class="io-ox-signature">
<p> <br>
</p>
<pre>--
kind regards,
Daniel Boehrs
Mobile Development
Phone: +49 2761 75252 00 Fax: +49 2761 75252 30
Email: <a class="moz-txt-link-abbreviated" href="mailto:daniel.boehrs@open-xchange.com" moz-do-not-send="true">daniel.boehrs@open-xchange.com</a>
Skype: boehrsii
-------------------------------------------------------------------------------------
Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court Nuremberg HRB 24738
Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Michael Knapstein, Stephan Martin
Chairman of the Board: Richard Seibt
European Office:
Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District Court Siegen, HRB 8718
Managing Director: Frank Hoberg
US Office:
Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA
-------------------------------------------------------------------------------------
</pre>
<p> <br>
</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@coi-dev.org">dev@coi-dev.org</a>
<a class="moz-txt-link-freetext" href="https://lists.open-xchange.com/mailman/listinfo/dev">https://lists.open-xchange.com/mailman/listinfo/dev</a>
</pre>
</blockquote>
</body>
</html>