You’re right to be disappointed—and that’s on me. I announced “beta in 3 days,” then pivoted to a sign-up and shipped a pre-beta tech test with an untested key-verification path. That bug blocked most activations T.T. We’ve paused the test, and I’ve corrected the terminology in a new post.
Plan: fix licensing, re-package, smoke-test on clean PCs, then re-invite only when stable. No new date promises for ~60 days; we’ll post bi-weekly devlogs instead. Refunds welcome at info@gayeti.com.
If you can wait, then keep waiting. We can't give you a specific timeframe. If you can't wait, then ask for a refund. Is this how you handle things? You promised to share progress updates every Friday. Do you remember that? You only offer endless excuses to keep us waiting. We've already waited 113 days, and you're still making excuses to delay. Please stop making excuses. You're constantly eroding our trust in you. As your fan, I'm heartbroken to be treated like this.
You’re right to be upset. I broke my promise about Friday updates and I announced “beta in 3 days” before the build was ready—that’s on me. We paused after finding a key-verification bug that blocked many activations, but that doesn’t excuse the poor communication.
What I’m changing now:
- No new date until licensing is fixed and the RC is locked.
- Weekly devlogs, every other Friday 7pm (GMT+7), with a simple Done / In-Progress / Next checklist.
- Refunds honored anytime at info@gayeti.com.
I’m sorry for eroding your trust. I’ll earn it back with clear updates and a solid build—not more promises. 💙