Suspicious.
The post itself reads authentic, but structural evidence reveals coordinated manipulation: two accounts (u/dearesteater and u/sinuk-dev) show strong same-hand stylometric signals (matching colloquial interjections, similar concessive phrasing), and three insular accounts only ever engaged in this thread. This pattern is consistent with sock-puppet comment boosting to artificially validate the OP's experience.
Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 14 comments and 6 unique commenter accounts.
- Signal count: 0 high, 1 medium, 0 low flag; 1 coordination-class signal.
Not conclusive, but the writing-style overlap is enough to warrant skepticism — especially when these same accounts are also new or copy-pasting praise.
Full evidence trailSources, public checklist, values lens, network map, account coverage, archive, and sharing tools.
Review before sharing.
Hugin reports are evidence packets, not accusations. Use the rating as a prompt to inspect sources, limitations, and archived material before quoting a claim elsewhere.
Has anyone else sold an In-Appp purchase really quickly after launching and afterwards got nothing?
Source checks
26 public comments loaded for r/micro_saas.
Public comment bodies were retained with the report snapshot.
7 author age values were unavailable.
1 selected author history checked; 1 unavailable.
14 reply edges mapped.
1 same-hand writing pair surfaced.
0 unique external identifiers extracted.
0 prior archive matches returned.
Show your work
Deterministic explanation of the stored scan inputs behind the verdict. This is not hidden model reasoning; it is the evidence checklist Hugin can show publicly.
Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 14 comments and 6 unique commenter accounts.
- Signal count: 0 high, 1 medium, 0 low flag; 1 coordination-class signal.
- The scan crossed the caution threshold, but did not show enough stacked proof for likely scam.
What pushed risk up
Not conclusive, but the writing-style overlap is enough to warrant skepticism — especially when these same accounts are also new or copy-pasting praise.
- u/dearesteater ↔ u/sinuk-dev — Both use colloquial interjections ('Ag', 'Ja', 'lol') and share conversational clause structure with qualifiers; dearesteater's 'well under 1%' and sinuk-dev's 'but haven't been able to' show similar concessive phrasing patterns.
1 commenter pair had medium-or-higher stylometry similarity.
- u/dearesteater / u/sinuk-dev: medium - Both use colloquial interjections ('Ag', 'Ja', 'lol') and share conversational clause structure with qualifiers; dearesteater's 'well under 1%' and sinuk-dev's 'but haven't been able to' show similar concessive phrasing patterns.
What limited confidence
7 scanned authors had unknown account age, so absence of young-account signals is lower confidence.
What kept the rating lower
Hugin mapped 14 reply edges and did not find a mutual-reply clique.
- 7 author account ages were unavailable.
- 1 selected author history was unavailable to the scan.
- Username shape alone is never treated as a finding; it is only context when stronger public signals also appear.
- Likely scam: multiple high-severity signals, prior identifier reuse, or several coordination signals stacking together.
- Suspicious: one high-severity signal, multiple medium signals, or one concrete coordination signal that deserves review.
- Inconclusive: weak, conflicting, or partial signals where the scan cannot justify either trust or a stronger warning.
- Looks legitimate: no structural red flags, available metadata, and clean coordination passes.
Values lens
Use scans to slow down, inspect public signals, and keep uncertainty visible. Never use them to harass, shame, or flatten people into a verdict.
Fair-use checks
- What was observed, and what is interpretation?
- What data is missing, blocked, or confidence-limiting?
- Would the wording feel fair if it were about someone you care about?
What the post is doing
- u/dearesteater and u/sinuk-dev share medium-confidence same-hand writing signal: both use 'Ag'/'Ja' interjections, similar concessive clause structure ('well under 1%' vs. 'but haven't been able to'),
- u/dearesteater dominates comment section with 4 consecutive replies (comments 6–9), all score 0, creating appearance of organic advice thread
- Three accounts (u/dearesteater, u/sinuk-dev, u/Zoxibi) show insular behavior: only ever replied within this single thread, no cross-community activity
- All comments score exactly 0 despite varied lengths and apparent relevance, suggesting vote manipulation or bot-like posting pattern
- u/Curious-Objective-21 (OP) metadata unavailable to this scan; combined with sock-puppet ring signals, suggests potential coordinated throwaway account
Automated flags
Not conclusive, but the writing-style overlap is enough to warrant skepticism — especially when these same accounts are also new or copy-pasting praise.
- u/dearesteater ↔ u/sinuk-dev — Both use colloquial interjections ('Ag', 'Ja', 'lol') and share conversational clause structure with qualifiers; dearesteater's 'well under 1%' and sinuk-dev's 'but haven't been able to' show similar concessive phrasing patterns.
Coordination map
Who replied to whom in the scanned comments. Organic threads branch out from the post; accounts that reply back and forth to each other (red links) or hub around one shared identifier (dashed amber) are the structural fingerprints of a coordinated pod.
- mutual-reply ring member
- account under 30 days
- other commenter
- replied to each other
- shared identifier
Commenter patterns
Recent public Reddit activity for the OP and selected accounts, plus same-hand writing checks when the stylometry pass runs. These are coverage-limited evidence summaries, not identity or availability claims.
Reddit did not return recent public activity for this account during the scan. Treat this as missing coverage, not a finding by itself.
- u/dearesteater / u/sinuk-dev medium confidence - Both use colloquial interjections ('Ag', 'Ja', 'lol') and share conversational clause structure with qualifiers; dearesteater's 'well under 1%' and sinuk-dev's 'but haven't been able to' show similar concessive phrasing patterns.
Account age coverage
OP and scanned commenters are shown when Hugin recovered profile metadata or an oldest-public-activity age floor. Lower-bound ages are labeled as estimates; unknown age remains missing coverage, not a finding about the account.
Archived evidence
Snapshot of the post and comments at scan time. Preserved here so the evidence survives even if it gets deleted on Reddit.
- u/saypofitscore 0Sorry to hear that, but as far as I know early success is an exception, in most cases it takes time to sell, so just keep up your original plan and don't feel disappointed, good luck🫡
- u/Curious-Objective-21score 0Thank you! Yes, we'll see how it turns out. I really enjoy developing the app, so I guess that and the 5$ from that kind stranger is already a success :)
- u/sinuk-devscore 0I had one person in Sweden make an IAP within a few days of launching. Since I’ve done a product hunt launch and posted on several subreddit but haven’t been able to turn any of my new users into customers. I even added Swedish localization in my latest update as a thank you lol.
- u/Curious-Objective-21score 0Haha, yeah my customer was from Belgium. I already added dutch and French though :P
- u/Zoxibiscore 0What is your app?
- u/Curious-Objective-21score 0CityTour AI :)
- u/Zoxibiscore 0Cool stuff, I'll check it out. How did you build it and how did you decide your tech stack?
- u/Curious-Objective-21score 0Thank you very much :) The app itself is with Kotlin Multiplattform, since I made an android app before and I didn't want to maintain two separate apps. For the backend I used Rust, since it's really performant and wanted to learn it. The backend asks an llm for points of interests and a rating and the backend matches it on location data from sources like openstreet maps and wikidata. I wanted to keep it low cost, but scalable.
Original on Reddit: https://www.reddit.com/r/micro_saas/comments/1ufhxlx/has_anyone_else_sold_an_inappp_purchase_really/ — “Has anyone else sold an In-Appp purchase really quickly after launching and afterwards got nothing?”
Share this report
Share this link in a Reddit reply when the thread needs supporting evidence. The report stays public so anyone reading the thread can review the data themselves.
Reports like this stay free for everyone. Keep Hugin free →