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.ml to
- •
- 1M
- •
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…
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.
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.
It depends on the distributor:
https://unifiedpush.org/users/distributors
And how much info they collect. I understand the ntfy requires is really bare minimum compared to what GCM/FCM asks and collects.
On mobile, it’s sort of a needed if you one doesn’t wand to use GCM/FCM which is really bad privacy wise, and particularly needed on peer to peer applications, because they tend to drain the battery…
Some other benefit is that for those who can, they can self-host ntfy, nextcloud with unified push provider, and so on…
On the list of apps supporting unifid push, I even see element (matrix), but I don’t identify any xmpp one:
Yeap, I noticed it being a unified push distributor, actually in its settings on can find the option to enable it.
OK, I won’t worry about battery usage then. But the argument about unified push notifications not being useful, but the GCM/FCM actually found useful is somehow hard to understand. But I understand what you’re saying about battery usage. Thanks a lot !
- @kixik@lemmy.ml to
- •
- 7M
- •
Being using mull for so long, even when it was not available on f-droid official repos, but only divestos f-droid repo.
The only thing really bothering on mull is a config one really must change, security.OCSP.require, the default to true prevents reaching several sites. But other than that mull shouldn’t get in your way, and one can change other config to one’s liking if in need.
That’s so sad. So perhaps it’s time to say goodbye to reddit frontends, :( I’d prefer to setup rss feeds, but even those are getting rate limited now a days.
Sadly, even with the movement to lemmy, several interesting technical subs are still strong on reddit. The thing with local feeds, is disk space, and self-host is something I can’t do at the moment. At any rate, with the last libreddit front end down, I can’t even easily get the subs I was locally subscribed to, :(
Oh well…
- @kixik@lemmy.ml to
- •
- 10M
- •
It depends on what you want. I encourage people to use Jami (distributed, so might be a thing, if not self-hosting your own service, since what is said decentralized in reality is a set of centralized services). If too hard, then XMPP + OMemo. And only then, Matrix (by design it gives up more meta data than XMPP).
1.- jami 2.- xmpp + omemo 3.- matrix 4.- signal
It’s hard no one cares. Where I live everyone uses whatsapp, and unfortunately what comes closer, and still without enough users base is signal on my list, and it’s the last. Jami is distributed, which makes it best in class, and there are good efforts trying to make it not to steal the whole battery, as opposed to briar. I which more people were interested on not using centralized stuff, not even what has been called lately decentralized, which means centralized but with several central points (only if everyone self hosts it would be decentralized, which is not the case). Currently I use Jami and signal, though I’ve tried all those, plus briar, plus tox, even telegram…
Perhaps @lapcatsoftware@mastodon.online could think of lemmy besides mastodon, hehe
it’s not just osm instead of gmaps for the FOSS version. It’s NOT using google push notificationss neither gapps at all. Using sockets instead of push notifications. It makes molly FOSS being more battery hungry, but at least it’s not using google stuff. Not sure if the dev would be willing to integrate suipport for unified push for the FOSS version, that’d be even better…
No issues in newpipe, though piped.mha.fi is not a valid URL on newpipe, still searching for the video m3att9ydcxc does it. No issues on freetube either, neither with invidio instances, like:
I do use apkgrabber, but I’ve always got it from:
https://github.com/hemker/apkgrabber/releases
And it supposed to allow “notification updates” when new versions come out, though it’s been on 1.7.0 for quite some time.
Does izzysoft makes sure not to include apks which are already included in the official f-droid repo? It includes many apks already… And I’d rather grab the ones on official f-droid, with some exceptions, like the newpipe repo, but it doesn’t include anything else but newpipe…
BTW, Today at least https://searx.sp-codes.de is working. It might be Google aggressively rate limited several instances, and for some time. And it relaxed those limits after some time.
Thanks !
- @kixik@lemmy.ml to
- •
- 1Y
- •
There’s as well !monero!monero@lemmy.ml which I guess halted in favor of !monero!monero@monero.town?
If this is the case, I’m wondering why not locking the community, writing a message in the community information to go to the actual active one (!monero!monero@monero.town)…