forgejo_admin
0 followers · 0 following
  • Joined on 2025-07-24
Repositories
1
 Projects Packages Public activity Starred repositories
47. The Proposed Filename shall always include at least one token derived from the AI Vision Descriptor.
46. The Proposed Filename shall never duplicate within the same batch; a numeric suffix " (2)" shall be appended when collisions occur.
45. The Proposed Filename shall be ≤ 60 characters long, excluding the original extension.
44. The Proposed Filename shall always exclude stop‑words such as "the", "a", "an", "and".
43. The Proposed Filename shall start with an uppercase letter and contain only letters, numbers, spaces, and hyphens.
42. The final pool shall be truncated to a maximum of six distinct, natural‑language tokens.
41. The server shall combine Enhanced Keyword Set + AI Vision Descriptor into a ranked pool, giving 70 % weight to Vision tags and 30 % to user keywords when resolving conflicts.
40. The remaining labels shall form the AI Vision Descriptor list for that image.
39. The system shall discard any label below 0.40 confidence.
38. Each background job shall send the image to a vision API (e.g., OpenAI Vision or Google Vision) requesting labels and confidence scores.
37. Users can manually delete any auto‑suggested keyword before upload.
36. The client shall merge and de‑duplicate the Enhanced Keyword Set before re‑rendering the chip‑list UI.
35. The enhancement endpoint shall invoke an LLM that returns up to ten additional, SEO‑relevant keywords ranked by search volume.
34. Pressing the button shall call /api/keywords/enhance with the current Keyword Set and target locale "en‑US".
33. The "Enhance keywords with AI" button shall be disabled until at least one keyword is typed.
32. The server shall respond synchronously with a batch_id and an initial status of "PROCESSING".
31. The server shall enqueue one background job per image for AI Vision processing.
30. The server shall persist the raw binary files to an object‑store bucket under a time‑based UUID folder.
29. After drop, the client shall POST a multipart/form‑data request to /api/batch containing files and raw Keyword Set.
28. The client shall compute SHA‑256 checksums of files to avoid duplicate uploads in the same batch.