kixik

I second xmpp + omemo, and would caution that as far as I can remember matrix leaks significant metadata when syncing between instances/services.

As a personal decision I got away from signal (molly in fact) more than a year ago.

I'm also keep jami working with my family, particularly for things not requiring immediate response. It's a different beast, since it's p2p, but there's no server associated to it, no matter if decentralized or not. It's easy as well, just not as responsive, in particular if looking for immediate responses... I like and keep both, hoping jami improves.

Ohh, I understand now what you're saying. LOS (upstream) finally allowed uG to work on their images, though not pre-installed with them, it's mentioned on LOS4uG FAQ, see question Why do we need a custom build of LineageOS to have microG? Can't I install microG on the official LineageOS?, the answer includes a couple of references to LOS MRs. I was not aware of that, and that makes all derived ROMs inherit such ability from upstream LOS, including divestOS, so now I see what you were talking about. The answer in that FAQ doesn't indicate that the official F-Droid client can be installed, and even better neither it or it's lighter official client (that one never supported privileged extension) require privileged extensions to install apps in the background, so no need to install such extension through adb, and once installed the F-Droid client, one can add the microG repo to keep the uG apps up to date. Therefore no need for LOS4uG actually.

The sad thing is that divestOS images/ROMs are no more, since divestOS is dead. I hope LOS ports divestOS' boot locking/unlocking mechanism from the still available divestOS repos, that would make LOS even better.

The other sad thing is that as LOS4uG signs with its own keys, different than the LOS ones, once you start with such images, unless you can backup everything, apps, apps settings and contents, LOS settings, and so on, without a google account, you'll have to keep using it, until you change phone, or you are OK with a factory reset and having to set everything again, since moving to LOS implies different signatures and keys, which in turn implies factory reset and further cleanup to make the image work, :( That holds true if wanting to move to divestOS images as well.

Sorry I didn't understand what you were saying. I've been using LOS before it was named like that (cyanogen), and as far as I can remember when uG showed up, LOS decided it didn't want to support it, and it was until early last year that it decided to finally allow it, though not helping a bit providing it pre-installed, which is fine, because then the user can get to it, or rather Gapps. So I never read back about LOS criteria changing...

What do you suggest? If they get forced to use something encrypted, they won't choose XMPP for sure, most probably something like whatsapp or telegram.

Being forced to use non standard protocols, and specially non federated ones is also a concern. Where I live, it's assumed that all clients/users must use whatsapp, so they don't answer your questions, you can't ask them anything, you can't share any doc with them if in need for support, it it's not through whatsapp. And everyone seems happy with it.

e2ee by itself is not enough for privacy, metadata counts, and on proprietary communication systems one doesn't even have a clue what data is mined by the company/owners or even worse if they have non disclosed mechanisms to do that or even worse to introduce back doors.

If I'd suggest something, that would be a standard and federated protocol with e2ee like xmpp + omemo. But again, I'd be naive to assume that's a possibility, if forced to do something corporations will choose what's more convenient to them not to the user, and that usually translates into proprietary abusive mechanisms.

Now about nerds using gnuPG/openPGP keys, ohh well, thunderbird chose what to me is the wrong path of not using gnuPG underneath (now by default all keys are exposed unencrypted, unless you choose to use TB's master password for example, between several other limitations, the good thing is that there's sequoia-octopus-librnp to the rescue), but that path allows them to offer a really easy way for users to interact with openPGP keys. On Android K9, now a days Thunderbird, has made it really easy as well to use gnuPG/openPGP keys when accompanied with openkeychain for example. There's nothing obscure neither truly complex about current gnuPG/openPGP usage these days. I would agree like 15 years back one really needed to learn how to maintain the gnuPG keyring, how to add and manage public keys and how to manage your own private keys. But even then there was Enigmail, which after TB chose that path turned into just a shell to help move from Enigmail to the chosen TB's librnp way, and Enigmail made it really easy to do all that gnuPG stuff. Besides thunderbird, which I wouldn't say is a nerdy thing, there were/are several other easy alternatives to use and handle gnuPG/openPGP keys. So, not really nerdy, I'd think just willing to go a bit beyond what the corporations offer you, for "your own convenience". But how many people even care? I'd say we're a sleepy society, accepting everything imposed to us, even when there's no need to, because of the hassle to look for truly privacy respectful, security respectful (from the user perspective, not just the corporations perspective), and also really important user liberties/freedom respectful, which Today's corporations with the help of some communities and the banning culture we all embraced, have been successful in convincing us that's unnecessary in favor of more "practical" alternatives, including proprietary ones...

