iOS-SortingAlgorithmsApp VS ios

Sorting Algorithms App - An open source app focused on show in a visual way how sorting algorithms actually works.

Journelly uses standard iOS file access and relies on iCloud (or third parties) to handle syncing via related infrastructure.

Theoretially, any third party app that is a file provider https://developer.apple.com/documentation/fileprovider should be able available to Journelly.

The reality is that reliability and provider completeness by third parties varies drastially. For example, many of them don't offer directory access to other apps (Nextcloud as an example https://github.com/nextcloud/ios/issues/3283#issuecomment-27...), which is a show-stopper for Journelly. It needs a directory to save images.

Here's a thread with some third party options some folks are using with Journelly https://framapiaf.org/@marczz/114369575100101184

Working Copy, SyncTrain, and Möbius Sync are amongst the ones I've heard working from users. For v1, I'm officially supporting iCloud (but still leaving it open for folks to try other providers). I'm just not able to do what's necessary to implement or fix what's needed in those providers (their app/codebase).

> Can you expand on this further? Wouldn’t this just be exposing myself to the same vulnerabilities as OP?

Yeah I wouldn't do this personally, I just mentioned it as the simplest option.

> If I use nginx as a reverse proxy, would I be mitigating the risk?

If the reverse proxy performs additional authentication before allowing traffic to pass onto the service it's protecting, then yes, it would.

One of my more elegant solutions has been to forward a port to nginx and configure it to require TLS client certificate verification. I generated and installed a certificate on each of my devices. It's seamless for me in day to day usage, but any uninvited visitors would be denied entry with a message saying that they didn't provide a valid certificate.

However support for client certificates is spotty outside of browsers, across platforms, which is unfortunate. For example HomeAssistant on Android supports it [1] (after years of pleading), but the iOS version doesn't. [2] NextCloud for iOS however supports it [3].

In summary, I think any kind of authentication added at the proxy would be great for both usability and security, but it has very spotty support.

> Based on other advice, it seems like the self hosted VPN (wireguard) is the safest option, but slower.

I think so. It shouldn't be slow per se, but it's probably going to affect battery life somewhat and it's annoying to find it disconnected when you try to access Immich or other services.

[1] https://github.com/home-assistant/android/pull/2526

[2] https://community.home-assistant.io/t/secure-communication-c...

[3] https://github.com/nextcloud/ios/pull/2908

In my opinion it’s not a good alternative if you or your team members expect exactly the same quality of service. When you switch to Nextcloud you’ll have to expect more bugs, less reliability, less performance and obviously more maintenance (since it's typically self-hosted) compared to Google Drive, Dropbox or One Drive. So you'll have to go into this with a different kind of mindset. What you gain is independence and extendability due to a rather big platform ecosystem.

E.g. here are some specific things and examples of things you'll have to deal with, in no specific order. These are just some things I've had to deal with recently.

- You'll have to educate people in your group that there are at least 3 different ways to share files among each other and that they can all coexist in parallel (Individual Shares vs. Group Shares vs. Group folders vs. Circles/Teams) (I did a german blog post on this: https://bitbetter.de/blog/nextcloud-freigabe-chaos/)

- Handling of file/folder names with special characters is a mess e.g. if you have Windows and Linux clients there will most certainly be conflicts. (Luckily this has been fixed recently by the `forbidden_filename_characters` config option – which is not enforced yet via the Web UI) see https://github.com/nextcloud/ios/issues/2802

- Creating Nextcloud users with spaces in their names, will break CalDAV on iOS Devices (https://github.com/nextcloud/server/issues/15641)

- Nextcloud (aka Collabora) Office is very slow if you want to actually work collaboratively with it (no matter the power of your Collabora server) – unfortunately it's no match for Google Docs or Office 365

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.