frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

GPS and Time Dilation – Special and General Relativity

https://philosophersview.com/gps-and-time-dilation/
1•mistyvales•1m ago•0 comments

Show HN: Witnessd – Prove human authorship via hardware-bound jitter seals

https://github.com/writerslogic/witnessd
1•davidcondrey•1m ago•1 comments

Show HN: I built a clawdbot that texts like your crush

https://14.israelfirew.co
1•IsruAlpha•3m ago•0 comments

Scientists reverse Alzheimer's in mice and restore memory (2025)

https://www.sciencedaily.com/releases/2025/12/251224032354.htm
1•walterbell•6m ago•0 comments

Compiling Prolog to Forth [pdf]

https://vfxforth.com/flag/jfar/vol4/no4/article4.pdf
1•todsacerdoti•7m ago•0 comments

Show HN: Cymatica – an experimental, meditative audiovisual app

https://apps.apple.com/us/app/cymatica-sounds-visualizer/id6748863721
1•_august•9m ago•0 comments

GitBlack: Tracing America's Foundation

https://gitblack.vercel.app/
2•martialg•9m ago•0 comments

Horizon-LM: A RAM-Centric Architecture for LLM Training

https://arxiv.org/abs/2602.04816
1•chrsw•9m ago•0 comments

We just ordered shawarma and fries from Cursor [video]

https://www.youtube.com/shorts/WALQOiugbWc
1•jeffreyjin•10m ago•1 comments

Correctio

https://rhetoric.byu.edu/Figures/C/correctio.htm
1•grantpitt•10m ago•0 comments

Trying to make an Automated Ecologist: A first pass through the Biotime dataset

https://chillphysicsenjoyer.substack.com/p/trying-to-make-an-automated-ecologist
1•crescit_eundo•14m ago•0 comments

Watch Ukraine's Minigun-Firing, Drone-Hunting Turboprop in Action

https://www.twz.com/air/watch-ukraines-minigun-firing-drone-hunting-turboprop-in-action
1•breve•15m ago•0 comments

Free Trial: AI Interviewer

https://ai-interviewer.nuvoice.ai/
1•sijain2•15m ago•0 comments

FDA Intends to Take Action Against Non-FDA-Approved GLP-1 Drugs

https://www.fda.gov/news-events/press-announcements/fda-intends-take-action-against-non-fda-appro...
12•randycupertino•17m ago•3 comments

Supernote e-ink devices for writing like paper

https://supernote.eu/choose-your-product/
3•janandonly•19m ago•0 comments

We are QA Engineers now

https://serce.me/posts/2026-02-05-we-are-qa-engineers-now
1•SerCe•19m ago•0 comments

Show HN: Measuring how AI agent teams improve issue resolution on SWE-Verified

https://arxiv.org/abs/2602.01465
2•NBenkovich•19m ago•0 comments

Adversarial Reasoning: Multiagent World Models for Closing the Simulation Gap

https://www.latent.space/p/adversarial-reasoning
1•swyx•20m ago•0 comments

Show HN: Poddley.com – Follow people, not podcasts

https://poddley.com/guests/ana-kasparian/episodes
1•onesandofgrain•28m ago•0 comments

Layoffs Surge 118% in January – The Highest Since 2009

https://www.cnbc.com/2026/02/05/layoff-and-hiring-announcements-hit-their-worst-january-levels-si...
9•karakoram•28m ago•0 comments

Papyrus 114: Homer's Iliad

https://p114.homemade.systems/
1•mwenge•28m ago•1 comments

DicePit – Real-time multiplayer Knucklebones in the browser

https://dicepit.pages.dev/
1•r1z4•28m ago•1 comments

Turn-Based Structural Triggers: Prompt-Free Backdoors in Multi-Turn LLMs

https://arxiv.org/abs/2601.14340
2•PaulHoule•30m ago•0 comments

Show HN: AI Agent Tool That Keeps You in the Loop

https://github.com/dshearer/misatay
2•dshearer•31m ago•0 comments

Why Every R Package Wrapping External Tools Needs a Sitrep() Function

https://drmowinckels.io/blog/2026/sitrep-functions/
1•todsacerdoti•31m ago•0 comments

Achieving Ultra-Fast AI Chat Widgets

https://www.cjroth.com/blog/2026-02-06-chat-widgets
2•thoughtfulchris•33m ago•0 comments

Show HN: Runtime Fence – Kill switch for AI agents

https://github.com/RunTimeAdmin/ai-agent-killswitch
1•ccie14019•36m ago•1 comments

Researchers surprised by the brain benefits of cannabis usage in adults over 40

https://nypost.com/2026/02/07/health/cannabis-may-benefit-aging-brains-study-finds/
2•SirLJ•37m ago•0 comments

Peter Thiel warns the Antichrist, apocalypse linked to the 'end of modernity'

https://fortune.com/2026/02/04/peter-thiel-antichrist-greta-thunberg-end-of-modernity-billionaires/
4•randycupertino•38m ago•2 comments

USS Preble Used Helios Laser to Zap Four Drones in Expanding Testing

