okikio

It is more like using pre-cut vegetables to make a salad than anything else. I still made the salad I just used tools that sped up the repetitive parts.

That is basically what AI was here. I used it mostly for docs, research, templating, and basic setup. The project itself, the decisions behind it, and the final result are still mine.

I can understand the apprehension to AI generated code, AI generated anything to be honest. The reason I didn't mention it earlier is because it has never really mattered before.

In 10 years of building software, I’ve never needed to list out the tools libraries, editors, etc... that I've used as part of my process.

The code is fully open source and MIT licensed. You can use it however you wish.

tbh, it's a philosophical difference but imo AI can't create anything, it's not sentient. you can use it as a tool, but just because you use a hammer to create a roof does not mean the hammer created the roof...you did. a more apt metaphor would be you give AI a task it will give you a result it will not necessarily give you a solution.

I personally use AI like auto-complete, I've been using auto-complete for years, it's just smarter auto-complete imo.

A good example would be for this project, AI did pickup the patterns behind DDNS but it doesn't understand that Synology approaches DDNS in a somewhat unsafe manner natively. AI also doesn't understand the nuance by default that's primarily why the `cloudflare-ddns` project has a separate update model/process included under the `/updates` endpoint, so you can actually have a more secure alternative if your usecase demands it.

For my usecase I was fine with the slightly less secure but more Synology native `/nic/update` endpoint.

You should be able to use WAFs and other defences if you so wish, but it was more designed with the assumption that you are not exposing your DSM publicly, so there really isn't a point in using WAFs if you're not exposing publicly. If you are exposing publicly then you should absolutely look to setup WAFs, etc... Personally I recommend using Tailscale so you can access your NAS outside your private network, that way you avoid the headache of setting up WAFs.

you should be able to just use a CNAME record to point your custom domain at your Synology domain

The synology domain is a good solution too, but if you want a custom domain that's when you'd want to use the cloudflare ddns