trexd

Declarative reproducible configuration is probably the main draw.

This happened to me recently with verification to Coinbases's KYC system. I was repeatedly denied verification and after contacting their support on X (the only method of contacting support without logging in is social media) they gave me the same ring around that you've experienced. Ultimately I solved the issue by using my girlfriend's phone to take the pictures of my license.

The root of the issue in my case is probably caused by my camera's low quality pictures from a lack of AI post processing since I use Graphene OS. It sucks that you can no longer easily contact a human when you're really stuck.

I bought all the parts for this last week based on the GitHub project. Looking forward to being able to use this guide!

I found that building my configuration on a virtual machine was the best way to go. This way I was not desperate to get things working and simply moved when I felt like all my essential programs were in place.

I was speaking more to preventing companies from using your open source work, but I guess in this instance the emphasis is on getting paid.

Why not just change the license to GPLv3 for the upcoming version?