Follow

does an amazing job of allowing two or more people to do or video chat without any centralized servers involved. But I'm having a lot of trouble getting it to sync my contacts and text messages between apps on different devices, even when I have them open and running at the same time for quite a while. It's also too easy to lose your account if users remove the apps from all their devices without making a backup, and that doesn't seem to be possible with the app.

If .chat (or a fork of it) added voice/ video chat using the protocols, allowing Jami accounts to be associated with email accounts, that might be the best of both worlds. A reliable, federated transport and storage for text messages, file attachments, and voice mails, and a fairly robust voice/ video chat experience (both one-to-one chat and group conference). Same if native apps like supported for voice/video chat.

In fact, the ultimate comms might be a native client that could speak , , and protocols. It would accept messages from either or email servers, and deliver them to either a chat UI or a long-form email, depending on message length (a sane default # of characters that users can change in settings). When XMPP presence protocols and/or Jami protocols told users contacts are online, they could make a voice/video call using Jami protocols.

If clients like this were developed for mobile GNU/Linux like , , , as well as for and , it could be a game changer. Although it would work better if creating a webmail account on a community-hosting service automatically created Jabber and Jami accounts associated with them. Which would require hosts to run an server and a Jami ID node.
jami.net/the-jami-blockchain-s

The UI of the mobile app is pretty good, but it could use work on the desktop client. Here's a side-by-side comparison with the desktop client, on the default desktop of GNU/Linux. The differences are subtle, and hard to fully appreciate without seeing them in use, but something about the Wire UI just feels more ... polished. If I could even had the option to change the colours in Jami to a darker palette, that would help I think.

... and here's the Jami screenshot. Note that despite the fact I'm pulling this directly from their repo, it's still using the old branding (Jami is still part of the GNU Project but they seem to be playing that down a bit in the visual branding since the rename).

@strypey
> /e/

Do you mean rebranded+outdated LineageOS+MicroG?

@succfemboi ? You mean rebranded Android that only works on a fraction of Android devices? Anyone can play the 'sneer at other people's projects' game. To what end? I'm talking about the , a project integrating hardware, OS, apps, and hosted services, designed to be respectful of users and their privacy and control over their computer, under a unified branding comprehensible to non-geeks. You're free to scoff but I see that as a worthwhile contribution.

@strypey Sorry for late response but LineageOS can’t be compared to Android 1:1. It’s a continuing fork of Cyanogenmod which develops their own apps and has an additional set of APIs, more privacy features support for optional root (things that won’t be upstreamed directly). Some people who worked on Cyanogen are also maintaining LineageOS.

However /e/ simply cashes in by forking many open source projects and don’t contribute their fixes to upstream, even though they are still active.

While it’s great that they are wanting to make it easier for users, it’s not really good to provide them surverely outdated software and presenting it as google-free while loading the OS with microg would be dishonest to say the least

@succfemboi OK, at least you're presenting your arguments now ;) There seem to be four:
1) they are bringing in revenue but not sharing it upstream
2) they are fixing code but not contributing upstream
3) the versions of software they distribute are outdated
4) the Goggle-free promotional claims are incompatible with including a free code implementation of the Prey Services component of Android.

Can you share your sources for each of these concerns?

@succfemboi I can't really comment on 2, 2 or 3 without seeing more information. I agree it *sounds* bad, but devil, details, yada, yada. On 1, a project that's only about a year old is most likely burning through far more cash than it's bringing in. I'd need to see strong evidence to the contrary before I believe they have any ability to send cash upstream and are choosing not to. Hopefully one day they will be profitable and will help fund upstream projects. (1/2)

@succfemboi As for 4, it looks to me like a petty nitpick. The pitch of the /e/OS project includes giving users an OS and remote services that are not controlled by Goggle. is not controlled by Goggle. It's a project that allows people to use the handful of otherwise free code apps, which make the mistake of depending on Prey Services. If you don't use any of those apps, and don't want MicroG on your device, /e/OS gives you root, so uninstall it. What's the big deal?

@strypey Please note that the desktop client (jami-gnome) is a #gtk app and tries to follow the global gtk theme (at least to some extent)

@strypey Also, Wire is an #electron app (basically an embedded website) so comparing them isn't very fair as electron apps trade good looks with resource consumption

@Naughtylus Electron is neither here nor there. Take and , both native apps. Transmission has an elegant UI, minimal info per element, intuitive to navigate, tweaked a bit for each platform it runs on, but consistent across them. qBitTorrent is a great BT client, but the UI is a screaming hot mess that looks like a 1990s era Windows app. Jami isn't nearly as bad as it could be, but there's plenty of room for improvement. The Android app is much better than on GNU/Linux.

@strypey
Im experiencing the same syncing problem. Id love to use #Jami but Id want it to sync between devices.

@whirli I'm wondering if the syncing problem is a bug. I've had better luck with syncing between Jami apps in the past.

@strypey @whirli There is no sync for text messages for now. But this feature is a mandatory step to group chats

@AmarOk but ... like I said, I'm sure I remember my text messages syncing before.
@whirli

@strypey But I confirm you that the feature never existed. The only thing existing is when multiple devices are present on the DHT, they both receive the messages @whirli

@AmarOk
> they both receive the messages

Ah, that must be what I'm remembering.

> But this feature is a mandatory step to group chats

Has the Jami group chat feature not shipped yet? It's already promoted on the website. I was looking forward to testing the group voice chat feature with the group this Sunday.
@whirli

@strypey
group chats (text messages) is different from voice conferences (which is available since a few years in Jami)
@whirli

Sign in to participate in the conversation
Mastodon - NZOSS

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!