Syncany VS ios

This reminds me of my (now dead) open source Dropbox alternative Syncany [1] and all the different storage plugins I made for it [2]. Long story short, a storage plugin only had to implement the API methods upload, download, list and delete, so you could literally use anything as a storage backend (FTP, SFTP, S3, WebDAV, ..).

I made a few fun plugins that would encode data (after deduping, compressing and encrypting them) into PNG or BMP and store them on Flickr (which gave you 1TB of free storage for images) or Picasa (now Google Photos). It was actually relatively efficient and not slower than the other methods, and it looked super cool to have albums full of what looked like images of static. It was a blatant violation of their ToC, so obviously not serious.

The code is still online, it's from 2014/2015. The Flickr plugin with the PNG encoder is here [3], and I'm not entirely sure if I ever published the Picasa one.

[1] https://www.syncany.org/

[2] https://github.com/syncany?q=plugin

[3] https://github.com/syncany/syncany-plugin-flickr/tree/develo...

Although I don't need to dial a VPN before accessing my NAS outside, but expose NextCloud on public network is not safe. There are already some people request NextCloud add support for client-side certificate authentication on their app, I am also very interested in this feature, it will improve the security of public network access.

I recently setup my first unraid homelab and ended up going with a cloudflare tunnel + warp setup for accessing docker/VMs like Nextcloud remotely. Everything seems to be working well through the browser, but the nextcloud desktop and mobile apps give me "unknown" errors when I try to connect. I've seen a few other posts and issues submitted on github in regards to this (https://github.com/nextcloud/ios/issues/1565), but I haven't seen anyone mention a work around besides creating another connection workflow (ie. separate VPN). Any suggestions?

With multiple android phones come and go in the past 8 years or so, the background upload seems to stand its ground.

The real problem here is iOS and its lack of proper background tasks. See: https://github.com/nextcloud/ios/issues/215 -- they tried every possible way to persuade iOS into running background sync, but still hit and miss.

I have to request access to my wife's iPhone and manually trigger some :)

One small suggestion here -- PhotoPrism went with `tensorflow.js` to load up classification models, and I recommend a "real" TF or PyTorch installation to properly leverage the computation resources. The difference is huge even running cpu-only because it's wasm vs. proper BLAS library.

I worked on a nodejs binding for native ONNX runtime (not publicly) so that's also a possible way out.