https://www.twz.com/sea/uss-preble-used-helios-laser-to-zap-four-drones-in-expanding-testing
3•breve•44m ago•0 comments
Open in hackernews

Ask HN: When does changing pricing models break user trust?

6•skicoachapp•2w ago
I’m curious how people here think about this.

Many apps start with a one-time purchase. Clear deal. You pay once, you own the features.

At some point, the business model changes: subscriptions are introduced, and features people already paid for disappear or become locked behind a new paywall.

I understand why subscriptions exist. Recurring revenue makes products easier to sustain.

But from a user perspective, this feels like changing the rules after the fact. Not a price increase for new users — but a retroactive change for existing ones.

I recently added GPX import to a project I work on, specifically to avoid data lock-in. The idea was simple: even if someone stops using the app, their data should remain usable elsewhere.

This raised a broader question for me:

• Is it ever acceptable to change the deal for existing users? • Where is the line between sustainable monetization and broken trust? • How do you think about “ownership” in software you paid for once?

Genuinely interested in perspectives from founders and users.

Comments

JohnFen•2w ago
> At some point, the business model changes: subscriptions are introduced, and features people already paid for disappear or become locked behind a new paywall.

If this happens, trust is immediately broken. They have taken away something I paid for. It's a kind of theft.

> Is it ever acceptable to change the deal for existing users?

Not for one-time sales. If it's an ongoing contractual arrangement, like a rental or service subscription, then it's acceptable to change the offer when the contract renews or on terms agreed to in the contract.

> Where is the line between sustainable monetization and broken trust?

There is no tension between those two things. If you make promises, don't break them and there won't be trust issues.

> How do you think about “ownership” in software you paid for once?

If I have paid for software without the terms being a rental from the start, then my expectation is that I will be able to continue to use the software forever (or as long as I have machines that can run it).

I don't expect to get free updates. If I want an updated version, I expect to pay for it. There's a gray area here about security updates, though. A good company will provide security updates at no charge, and feature updates separately for a charge.

skicoachapp•2w ago
This matches my intuition almost exactly.

Especially the distinction between: paying once to own a version vs paying for an ongoing service.

I think a lot of conflict comes from companies blurring that line after users have already built habits and trust.

The point about security updates vs feature updates is interesting too — that gray area is where many products struggle to be explicit.

JohnFen•2w ago
What I've described is also pretty much the way this worked for all software back in the day.
bobby_lea•2w ago
I see this happen so frequently, and my co-founder and I are grappling with exactly this issue. Our model will rely on subscription rev for a good portion of total rev once we are at full capacity, but we won't be there at launch. The approach we are taking now is deliberately holding back from V1 and V2 the features that we think will be the real value-ads that will entice paid memberships. That way, instead of asking people to pay for a think they previously got for free, we will be adding new features and asking people to pay if they want more - or stay on the free membership and continue doing what they are already doing.
skicoachapp•2w ago
That approach makes a lot of sense to me.

Adding new value and asking people to pay for more feels fundamentally different from taking something away and asking them to pay to get it back.

The moment users feel something was removed, the conversation shifts from value to resentment.

JohnFen•2w ago
This is the way, in my opinion.
nitwit005•2w ago
The two most prominent companies to do this were Microsoft and Adobe, but they actually still do have some one time purchase options remaining. They just stopped advertising them, and made them hard to find on their website.

MS Office: https://www.microsoft.com/en-us/microsoft-365/p/office-home-...

Adobe Elements: https://www.adobe.com/products/elements-family.html

Also, I have to be frank that both companies are trying to scam people with the subscriptions. Try a full month free, and if you forget to cancel get stuck paying for a full year. The scamming has damaged their reputation more than the actual subscription model.

skicoachapp•2w ago
That example actually highlights something important: it’s not just a technical pricing choice, it’s a perception thing.

When users feel like they were nudged into a subscription in a way that feels deceptive, that’s what really dents trust — sometimes more than the subscription itself.

It’s interesting to see how even big companies struggle with the narrative around subscription transitions.

hollow-moe•2w ago
The "old" model is the best IMO. Sell the software once with like 1 year of updates, and then the user can keep their software at an old version or can pay some amount to get the new version / another year of updates. If you wanna make it look like a subscription ask for a fixed fee first and then a small amount every month but then you don't get to keep the software on unsubscribe (or if you really want to play nice allow to keep using "old" version after defined subscription time like a year or smth)
skicoachapp•2w ago
I agree that this model has a lot going for it.

What it does really well is set expectations upfront: you’re buying a version and a defined update window, not an open-ended promise.

Where I think many products stumble is skipping that clarity and retroactively redefining what users thought they bought.

If users know from day one: “this includes X months of updates, after that you can keep using it or pay for more”, most of the trust issues simply don’t exist.

jerryjobrien•1w ago
Changing the deal retroactively breaks trust. Sustainable monetization is fine — but only when new costs map to new value. Taking away features people already paid for isn’t pricing evolution, it’s expectation debt coming due.

My rule: You can change the future. You can’t rewrite the past.

If you want to monetize long-term, protect ownership, data access, and core functionality — then charge for what truly costs you to keep running.

let me know if you can help more.