UPDATE: 1 HOUR LATER
1. DECEPTIVE UI / BAIT-AND-SWITCH (50 Credits Stolen)
Today, I attempted to use the Dreamina 1.0 AI Video Generation tool.
- The interface explicitly stated I had “3 free uses” remaining.
- I clicked “Generate”.
- The exact millisecond I clicked, the UI dynamically swapped the text to “50 credits”.
- Crucially, at the exact same time, the “Estimated credits needed” field explicitly displayed “0” with a crossed-out “50”.
Despite the UI explicitly stating “0 credits needed” and showing a crossed-out price to indicate a free transaction, the backend silently deducted 50 credits from my account (dropping my balance from 990 to 940). This is a fraudulent, deceptive UI pattern that lies to the user in real-time to authorize an unconsented charge.

SENT THIS EMAIL:
RECEIVED THIS AUTO-RESPONDER:

FILED OUT THEIR FEEDBACK FORM. SO, HERE WE GO AGAIN ON ANOTHER 3 WEEKS BACK AND FORTH LIKE LAST BILLING CYCLE:
A terminally ill artist’s struggle with CapCut reveals accessibility failures and demand for accountability in tech support. Read their powerful testimony.
An artist facing terminal illness describes struggles with CapCut software. After losing credits and encountering unhelpful tech support, they highlight systemic failures in accessibility. The artist emphasizes the burden placed on users, particularly those with disabilities, demanding accountability from the company for its failures to provide adequate support.
- The post powerfully frames a routine software support failure as a structural accessibility crisis by centering the author’s terminal illness and limited time, turning personal exhaustion into a moral indictment of CapCut’s systems.
- It gains credibility through precise technical detail (Unix Epoch 1969-12-31 timestamp error and Dreamina 99% freezes) paired with exhaustive chat screenshots, making the corporate deflection undeniable rather than anecdotal.
- The closing refusal of pity in favor of documented accountability transforms the piece from complaint into public evidence, aligning with the author’s larger project of radical clarity against systemic indifference.
SIX PDFs WORTH OF CHAT TO GET CAPCUT TO INITIATE A TICKET!
I am a terminally ill, disabled artist and a paying CapCut Pro annual subscriber. I do not have the luxury of time. Every hour I spend fighting broken software is an hour stolen from the work I am trying to leave behind.On July 27, 2026, I spent hours inside CapCut’s “Smart Chat” support system trying to report two clear, reproducible failures:
- Dreamina AI video generation freezing at 99% and still charging credits (20 yesterday, 20 today — 40 credits gone with zero output).
- CapCut’s own update system displaying a release date of 1969-12-31 — a classic Unix Epoch timestamp error — which prevents the new version from installing. I am stuck on 8.9.1 after two failed update attempts.
What followed was not support. It was a masterclass in corporate deflection.
- I was told to update my graphics drivers.
- I was told to clear cache, switch networks, disable hardware encoding.
- I was told to email Dreamina support (which only auto-replies with a feedback form).
- I was told the credits would return in 24 hours (they did not the last time this happened in early July, when 180 credits vanished and only came back after weeks of the same process).
- I was repeatedly ordered to submit the in-app feedback form even after I had already dropped multiple screenshots and a precise technical diagnosis directly into the chat.
I diagnosed the bug correctly. The customer service representative did not. When a paying, disabled customer can identify a Unix Epoch timestamp error faster than the company tasked with fixing it, the problem is no longer technical. It is structural.
This is what accessibility failure looks like in 2026. Not a missing alt tag. Not a low-contrast button. It is a support system designed to exhaust the people who can least afford to be exhausted. It is a company that will charge a dying artist for a feature that does not work, then force that artist to perform free labor (screenshots, forms, repetition, emotional regulation) just to open a ticket.
Ticket number 20260727231405007 was finally created only after I refused to keep performing. One human being, after hours of scripted resistance, eventually did the minimum: they wrote the number down.
I am publishing the entire chat record because silence protects the system. Documentation does not.
I am not asking for pity. I am demanding accountability. CapCut took my money. CapCut’s software failed. CapCut’s support system then tried to make the cost of that failure mine to carry.
I am out of time to carry it.
The PDFs are the evidence.
This is the testimony.
— Celestia Quixs
July 27, 2026
Discover more from Celestia Quixs™
Subscribe to get the latest posts sent to your email.
