feat: ImaGen as a direct live third compose option ('Bild generieren') #29
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What (m, PWA — enhancement to #28)
m: „wir könnten auch direkt imagen als dritte Option erlauben.“
In addition to Eigene Medien and Aus Galerie wählen (#28), add a third compose source: 'Bild generieren (KI)' — the sender enters a prompt and ImaGen (FLUX on mRock) generates an image on the fly that becomes the card's image.
Why it's a follow-up, not part of #28
The #28 design deliberately keeps ImaGen out of the request path because generation takes seconds–minutes — fine for the offline gallery feed, but a live 'generate now' button needs async UX: submit prompt → show progress/spinner → poll for completion → preview → use. Plus: generation cost/rate-limiting, prompt moderation, mRock-availability handling (graceful 'gerade nicht verfügbar'), and the generated image flows into the same copy→postcard_images path as a gallery pick.
Design points (the eventual worker resolves)
/compose/generateendpoint (or job) → ImaGen via the/imagineskill / ImaGen HTTP API → store result undergallery/-style or a per-card key → return URL to the compose page (poll or SSE). Keep it off the synchronous form submit.Sequencing
After #28 (the gallery MVP) lands — reuses its source-toggle UI + copy-into-card path. Same compose track. otto-head assigns when #28 is done.
DoD