Fujimod
Try your camera firmware in the browser and build Fujimod SD boot files.
Three answers in, one culturally coherent evening out — powered by the Qloo taste graph (Qloo Agentic Hackathon)
Translation pending
LifestyleTypeScript · HTMLGitHub @sparkyqinOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Three answers in, one culturally coherent evening out — powered by the Qloo taste graph.
Most agents answer well. Taste Concierge knows what people like: it maps a 3-question interview to Qloo's taste-graph entities (250M+), then chains insights across dining, film, music and retail to compose an evening that fits that person — not the charts.
An LLM alone recommends popular things. Taste Concierge recommends that person's things:
/search./v2/insights call is seeded by
your entities — and the playlist is additionally seeded by the chosen
film, so the music follows the night's centerpiece. That's cultural
coherence, not four independent top-10s.Remove Qloo and the product collapses: without the taste graph there is no entity affinity, no cross-domain coherence, and no grounding — just generic popular answers.
# 1. Get a hackathon API key: see the Devpost overview page / docs.qloo.com
# 2. Configure and start
cp .env.example .env # put your key in QLOO_API_KEY
npx vercel dev # local dev server
Deploy:
npx vercel --prod # set QLOO_API_KEY in the Vercel dashboard
index.html the interview UI + plan cards (zero-framework, fast)
api/plan.ts serverless endpoint: the agent loop
src/lib/qloo.ts Qloo client (X-Api-Key, GET-only, hackathon base URL)
src/lib/agent.ts the pipeline: mapAnswersToEntities → composeEvening
→ recomposeWithRejection (the negative-feedback loop)
The agent pipeline is deliberately small and inspectable — every Qloo call and every affinity decision can be traced in the code.
Built for the Qloo Agentic Hackathon. License: MIT.