Probably folder structure and naming conventions.
If you still have some stubborn pieces of media, [imdbid-tt…] tags and even .nfo files can help.
Probably folder structure and naming conventions.
If you still have some stubborn pieces of media, [imdbid-tt…] tags and even .nfo files can help.


A bit cumbersome if you are traveling and using a different public wifi every time though
You’re not wrong. But you’re probably also familiar with the “secure vs. convenient” dichotomy: the closer to the “secure” end of the spectrum you get, the more cumbersome things will inevitably get. If you feel like you’re jumping through too many hoops and you don’t know what for, chances are you’re overshooting the target in terms of your threat model and might get away with doing less.
Plex -> Jellyfin (I don’t use it but I’ve heard good things about it);
I do use it heavily and came here to recommend it over Plex.




Most lists from https://github.com/blocklistproject/Lists


I feel you. Handoff was dodgy af. I’ve switched to BasicSync for this very reason. It’s a minimal Frontend, handling only execution conditions on Android. All config is done through the webUI. It works great and avoids some, if not all of the trust issues.


Immich is dead-easy to set up on its own. I’m a great fan and have been running it for >2 years now.
That said, I don’t think it’ll work for you because:
Obviously, I’m making a lot of assumptions about you. Whether these are true is up for you to decide.


Thanks for providing some evidence at last. You’re not wrong on many of those points, but not entirely right either.
Phone numbers are an issue, true, though you can get around that using a burner SIM or even a virtual phone number. Also, contact discovery has been working without exposing your phone number for over a year now.
a phone from Google or Apple
The phone can be made by anyone. The OS needs to be Android or iOS at some point, which is unfortunate; pure (desktop) Linux usage isn’t possible. That said, deGoogled Android has been around for more than a decade, allowing you to use Android in a privacy-friendly way. So if you want, you absolutely can avoid being tied to Google and use Signal.
As you can see, there’s a lot more nuance here than “Signal isn’t private”; privacy, after all, isn’t binary, but rather a gradient. For what it’s worth, Signal is more private than many messengers out there by a long shot, and it allows you to use it in more privacy-friendly ways if you so desire. While there are messengers out there that go even further in terms of security, privacy and decentralisation, a lot of them come with usability and convenience drawbacks. The way I see it, Signal sits in a Goldilocks Zone of “private enough” (for most threat models) and “convenient enough” for mainstream adoption. You can have the most secure and air-tight messenger; if there’s nobody there to talk to, it’s no more than a technically sophisticated brick. For now, Signal may be our best shot for mainstream adoption of reasonably private and secure messaging. If your threat model is higher than that of average Joe, by all means, go for Briar, SimpleX chat or any of the more hardcore options.




Ignore the downvotes. That’s a fair question to ask, but one that does have answers. Signal is FOSS, has E2EE and was audited several times, so we know that
Thus, while mistakes do happen and can open up severe vulnerabilities, cf. Heartbleed, there’s reason to assume that Signal is relatively secure. Signal’s centralisation of server infrastructure is a valid concern, but not for security, but rather for


Fair, that’s why I want to avoid it as much as I can.


Follow-up: I added the Guardian project repo to FDroid. Turn out: once FDroid has the repo, it can “take over” and do updates, even if Signal was originally installed from the Play Store / Aurora. That pretty much solved my primary issue here. (I’ll look into Molly at a later point anyway, just for the sake of curiosity.)
Thank you, once again!


Now that’s a smart solution that might just work for me. I completely forgot that they were packaging Signal for their repos too! For anyone interested: Here’s the link to their repo.


I’ll reply to you since you first brought it up, but it’s a question to anyone here recommending Molly: what makes you cofident that Molly is secure (i.e. they’re not fucking up Signal’s cryptography by accident) and maintained by trustworthy people. Signal does get audits from time to time, Molly doesn’t.
Mind you, I’m not trying to shit all over Molly; Unified Push looks great. I’m trying to approach this with due caution though.
There are no issues with DKB on degoogled Android.
Commerzbank have recently started claiming non-Google phones were “rooted” (which is bullshit) and refuse app-to-app pushTAN communication. One must work around that using a (PC-based) browser and photoTAN. Motherfuckers.


Aurora is all I use. We’re still trusting Google not to inject anything malicious into the app, which they’ll do in a heartbeat if the feds come knocking.
I’ve been a great fan of the project and used it as my daily driver for >5 years. It was stable as heck and the devs were super responsive, even adding in neat features at users’ request.
That said, I’ve lost trust in the project and moved on to GrapheneOS. The departures of Chirayu Desai and Nick Merrill smell weird from miles away. The latter left without any words of farewell explaining why he’d abandon his own project from one day to the other. I won’t engage in speculation as to what happened behind the scenes, but there are enough red flags here to keep my distance.
Man, your basement has the weirdest carpet I’ve ever seen. Also, much too bright for my taste. If you can see the keycaps without backlight, you’re doing the lighting wrong.


Corporate-driven > community-driven distros
This isn’t entirely true. Linux is getting a lot of help from Microsoft. <wink wink>