[verdict][curated prompt][source: feedspace.io]
Can I vibecode Feedspace?
// buildable in a weekend, but real gaps stay open
The form, the queue, the wall and the embed widget are one sitting, as the two tools here show. What is not: 150+ sources with 120+ on auto-sync, on an extraction engine Feedspace owns in-house, and widgets that fill themselves from curation rules. Only collecting written reviews through your own form? Build it. Want the ones you have elsewhere kept current? Don't.
confidence: medium
what it is: Collects text, video and audio reviews, imports existing ones, embeds them anywhere
Buildability index · an editorial game
- Price 29 $/month weight: plus 3
- Time multi-day weight: plus 1
- Category testimonials no weight
- Moat integrations · infrastructure scale · execution quality weight: minus 4
- Confidence medium weight: zero
- What you lose 5 items weight: minus 2
- Site feedspace.io (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
A public form collects a written, video or audio review, you approve it, and saved filters decide which approved reviews appear on each embeddable widget and hosted wall page.
what you need
- a small always-on host
- somewhere to keep uploaded video and audio
- ffmpeg to convert recordings into a web-playable file
The collection form in the middle is a weekend · the 150+ source fetch engine and the curation rules either side of it are not.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a testimonial system for my own site where the wall keeps itself up to date. Requirements:
- Python 3 with FastAPI, SQLite via sqlite3, Jinja2 for server-rendered HTML, and local disk for
uploads. Single process, no Docker, no signup flow, no tenants. It serves one site: mine.
- Collection page: a shareable link taking a star rating, a written quote, and optionally a video
or audio take recorded in the browser. Ask for name, role, company and a photo, let me mark which
of those are required, and stop recordings at three minutes.
- Re-encode recordings to MP4 with a thumbnail in a worker off the request path, keeping the
original. If ffmpeg is absent, store the upload and flag it rather than failing the submission.
- Moderation screen at /inbox behind an .env password: newest first, approve or bin, plus free-text
labels I can attach to a review.
- Now the part I actually care about. A display is either a hand-picked list or a saved filter. A
filter can require a minimum rating, a media type, a photo on the reviewer, a job title, a named
company, one of my labels, a phrase that must appear, and a phrase that must not.
- When a review is approved, every filter it satisfies picks it up immediately, with no republish
step. Each display shows whether it is filtered or hand-picked and how many reviews it resolves to.
- Let me override a filtered display by pinning up to three reviews to the front of it.
- Embedding: a one-line script tag plus an empty div. Attach a shadow root and inject markup the
server already rendered, so the host theme cannot restyle it and the quotes sit in the response.
- Three presentations: a masonry grid, a swipeable row, and a slow vertical ticker. Theme, accent
and radius come off data- attributes.
- A standalone wall at /wall with my logo, a call to action, and Review plus AggregateRating
structured data emitted from the same query that renders the cards.
- A score badge: rounded average and total count, recalculated whenever a review is approved or removed.
- Public endpoints get a per-IP throttle and an invisible decoy field, since anything with a form
attracts bots.
- README covering the embed snippet, the .env keys, and running it behind nginx with a TLS cert.
- Not building: fetching reviews I already have on Google, Trustpilot, G2, Yelp or an app store, or
polling them for new ones. That is a parser per platform plus someone maintaining them, which is
not a weekend. Teammates and outbound review-request email are out too. Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- 150+ review sources with 120+ on auto-sync, on an extraction engine Feedspace owns and runs in-house
- the upkeep · sources change and keeping the fetching working is someone else's job
- rule-based curation · matching new reviews join a widget or wall page by themselves, so the embed never goes stale
- in-browser video and audio recording that works on mobile without an app, and the media pipeline behind it
- aggregate rating badges that stay accurate because the auto-syncs keep feeding them
Why people still pay
Because the hand-built version decays. A wall you assemble yourself is accurate the week you build it and stale three months later, the newest review sitting in an inbox nobody pasted from. Here neither end stays manual: reviews arrive on their own, rules decide what reaches the widget. Rebuilding it means owning the fetching, not just the form.
moat: Integrations Infrastructure scale Execution quality what a moat is
the in-house fetch engine and the curation rules are the two automated ends · the collection form between them is the easy part
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (1) — and why
- Famewall (si apre in una nuova scheda) — The free plan stops at 10 testimonials and one video; useful demo, not a permanent replacement.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.