Well, I think you already mentioned the key thing about encrypting disks. It's not about protections when the block device is already decrypted and the filesystem already mount. At that point your disks are decrypted and anyone with or without physical access to your device, if gaining any access to it you're toast. That's true, but that's not what disks encryption help you with, and you already mentioned. If you turn off your device, and someone steals it, or gains access to it, they can't look at your contents, that's it. That wouldn't prevent malicious people, to instead plant something through UEFI for example, and you are right about that case. And if you never turn off your computer, and just do sleep to memory, then you depend on how strong your password is, or any other authentication mechanism you have...

Can you explain why if someone get access to your encrypted disk, they would have access to its contents?

Phoenix is not a browser, is it? AFAIK it's a similar user.js to Arkenfox... They claim to be better, and have their on comparison, but I don't know:

https://codeberg.org/celenity/Phoenix/wiki/Comparison

Arkenfox has been like the default user.js for privacy... Perhaps phoenix already is better...

Maybe @[email protected] or @[email protected]. BTW I remember about [email protected] but I think it didn't survive, and on lemmy instances this is the only Librewolf community.

Well it's a bit confusing. On Guix' wiki General features you can read:

Guix keeps track of these references automatically so that installed packages can be garbage collected when no other package depends on them - at the cost of greater storage requirements, all upgrades in Guix are guaranteed to be both atomic and can be rolled back.

The roll-back feature of Guix is inherited from the design of Nix and is rarely found in other operating systems, since it requires an unorthodox approach to how the system should function (see MicroOS).

And then on its wiki Guix System (operating system) Roll-back you can read:

This is accomplished by a combination of Guix's functional package manager, which treats each package and system configuration as an immutable and reproducible entity,[58] and the generation system which maintains a history of system configurations as "generations."

So the system configurations on a Guix system are actually immutable, as opposed to regular gnu+linux distributions, which can change the system configuration on the fly. What else is immutable on Guix, I can't tell, but at least you can not change its system configs. What is atomic is the upgrades.

I'm not sure, but as Guix borrowed these properties from Nix, I'd think this applies to Nix as well.

In other words, at least the Guix system has immutable components. And further, the system config which is immutable, is also declarative. Combining those two things might be intimidating, since it's not like on the fly one can go and change the system config, which might be required when debugging some misbehavior, and it's what most distros document, then one needs to learn about guile, and a bit about functional programming I guess or at least their basics... Deploying systems might take advantage of such declarative configurations though...

It's been a while since extensions need to be signed for FF to enable them. Not sure if Librewolf build scripts do something about it, but the config is not configured by default:

% grep xpinstall.signatures.required /usr/lib/librewolf/librewolf.cfg
%

and if you look for it on about:config, it's enabled. So far it's functionality is mainly to sort of not allowing dangerous extensions, though that promise can't really be fulfilled, and besides, and it's true the feature can be abused, but it's not something new for FF, not sure why that petition is showing up just now, hmm. For the apps I use, this hadn't posed a problem on Librewolf so far.

But it's been a while I don't see Librewolf devs around this community and the other lemmy one I know [email protected] seems abandoned. Perhaps someone is familiar with Librewolf build scripts...

Regarding omemo, dino is getting there, see its closed issue 1609. Not sure why it has taken them too long for a new release, but they have the stuff already merged.

Ups, I just got to enjoy piped and in particular pipeline on gnu+linux and libretube on AOSP.

Pipeline in particular allows to totally avoid electron (freetube), and in both cases the piped instance is the one communicating with youtube, not me, :) And both applications support sponsorblock (tubular does, but newpipe doesn't). But not talking directly to youtube is a win. Did I mention dropping another electron app, :) ?

But... I installed pipeline from AUR, because I don't like flatpak... Not sure if other user repos offer it as well...

I'm interested on what changed that make it differ from Mull in a non recommended way. Are you referring to their 1st MR? where they outline:

• Replaced Arkenfox & Brace preferences with ones from Phoenix 2025.01.06.1...
• Added support for Google Safe Browsing (Safe Browsing is disabled by default and can be enabled by setting the following preferences to true in about:config)

I understand Mull was using arkenfox which is sort of the go-to reference, and now ironfox move to phoenix. The safe browsing is the same approach Librewolf follows, though I don't like their comment on a proxy. I don't like their choice of the brave search engine, but I always replace that with searxng tweaked a bit.

The MR doc doesn't look too terrible, but don't know about the changes themselves.