Over the past day, people have reported things like unusual text-generation behavior, sluggish generators, failed story imports, and browser data apparently disappearing.
The difficult part is that nobody knows whether these are:
- intentional model or backend changes,
- temporary maintenance,
- an upstream provider problem,
- a generator-specific bug,
- or simply a browser/device issue.
That uncertainty is causing more damage than the bugs themselves. Users start guessing which model is running, assuming changes were never tested, repeatedly reporting the same problem, blaming their own devices, or arguing with each other over whether anything actually changed.
A single sentence from the developer could often stop most of that:
June 26: Text generation is currently affected by a backend/provider issue. Investigating.
Or:
June 26: Updated the default text model. Some prompt-following issues are still being tuned.
I understand that Perchance is a huge and unusually complex project maintained primarily by one person. It is free, the developer has no obligation to write polished release notes, and nobody should expect detailed explanations or guaranteed repair dates.
That is exactly why I am suggesting something much smaller than a traditional changelog.
A minimal update system could be:
- one pinned Lemmy thread, page, or status line;
- only for changes or problems that noticeably affect users;
- a date, the affected feature, and one sentence;
- simple labels such as changed, investigating, and resolved;
- no detailed technical explanation and no promised ETA.
For example:
June 26 — Text generation — Investigating: First responses may ignore instructions. This may be related to a recent backend change.
This would not only benefit users. It could reduce the developer’s workload by:
- preventing dozens of duplicate reports;
- producing more accurate bug reports;
- stopping unsupported theories from becoming accepted as fact;
- letting experienced users answer newcomers correctly;
- reducing hostility caused by people interpreting silence as indifference.
The community already tries to diagnose changes unofficially, but without one authoritative sentence, we can only speculate. Even “I changed something, expect temporary instability” is far more useful than complete silence.
This is not a demand for constant communication, a public development roadmap, old models being permanently preserved, or an explanation for every internal adjustment. It is a request for the smallest sustainable signal that tells users, “Yes, something changed,” or “Yes, this problem is known.”
Developer: would some version of this be realistic? The format does not matter. A pinned post, tiny status page, generator notice, or occasional one-line Lemmy update would all solve most of the problem.
And for everyone else: would a minimal log like this meaningfully help you, or is there an even lower-maintenance format that would work better?
can't scrolling down here, help!
In rare condition(idk the trigger yet), happened in story-gen and ai-furry-generator twice, one is for setting up nickname; another is for unban user =>
@perchance@lemmy.world