Here is a script to easily install WireGuard and generate client config files for any server: https://github.com/Nyr/wireguard-install

Sure, I get that. The issue is that as soon as you introduce the ability to install apps from outside the App Store, it becomes possible to trick unsuspecting users into clicking buttons they don’t understand. By designing a web page to look like an actual Apple page, a malicious party could convince users to “opt in” to outside sources, in a similar way in which phishing websites harvest users’ online banking credentials. Currently, this kind of attack is entirely impossible on iPhone.

I think that’s exactly the problem. The real user benefit will be very small, but in order to enable those changes, functionality will be implemented on everyone’s phones to support sideloading. In my eyes, this increseas the attack surface against iPhones. Time and time again alt stores have been used to distribute fake apps and malware on Android, and the victims are often those users who haven’t asked for sideloading and are unlikely to use it intentionally.

Yes, maybe this will enable an F-droid equivalent on iPhone and it will be great to have direct access to open-source apps. But is this niche addition worth potentially reducing the security of all iPhones? I’m not convinced.

What were the limitations of borg that you ran into?

Here are some alternatives you can try.

Do navigation gestures still work if you use a third party launcher? There was a time when it broke the animations and the gestures became clunky.

I used Standard Notes selfosted for a while, but, like many others, I’ve given up due to frequent issues. I’ve been trying Notesnook since and it more than does the job for me. A selfosted version should also be coming soon.

I did read it and, just like your reply, it doesn’t answer my question.

What I’m asking about is a special case that is not directly addressed in the article. If the carrier supports eSIMs, i.e. you can buy one from them directly instead of a physical SIM, then maybe this transfer tool will work, with the disclaimer that it may not work in some cases. But if the carrier only offers physical SIMs, there is no information whether this new Pixel feature will let you create a usable eSIM.

I’ve had bad experience with FocalBoard. Several times it lost data for no apparent reason, including during updates. Eventually I decided to stop using it because it was too fragile.

Can you use the conversion tool on networks that don’t offer eSIMs directly? There are still many networks, especially smaller or cheaper ones, that only offer physical SIMs.

Do you know if hardware decode of 4K HEVC works on the Orange Pi 5?

Thanks. I didn’t realise you can’t do relays anymore on the selfhosted version. That sucks…

You can set up relay nodes in the Netmaker config, and enable them only for those nodes behind NAT that need relaying. I’ve generally had good experience with Netmaker—when it works, it works—but several times it auto-updated and wiped my network config in the process.

What is your experience with Netbird vs Netmaker?

Tailscale doesn’t require you to wrestle with certs or the networking setup required to do NAT traversal. And they do it well, you don’t have to wonder whether you’ve screwed something up that’s degrading NAT traversal only in certain conditions. It just works. That said, I’ve been through the wringer already on these topics so Headscale is not painful for me.

Does Headscale require additional work to deal with NAT traversal on clients? Or is it just for the controller node itself?

For what it’s worth, I usually install Ubuntu Server instead of Debian because it comes with a few more things out-of-the-box that I would install anyway. I have several installations of 22.04 that have been upgraded since 16.04 and they work no problem. (I also have a few Debian installations working similarly well.)

+1 for mxroute. I’ve been using them for several years with no trouble whatsoever.