Your comment is AI-generated. Your entire README.md is AI generated. Your project structure is a mess, multiple overlapping packages. You declare a pkg/logger package, and yet tons of other code uses a bare stdlib log.Logger.
It looks like none of your CI tests have passed a single commit.
You have an install.sh script that attempts to download an artifact from a non-existent repo dockbridge/dockbridge.
Yep, the project is completely AI generated. I don't hide it. You can see the specs that I used initially for this project. And it was generated by multiple different AI tools.
As it's just a small tool I've created for myself, and share with others. :) It's not a thing I'm selling here. So, yep, it's not something with super high quality, especially from the code perspective. I know it. :)
And thanks for your comment. I'll apply your recommendations. ;)
Or feel free to open a PR, if you want. I'll be grateful.
For me, it's a tool I created because I'm often running stuff with docker, it takes a lot of memory. And additional memory on macs costs too much. :D
oh, yep... About that "insecure", it's implemented because the instances are dropped, when inactive. And after the reprovisioning, new instance on Hetzner very often has the same IP. But other key. So, it's more or less expected behavior, that you have same ip with different keys.
It could be an improvement later in this area. But it's not the most critical stuff.
> And these, IMO, are more prevalent than the positive ones overall.
If a problem is this widespread, a conference is arguably the best place to address it.
> but there are also numerous bad examples of AI use
which should be discussed publicly. I think we all have a lot to learn from each others' successes and failures, which is where coming together at a conference can really help.
Just an aside, but I feel like the codebase could use some comments. I don't use Zig so it may just be my unfamiliarity with the language, but at first glance code like this doesn't seem immediately straightforward:
To be added to the Prohibited List, a substance must meet any two of the following three conditions:
1. It has the potential to enhance sport performance. (potential -> a theoretical mechanism, even if unproven)
2. It represents an actual or potential health risk to the athlete.
3. It violates the spirit of sport.
Most of these peptides haven't passed adequate human safety trials, and their long term side effect profile is unknown. Additionally, an attempt at using anything to gain an unfair advantage violates the spirit of sport, even if the effect is placebo or even negative.
Your comment is AI-generated. Your entire README.md is AI generated. Your project structure is a mess, multiple overlapping packages. You declare a pkg/logger package, and yet tons of other code uses a bare stdlib log.Logger.
It looks like none of your CI tests have passed a single commit.
You have an install.sh script that attempts to download an artifact from a non-existent repo dockbridge/dockbridge.
You're binding to 0.0.0.0, so someone with a public IP will have an exposed docker daemon. You claim security but "Implement proper host key verification" is a TODO item: https://github.com/Max-Levitskiy/DockBridge/blob/23d164232b8...
reply