ryper

Careful. There are quite a few terms of service that you’ve agreed to over the years that if certain aspects of them were enforced, you wouldn’t think they were very reasonable.

Epic has an entire legal department to read over agreements like that, and yet they deliberately breached the terms. That's hugely different from someone unknowingly breaching a TOS that they didn't read.

Epic changed the mobile versions of Fortnite to add an option to pay for V-Bucks through their own system, which is against the terms of both Apple's app store and Google's. That got them kicked off of both app stores and then they sued Apple and Google.

This isn't some random developer, it's a developer that has already breached a contract with Apple. It's reasonable for Apple to be wary of entering into another contract with them when the CEO is publicly complaining about the terms.

There's definitely a case to be made that Epic shouldn't need an Apple developer account to make their own app store, but Apple is well within its rights to deny them an account based on their history.

Apple said one of the reasons they terminated our developer account only a few weeks after approving it was because we publicly criticized their proposed DMA compliance plan. Apple cited this X post from this thread written by Tim Sweeney. Apple is retaliating against Epic for speaking out against Apple’s unfair and illegal practices, just as they’ve done to other developers time and time again.

Epic breached the terms of its agreements with Apple and Google to kick off its lawsuits against them in 2020, and now that Sweeney is openly complaining about Apple's terms for third-party app stores Apple doesn't trust Epic not to breach those too. Seems reasonable.

Spotify should have handled their issues with the app store rules but just not making an IOS app. If the biggest music streaming service in the world didn't work with iPhones maybe Apple would have had to reconsider some things.

The issue here is that Apple only allows devs to let users sign up for their service through Apple. Apple also demands 30% of the subscription fee when doing this. They don’t allow a developer to have a button in the app that allows to sign up through their website, or to mention that you can sign up through a website.

"Reader" apps like Spotify can have a link to sign up on their website. There are more rules around than there maybe should be, but it's allowed, and Apple's letter says Spotify chooses not to do it.

The article sounds like you could have the A records on a local DNS service like Unbound or Pi-hole instead of public DNS. I guess maybe they just need to be defined somewhere that they'll resolve for your Caddy instance.

Keepass has a synchronization mechanism, maybe you can get it to work between your phone and your PC?

If the files to be synchronized are accessible via a protocol that KeePass supports by default (e.g. files on a local hard disk or a network share, FTP, HTTP, HTTPS, WebDAV, ..., see the page 'Loading/Saving From/To URL' for details), then no plugins/extensions are required.

If one of the files to be synchronized should be accessed via SCP, SFTP or FTPS, you need the IOProtocolExt plugin, which adds support for these protocols to KeePass.

If one of the files to be synchronized is stored in a cloud storage: for most cloud storages, there is an integration with the local file system available (i.e. you can access your stored files using Windows Explorer). For example, Dropbox, Microsoft OneDrive and Google Drive provide such an integration. If such an integration is available, it is recommended that you access your database file this way; this often works better than accessing it via a protocol like FTP or WebDAV. If no such integration is available and your cloud storage also is not accessible via a standard protocol, a specialized KeePass plugin for this cloud storage might be available.

Like the other commenter said, you can use Let's Encrypt without needing to expose anything on your network to the internet. I set it up on my network a couple of weeks ago using this guide; I couldn't get caddy to work with duckdns but it worked with Cloudflare without any trouble.

I don't suppose the people responsible for the over hiring have seen any consequences?

The headline isn't clear, it's actually one fee; the ad tier doesn't have Dolby and the ad-free tier does.

Reader mode will get around that