Took me a couple of times to get through it. For the same reason. Well worth it in the end though.

Ah, misunderstood your post. I think regular Signal still supports local backup. Doubt they’ll remove it when they add this.

Switching to Molly won’t necessarily give you free cloud backups. Someone will still need to pay for the storage costs.

I’ve seen posts by the GrapheneOS team about recommendations against using both F-Droid and Aurora. F-Droid had a decent sized list of issues they raised. One of the key ones they raised against both was that it added an extra person to trust. You always need to trust the code of the developer of the app. No way to avoid that. With F-droid you need to trust that their build system/infrastructure is serving you the app as per the developers code. With Aurora you need to trust the Aurora devs are giving you the app unmodified from Google.

There were other criticisms on F-Droid that they sign almost all apps with their own key rather than the developers. They do offer to serve apps with the developer keys, but it’s difficult to setup and not many apps implement it. Google Play also does the same thing though, so I feel this risk isn’t that big. Generally they seem to recommend getting apps directly from developers rather than via a 3rd party. They offer Accrescent in the GrapheneOS app store which is designed for this, just pulls files from Github AFAIK.

All that said. I prefer to get all my apps from F-Droid (NeoStore technically) and Aurora for anything without a F-Droid repo.

Glad to see it as a Flatpak. Looks like it’s an ed version though. Shows as v5 for me, but direct download from their website is v7.

How are you checking the size? Some tools will split file size based on the number of hard links. So a 10GB file may show as 5GB in folder A and the other 5GB in folder B.

Also, if you’re using Docker. Its crucial that your downloads and media directories are listed as a single volume. If it’s two volumes, it’ll copy rather than hard link.

Yeah, in self hosting MollySocket and my own Ntfy server. I’m in the process of moving it all to my NAS so I don’t have to leave my computer on all the time.

I really wish Signal would support it natively.

I’m using Molly with UnifiedPush for notifications and it works quite well.

Another recommendation for Proton Mail. As others have said I’d recommend getting your own domain for email so you can always migrate providers without having to change your email address.

They do have e2e for emails. Any emails between Proton Mail users are always e2e encrypted, as are any emails others send you which they’ve encrypted with their own maio client. If someone sends you an email unecrypted (most email is), then Proton will encrypt it for you and put it in your inbox. They can’t read it after that, but there is some trust required that they don’t store/look at the unecrypted email before then.

The UnifiedPush server is intended to be a single source your phone can keep a persistent connection open to, rather than needing a connection per service/app (this is how Google’s Firebase notifications work too).

As Signal doesn’t support UnifiedPush, MollySocket keeps a permanent connection open to Signal’s servers to listen for new activity and forward them to your UnifiedPush server. This saves your phone keeping a permanent connection open to Signal’s servers and draining your mobile battery more.

I’m self hosting both too. MollySocket’s docs are pretty clear that it never gets an encryption key for your account, so it can’t read your messages. It only gets/forwards alerts that something happened on your account AFAIK. So I’m not sure what data it has that’s worth encrypting.

For Signal/Molly, it’s less that the notification is encrypted as I understand it. It’s more the notification content is just “Hey! Stuff happened” for Signal. The app then reaches out directly to the Signal servers to see what’s new. So the message content is never sent via the push notification service (UnifiedPush or Google’s service).

I’ve got a few old PCI cards around somewhere. I should pull one of them out and give them a try at this.

That would require a lot of data privacy concerns to be addressed. Even if it’s an explicit opt-in. The current method uses sample text which can’t include PII. Using user supplied text would almost guarantee they’d get names and other PII in their data set.

I also imagine it’s harder to train the model when you don’t know exactly what the user was trying to type. I.e. Was the swipe detection wrong, or did the user delete the word because they changed their mind on what to write?

The issue isn’t a big deal for the average user. The vulnerability required them to first get your username and password, physically steal your Yubikey, spend half a day using $10-15k worth of electronics equipment to repeatedly authenticate over and over, they then could potentially make a clone of the key.

She’ll independently recycle your matter into more coffee.

It’s a good game. Just don’t take the content warning at the start lightly. I’ve tried to finish it twice but haven’t been able to get more than a couple of hours in.

Probably don’t need to scrape it. Just query WikiData for it

https://wikidata.org

When I migrated emails last time, I setup my old email to automatically forward to the new email. Then on my new email, I setup an automatic label for any email that was addressed to the old address. Every week or two I’d review what was sent to it and either update the email address used or unsubscribe. Eventually it got to a level where I wasn’t getting much at the old email anymore and finally deleted it.