business

Verdict

Submitted 7/27/2026, 4:03:34 PM · Completed 7/27/2026, 4:14:00 PM

6.5
pivot
The idea

Ask HN: Do you hide your AI behind a curtain?

Show original source text →
I used AI to build a music recommender system that itself uses no AI in its operation. I have been promoting the system in communities that can sometimes be considerably anti-AI. But people usually assume that it is AI because, well, it's a recommender system. Anyways, after a 30-year break, I rebuilt it and got it working the way I always wanted! It basically uses the same 10 lines of code, (for which I was granted now-expired US patent #5749081), but with a good interface around it instead of a lousy 1990s one. You tell it your 5 favorite albums, and it recommends other albums to try. It uses collaborative filtering (CF) to generate the music recommendations. It's just now exiting the "cold start" phase that all CF systems have to get through. The tagline I use is: "No sign-up needed, instant results, takes 2 minutes to try. Not AI." Try it here: [https://SimilaritiesEngine.com](https://similaritiesengine.com/) If you're curious, here's a New York Times article from way back then. (But the URL in the article is wrong, so if you go read it, come back here to try the new version, alive and working): https://archive.nytimes.com/www.nytimes.com/library/cyber/0101miracolumn.html The system is about 6,000 lines of code, vibe-coded by me using Claude Code. I have basically never looked at a line of the source. (But I have a part-time partner now who is hand-revising some code.) Up until now, I have publicized the site mostly on Reddit. Boy, did I catch grief there for it "being an AI system." At first, I got Claude's help on the language for some of the website copy and some of my Reddit posts. I mostly stopped getting downvoted for it being AI once I learned my lesson (in "The Great r/Vinyl Debacle," https://www.reddit.com/r/vinyl/comments/1ul7o7c/i_built_a_music_recommender_in_1996_that_only/ ), which led me to tell Claude "Never use em dashes in anything, anywhere, that you help me with!" (To be fair, the downvotes made the post controversial and drove views to 15K, but my actual URL got buried.) You could argue that my "no AI" claim isn't fully true, and that I should instead say something like "no LLMs or generative AI are in the product itself, just classic collaborative filtering." But what I tell people sometimes is this: The weights file behind a SOTA AI system like Claude Fable is, by some estimates, 2 TB or more. The equivalent file in my system (my graph database or "links" table) is about 3 MB in size right now. So my question for Hacker News is: how often do you hide the fact that AI was involved in the production of your product? I actually think, based on some of the things I have seen in the press and on discussions I have had with people, that acquaintances might be talking behind my back in an "oh he's heavily into AI so you should not trust him" sort of way. Yeah, saying that makes me sound crazy. Am I crazy? Details on the tech (Cloudflare, D1, etc.) can be found on the website too.
TRIZ inventive level: 3/5· Principles: parameter changes, self-service
Synthesis verdict
<<b>Pivot</b>: The music recommender system has a unique selling point with its 'No AI' tagline and leverages collaborative filtering, but faces challenges in user trust, unclear monetization, and vulnerability to competition. The system's simplicity and instant results enhance user experience, but the involvement of AI in its initial build and potential user skepticism introduce risks. Monetization paths aren't clearly outlined, and the system's differentiation is limited and fragile. The system's core functionality is relatively simple, and its non-AI operational nature is a marketable differentiator. However, the competitive landscape already includes several recommendation-focused platforms that can easily replicate the core algorithm and add a no-sign-up UI. The 'no AI' claim is semantically weak, and the product's value proposition hinges on marketing rather than a truly novel technical advance. To pivot, the system should focus on refining its UI/UX, clarifying its 'no AI' claim, and developing a clear monetization strategy. It should also consider optimizing its collaborative filtering algorithm as the user base grows and exploring potential revenue streams, such as targeted advertising or affiliate partnerships with music platforms.

Strengths

  • - unique selling point with 'No AI' tagline
  • - leveraging collaborative filtering
  • - simplicity and instant results enhance user experience

Weaknesses

  • - vulnerability to competition
  • - unclear monetization
  • - potential user skepticism about 'no AI' claim

Best angle

Refine the system's UI/UX, clarify its 'no AI' claim, and develop a clear monetization strategy to differentiate itself in a crowded market.

Panel verdicts

Competition

nvidia/nemotron-3-nano-omni-30b-a3b-reasoning

6.0

“A no - signup, lightweight, non - AI music recommender occupies a narrow niche that incumbents can quickly copy, making its differentiation limited and fragile.”

The idea offers a clear point of differentiation: a music recommender that requires no sign - up, runs on a tiny 3 MB data store, and markets itself as "not AI" while using classic collaborative filtering. This appeals to anti - AI communities and provides an instant, low - friction experience that larger services (Spotify, Apple Music, Last.fm, Pandora) do not provide because they all demand registration, collect extensive user data, and rely on deep - learning models. However, the competitive landscape already includes several recommendation - focused platforms that can easily replicate the core algorithm and add a no - signup UI, especially since the underlying collaborative - filtering technique is well - known and not patented anymore. The expired US patent #5749081 offers no legal moat, and the 6,000 - line codebase, built with limited technical scrutiny, does not create a technical barrier to entry. Moreover, the "no AI" claim is semantically weak - collaborative filtering is itself a form of machine learning, and the product's value proposition hinges on marketing rather than a truly novel technical advance. Consequently, while the current niche is defensible in the short term, it is vulnerable to larger incumbents or new entrants that can copy the interface and algorithm, eroding any sustainable advantage.

Viability

nvidia/llama-3.3-nemotron-super-49b-v1(fallback #1)

8.0

“A small team can sustainably develop and grow this non-AI music recommender system, leveraging its unique selling point, despite needing strategic communication to manage AI development perceptions.”

The project's core functionality (collaborative filtering) is relatively simple and well-established, with a small codebase (6,000 lines) and minimal technical debt due to its non-AI operational nature. The 'no AI' selling point, while somewhat debatable, is a marketable differentiator. Challenges lie in perception management (clarifying the AI involvement in development vs. operation), scaling the user base beyond niche communities, and potentially optimizing the collaborative filtering algorithm as the user base grows. The cold start phase is nearly overcome, and the existing infrastructure (Cloudflare, D1) suggests scalability is manageable. A 2-person team can realistically maintain and incrementally improve the system within the given timeframe, assuming focus is placed on user acquisition strategies and refining the UI/UX based on feedback.

Market

meta/llama-3.3-70b-instruct

This agent failed to return a verdict (gave up after 1 attempts: timeout (attempt 1)). The synthesis ran with the remaining agents.

Risk

nvidia/nvidia-nemotron-nano-9b-v2(fallback #2)

8.0

“The cold start problem and no-budget user base will destroy user retention and revenue before regulatory or platform risks materialize.”

The system's reliance on collaborative filtering (CF) with only 5-album input creates a fundamental cold start problem that will likely result in poor recommendation quality. Users will either find the suggestions irrelevant or generic, leading to high churn within 6 months. Even if the 'no AI' claim is technically accurate, the anti-AI communities you're targeting may still perceive it as AI due to the recommender system's nature, eroding trust. Additionally, the lack of a clear monetization strategy or reliance on no-budget users means there's no sustainable revenue engine. If ad-based or freemium, low engagement from budget-conscious users will kill the venture. The expired patent also removes legal protection, but that's a longer-term risk. The immediate threats are churn from ineffective recommendations and no-budget users failing to convert.

Monetization

nvidia/llama-3.3-nemotron-super-49b-v1(fallback #3)

7.0

“A differentiated 'No AI' music recommender with a proven CF model, facing challenges in user trust and unclear monetization.”

The music recommender system leverages a unique selling point with its 'No AI' tagline, effectively differentiating itself in a market saturated with AI-driven solutions. The use of collaborative filtering (CF) on a small, manageable dataset (3 MB vs. TBs for AI systems) supports this claim. The system's simplicity, instant results, and no-sign-up requirement enhance user experience. However, the involvement of AI in the system's initial build (via Claude for website copy and posts) and potential user skepticism about the 'No AI' claim introduce risks. The cold start phase is now behind, which is a positive. Monetization paths aren't clearly outlined, but potential revenue streams could include targeted, non-intrusive advertising or affiliate partnerships with music platforms. The system's tech stack (Cloudflare, D1) suggests scalability. **Score Breakdown**: Innovation (8), Market Fit (7), Transparency/Risk (6), Scalability (8), Monetization Clarity (4).

Synthesized by meta/llama-3.3-70b-instruct · 73.1s