Dino 0.3 is released and supports video calls and conferences! 🥳
You can call a friend or a group of people. Calls are e2e-encrypted, peer-to-peer and compatible with other XMPP applications.
Release blog post: https://dino.im/blog/2022/02/dino-0.3-release/
@dino@fosstodon.org sounds cool. maybe add screen sharing (it it isnt already implimented)
@dino thank you for interesting facts about peat bogs I was not expecting to learn.
@dino I love a release named after a vital peat bog ecosystem. :)
@dino I need somebody to test it with!
@dino what's the participant limit for video and voice calls?
@zpojqwfejwfhiunz @dino The actual limit depends on the systems and networks of all participants in the call. For now we artificially limited the number of p2p participants to 5, but this number may change once we gain further practical insights.
@dino I wish I could share this, but it has an undescribed image. Could you consider adding alt text to the image so I can share it?
@weirdwriter @dino
They did non answer so, here it is: Dino logo, "Dino 0.3 Release".
Dino logo is an incredibly round dinosaur on its side (think a circle with feet, tail and spines).
@caffeine @weirdwriter @dino The Dino logo is a Dinosaur in the shape of a speech bubble. A speech bubble with legs, spikes and a tail! 🙂
@fiaxh @weirdwriter @dino
Oh right I remember that I noticed that long ago, but somehow I just think of the dinosaur now! 😄
@dino
This sounds like good news! Will this release be added to Debian's bullseye-backports?
@TMakarios @dino Apparently yes! 😉
https://packages.debian.org/bullseye-backports/source/dino-im
@dino Does it avoid the inflation of key pairs when used on several devices?
@holgerjakobs @dino I don't quite understand, could you please clarify your question? Are you referring to having lots of OMEMO device keys?
@holgerjakobs @dino Having one key per device is they way OMEMO works, but I understand the issue.
However, the newly added call functionality does not affect the number of OMEMO keys at all. The existing OMEMO key of your client is merely additionally used to authenticate call keys.
@dino Félicitations 🎉
@dino Thank you Dino team! Your efforts have benefitted XMPP greatly, and even helped out people on Windows inadvertently through the efforts of Felipe on Github! All the best to you all and thanks again!
@Phaserune @dino Well I wouldn't call it inadvertently :D We aim to release official Windows builds in the future.
@dino LET'S F* GOOOOOOO!!!
@dino
Is It #mobile friendly, can I try this on #pinephone ?
@Blort @dino
It is not :( To use it my #pinephone needs landscape mode
@dino I tried it on my raspberypi4. With a C170 USB Webcam. ARM64. I compiled it from source. Audio/Video doesnt work.
@HoSnoopy @dino Can you please clarify what exactly "doesn't work"? Do you not get a call button or does the audio/video not work during a call? Have you installed all dependencies? (see https://github.com/dino/dino/wiki/Build) Please feel invited to join our XMPP channel at chat@dino.im . You probably get quicker debugging help there.
@HoSnoopy
The Dino chatroom may be a better place for debugging the building. Often its about some missing dependencys for A/V
xmpp:chat@dino.im?join
@dino
@dino From looking at the code, it seems you use the Call Invites XEP (https://xmpp.org/extensions/inbox/call-invites.html). This may be of interest to other people 😉
Thanks for this great software !
@nels @dino The features of "Call Invites" will be merged into "Jingle Message Initiation" (XEP-0353), see https://github.com/xsf/xeps/pull/1155
@dino@fosstodon.org that's it I'm gonna use xmpp
@dino oooooooo
@dino *refreshes package manager multiple times to see if the update has reached the repos yet*
@dino Thank you soooo much! And kudos for the hard work.
@dino
Do you know how to install #dino 0.3 on #linuxmint? I am stuck at 0.1. Thanks.
@dino alright 😊👍 congrats and thank you 🎉