<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: shujip</title><link>https://news.ycombinator.com/user?id=shujip</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 03 Sep 2026 06:59:26 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=shujip" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by shujip in "Can I opt out of my input or output data being used for training?"]]></title><description><![CDATA[
<p>Yes. If the privacy control only exists per user, it isn't a control for a team.<p>Defaults matter more than the blog post. "You can opt out" is not the same product as "the org can actually enforce opt out."</p>
]]></description><pubDate>Wed, 02 Sep 2026 14:04:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=49536440</link><dc:creator>shujip</dc:creator><comments>https://news.ycombinator.com/item?id=49536440</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49536440</guid></item><item><title><![CDATA[New comment by shujip in "Check if a file was made with Claude"]]></title><description><![CDATA[
<p>A watermark answers "did this model touch the file?" It doesn't answer "did a person read it and stand behind it?"<p>Detection will get gamed, and a lot of useful text is already mixed. The more useful check, for me, is still human: would I put my name on this before it goes out?</p>
]]></description><pubDate>Wed, 02 Sep 2026 14:03:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=49536418</link><dc:creator>shujip</dc:creator><comments>https://news.ycombinator.com/item?id=49536418</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49536418</guid></item><item><title><![CDATA[Show HN: Nichestarter – Stop guessing what to build. Find validated pain points]]></title><description><![CDATA[
<p>I’m Lu. I spent the last year falling into the classic trap: building solutions first, then looking for problems. After launching two projects that got zero traction, I realized I needed to validate demand before writing code.<p>I started manually browsing subreddits like r/SaaS, r/marketing, and r/smallbusiness, looking for posts containing phrases like "how do I," "why is X so hard," or "I hate Y." It worked, but it was unscalable.<p>So, I automated it. I built Nichestarter.ai.<p>How it works (The Stack):<p>Ingestion: I try to scrape daily threads from high-signal subreddits (and soon G2 reviews).<p>Filtering (The hard part): I run raw posts through a cheaper model to filter out noise, general questions, and low-effort rants.<p>Analysis: Valid complaints are passed to llm to analyze "Willingness to Pay" (based on sentiment and business context) and "Solution Complexity."<p>Matching: I built a match engine that pairs these problems with user skills (e.g., "React Dev" + "Marketing Pain Point").<p>The Result: A daily feed of "Gap Analysis." Instead of just seeing a Reddit post, you see the core pain point, the customer segment, and a generated MVP roadmap.<p>It’s currently in beta. I have a free tier that sends a weekly digest of the best opportunities found.<p>I’d love to hear your feedback on the matching logic—specifically, does the "Opportunity Score" feel accurate to you?<p>Thanks!</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46780122">https://news.ycombinator.com/item?id=46780122</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 27 Jan 2026 14:10:22 +0000</pubDate><link>https://www.nichestarter.ai/</link><dc:creator>shujip</dc:creator><comments>https://news.ycombinator.com/item?id=46780122</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46780122</guid></item></channel></rss>