• 13 Posts
  • 38 Comments
Joined 3 years ago
cake
Cake day: November 3rd, 2021

help-circle


  • The issue with social networks is the account requirement. Even though decentralized, they still require servers with accounts. If you, to prevent not being able to access at some point included an email, and the server gets hacked, then there you go.

    Perhaps is a mistake of mine, to think social networks are not anonymous enough. Maybe they are. But tracking mechanisms are so sophisticated now a days, than the need for an account make me think they won’t ever be. That’s why I excluded social networks. Perhaps it’s the only option as of Today though.







  • kixik@lemmy.mltoPrivacy@lemmy.mlTox.chat security
    link
    fedilink
    arrow-up
    3
    ·
    4 months ago

    I has improved quite a bit. The phone app still requires navigating over its settings to get less battery consumption, and having ntfy or any other unifiedPush notification provider available in the phone. But with the default configs, you get Jami working at least. I tried it before, and I found before synchronization between devices was a mess. Currently it just works. I still find it hard on immediate/urgent calls or messages, which might not happen when you expect, but other than that it’s working.

    On the desktop, the default configs are pretty sane.

    And the best part, it’s being actively developed. And the UI is undergoing through lots of improvements. So if usability is your concern, it’s getting better, and each release improves over the prior one…



  • kixik@lemmy.mltoPrivacy@lemmy.mlTox.chat security
    link
    fedilink
    arrow-up
    12
    ·
    4 months ago

    Have you read it’s github front page?

    This is an experimental cryptographic network library. It has not been formally audited by an independent third party that specializes in cryptography or cryptanalysis. Use this library at your own risk.

    BTW, if you look at its issues (including closed ones, which most probably aren’t really closed) you’ll find pretty interesting discussions about its crypto not being right. That said, I’m not sure what irungentoo brings to the picture…

    At any rate, if you’re looking for distributed messaging, I’d look into Jami. It also uses DHT and something similar to torrents mechanism. Jami is my only option so far for distributed messaging. There’s also Briar, but I don’t like it for regular messaging, particularly on phones (too much battery usage), neither its underlying technology, but if it’s to your liking, then that’s another option for distributing messaging.







  • I would recommend using apkupdater for closed source apks, in particular enabling apkpure repo, rather than insisting on using google repo with aurora store or any other mechanism.

    Also looking for FLOSS alternatives if possile (granted things like whatsapp and waze won’t have alternatives for example).

    Some metioned apkmirror as the more trusted repo for closed source apps, however it’s currently formatting apks on multiple apks, and supposedly requesting for the apkmirror own instaler, so I recommend apkpure instead, which is also pretty well regarded, and they also in theory offer the same packages as the ones on google play…

    For FLOSS apps, the different f-droid repos (official ones and non official ones such as izzy-on-droid) offer a good amount of them.




  • The phone doesn’t poll, instead it goes to sleep, and gets awakened by the push notifications. Just like GCM/FCM ones. Part of the key thing, because not any one can self host, is that it requires very little information in comparison, and some providers are open source and even free SW. The one I use is ntfy, there’s the next cloud (next push), and not long ago you can use the conversation push service (up.conversation.im) through the Convesations xmpp client. I was aware of Conversations capable of becoming a unified push distributor, but actually was looking for it to use a unified push distributor instead.

    But I was informed already it’s not necessary, and doesn’t make much sense, by being very low power consumer, even though it requires to keep unrestricted battery consumption on the background. So no issues by Conversations not supporting using a unified push notifications distributor.