larma

7 ms·

1.
CalyxOS Temporarily Stops Updates(calyxos.org)
5 points by larma 1y ago|0 comments
2.
Dino 0.5: Polishing user experience(dino.im)
13 points by larma 1y ago|2 comments
3.
by larma 4y ago
Yes, the whole app will be Linux Mobile ready soonish, but priority was to have the main screen first and get everything ready in-time for Debian stable inclusion
4.
Dino 0.4 – Message Reactions, Replies and GTK4(dino.im)
89 points by larma 4y ago|24 comments
5.
by larma 4y ago
I wouldn't call it a fundamental difference. If I was to concatenate the 3 XMPP RFCs and the suggested XEPs from the compliance suite linked, I would end up with a monolithic spec. Every now and then, when a new compliance suite is pub
6.
by larma 4y ago
> nobody can tell me that bugs don't happen They do happen. And whenever someone does make use of them, that's considered unlawful - which is absurd considering that the bug is part of the code and thus part of the law.
7.
by larma 4y ago
Most of so called circulating supply is not circulating. 25% are in addresses that have been dormant for more than 5 years. Several percent are locked in "DeFi" or long term contracts. When Bitcoiners say "circulating supply&
8.
by larma 4y ago
The complexity of a whole protocol and running a client for it (which is effectively what you are doing when running bridges locally) is much higher than just doing the necessary part (e2ee) on the client. Also, you might be unable to run s
9.
by larma 4y ago
I think implementing just the e2ee part of the WhatsApp protocol (which happens to be the Signal protocol with open-source libraries available) client-side and have a server-side bridge transport the encrypted messages over to WhatsApp and
10.
by larma 5y ago
Check out https://github.com/dino/dino/issues/1193
11.
by larma 5y ago
> server typically has done termination of the encrypted call streams as it does its routing. Dino already supports some kind of "double encryption", where even if DTLS-SRTP is terminated at a media routig or bridging server, t
12.
by larma 5y ago
Vala is a nice, modern niche language for GTK development. It certainly can also be used for other things, e.g. it can be compiled to WASM, but GTK development really is focus. Also the language is actively developed and getting updates wit
13.
by larma 5y ago
While Dino and all of its dependencies can be compiled and run on Windows and macOS, this process is tedious and GTK isn't really well-tested on anything but Linux, resulting in worse UX when not going the extra mile of doing targeted
14.
by larma 5y ago
It does work, but UX isn't as good and installation is a little tricky. Check out the wiki page here: https://github.com/dino/dino/wiki/macOS
15.
by larma 5y ago
Friends and family all use XMPP via Conversations and/or Dino. I also join a few channels of FOSS projects on Matrix or IRC with a bridge. You can even bridge calls to SIP and PSTN via https://jmp.chat/ . I run my own s
16.
Dino 0.3: Video calls and conferences – encrypted and peer-to-peer(dino.im)
186 points by larma 5y ago|74 comments
17.
MicroG 0.2.23 reintroduces support for SafetyNet(github.com)
4 points by larma 5y ago|0 comments
18.
by larma 5y ago
In XMPP, encrypted messages can either contain encrypted XML > <message type="chat"><body>Hi there!</body></message> or raw text > Hi there! In Matrix, it's always encrypted JSON > {
19.
by larma 5y ago
HTTP would be fine as well, you could GET an XML with the form to fill and POST the XML with form data. But: - HTTP forms might be less flexible when it is about structured data. - HTML needs a complex renderer software Remember that this
20.
by larma 5y ago
Which modern serialized protocol do you envision here? That comes with good extensibility by design? Just the fact that XML is old, doesn't mean it's bad. It might be a bit unnecessary verbose or hard to parse for constrained devi
21.
Dino 0.2 Release: Mexican Caribbean Coral Reefs(dino.im)
15 points by larma 6y ago|2 comments
22.
by larma 6y ago
microG GmsCore is a FLOSS (Free/Libre Open Source Software) framework to allow applications designed for Google Play Services to run on systems, where Play Services is not available.
23.
MicroG 0.2.12 released, adds support for Covid-19 contact tracing apps(github.com)
9 points by larma 6y ago|1 comments
24.
by larma 6y ago
Dino is native, which means it is more likely to get proper support of hardware accelerated video encoding/decoding, best case leading to less energy consumption during video calls. My Laptop's fan always runs full speed when bein
25.
Dino: Setting Out for Calls and Conferences(dino.im)
2 points by larma 6y ago|0 comments
26.
MicroG Creates FOSS Implementation of Exposure Notifications API(mastodon.social)
1 points by larma 6y ago|0 comments
27.
by larma 7y ago
We fixed some issues with OMEMO in the last months, so if your experience is a little bit older, those might be fixed already. If not, please report. Dino has a very limited plugin system, extending it is planned for future releases. We are
28.
by larma 7y ago
Last time I checked, Pidgin lacked proper support for multi device by not supporting Message Carbons (XEP-0280, required to receive messages on multiple devices when both are online at the same time) and Message Archive Management (XEP-0313
29.
by larma 7y ago
No. OTR was not considered due to its lack of multi device support. OTRv4 now supports multi device, so it could be an additional option once it becomes standardized for XMPP. We are also monitoring development around MLS.
30.
by larma 7y ago
We are aiming for support for the Librem 5 and other smartphones that use a more GNU/Linux-ish environment. For Android there is conversations.im with a similar feature set.

More ›