As others suggested you don’t need all your historic mail on your mailserver. My approach to email archival is the same as all my historic data — a disorganized dumping ground that’s like my personal data lake, and separate service(s) to crawl, index, and search it (e.g. https://www.recoll.org/)

What is the issue with the external dependency? I would argue that consumer routers have near universal shit security, networking is too complex for the average user, and there’s a greater risk opening up ports and provisioning your own VPN server (on consumer software/hardware). The port forwarding and DDNS are essentially “external dependencies”.

Mesh VPN clients are all open source. I believe Tailscale are currently implementing a feature where new devices can’t connect to your mesh without pre-approval from your own authorized devices, even if they pass external authentication and 2FA (removing the dependency on tailscale servers in granting authorization, post-authentication).

I believe this is what some compression algorithms do if you were to compress the similar photos into a single archive. It sounds like that’s what you want (e.g. archive each day), for immich to cache the thumbnails, and only decompress them if you view the full resolution. Maybe test some algorithms like zstd against a group of similar photos vs individually?

FYI file system deduplication works based on file content hash. Only exact 1:1 binary content duplicates share the same hash.

Also, modern image and video encoding algorithms are already the most heavily optimized that computer scientists can currently achieve with consumer hardware, which is why compressing a jpg or mp4 offers negligible savings, and sometimes even increases the file size.

Your data is securely preserved on your Google Drive / Dropbox account, ensuring complete ownership and privacy

Lol

For iOS there’s location log. You can export your history too.

Also, don’t kid yourself. If you aren’t using Graphene and have any tech company app installed on your phone they’re logging your location, and sharing it with everyone who pays, even if you opt out.

Rather ironically, miniflux users could add miniflux releases to their miniflux feed using https://github.com/miniflux/v2/releases.atom

So it’s extra extra useless

Consumer routers fall apart when you want to do many common networking tasks, like setting up a VLAN on a separate subnet with pinhole access, so when faced with having to buy a significantly more expensive SMB router vs the cheap FOSS solutions others have mentioned, you’re better off just going the FOSS route.

Note: some consumer routers can be flashed with FOSS firmware, but be prepared to waste days tinkering and testing.

All you need is to use ZFS or BTRFS locally to prevent master version bitrot and provide failover/redundancy, manually sync that to a separate “offline” HDD periodically, then setup a simple pi with tailscale + HDD at a family member or friends house, and rclone all your data to it (encrypted) as a cron job every night or week. This performs the function of a cloud provider (offsite backup); alternately, just manually sync the offline HDD once a month.

With this approach you’re covered for accidental deletion, hard drive failures, bitrot, ransomware, and fire; possibly many natural disasters, depending how far away the offsite is.

Then you can just keep your most important data E2E encrypted in 1 or 2 cloud storage providers.

So, I’m guessing all it’ll take to keep Yuzu and Citra alive on future installs of EmuDeck, is any existing user creating a torrent of those dependencies from their own steamdeck? Not much more than a drag, drop, and chown for other users?

https://en.m.wikipedia.org/wiki/Power_over_Ethernet

Looks aight but I consider it overkill for my needs. I have my own system which is just creating a note titled ‘YY-MM-DD Desc/Model’ when I purchase something and adding compressed images & scans of the label/serial, sometimes packaging, user guide, etc.

I then just print a dymo label for the product, components, cables, and spare parts using the note title so I can search the date and pull it up if I need. Makes dealing with a mountain of cables and power adapters much easier. I never pull something out of storage and go “what the fuck is this” anymore.

Testing and tagging USB-C cables is especially helpful, too. They usually have no indication of what speed or power they can handle.

What’s the upload speed from a regular sftp client to the same destination?

Ditto for audio in general. I notice wild differences between encodings in dialogue clarity and volume. If this were standard we could all mix and match whatever audio is best for our equipment.

You need to specifically set it up to work offline. It’s not out of the box. Either the setup guide you followed included that step, or you went out of your way to enable it, and forgot about it. It’s been that way for 5+ years, at the very least.

https://archivebox.io/ would likely be best, but I use singlefile or screenshots for important copies.

Your commenting here is evidence to the contrary

Then the dev needs to build out a range of protocols and API’s to enable users to “supply their own server”, which can bring a range of additional headaches, like having to provide support for external dependencies outside their control, etc.

What if the users “server” fails? Should the dev waste hours of their life assisting a user with a highly specific Google Drive issue when they spent $5, 3 years ago?

Bluray would likely provide the greatest cost-benefit as of today. If stored correctly they should last for decades.

Otherwise, if money is of no concern, cloud service providers. Data is replicated across multiple drives and their filesystems have bitrot protection. Unless you stop paying, it’s likely your data would remain intact and accessible for just as long as a bluray. If it’s good enough for critical government and corporate data, it’s good enough for your data.

First take the dinglebop, then smooth it out with a bunch of shleem. The shleem is then repurposed for later batches. Take the dinglebop and push it through the grumbo. Where the fleeb is then rubbed against it. Its important that the fleeb is rubbed, because the fleeb has all the fleeb juice. Cut the fleeb. There are several hizzards in the way. The blamfs run against the trumbles and the ploobis and grumbo are shaved away. That leaves you with a regular old plumbus.