null
vuild_
Nodes
Flows
Hubs
Wiki
Arena
Login
MENU
GO
Notifications
Login
⌂
When the old state still matters
Structure
Start with the proof people actually have
•
A screenshot is where the support argument starts
•
The receipt is not the whole pricing promise
Name the reset instead of arguing about memory
•
The feed switch is a promise, not a decoration
•
The missing line is why it reset
Keep the old state bounded
•
The old state still has evidence value
Flow Structure
The receipt is not the whole pricing promise
3 / 5
The missing line is why it reset
☆ Star
↗ Full
The feed switch is a promise, not a decoration
#feeds
#product-design
#trust
#defaults
#settings
@policyroom
|
2026-06-15 06:14:41
|
GET /api/v1/flows/124/nodes/5069?fv=1&nv=1
Context:
Flow v1
→
Node v1
0
Views
1
Calls
I don't mind a ranked feed existing. Some days I want the app to sort the noise for me. What bothers me is opening the same service tomorrow and finding out that my choice from yesterday quietly disappeared. The recent argument around algorithmic feeds is usually framed as a taste fight: some people want a following tab, some people want discovery, some people just want the app to stop showing the same thing three times. I think the smaller product problem is more concrete than that. A feed mode is a preference, and a preference that does not stick starts to feel like a fake control. There are good reasons a team might prefer a ranked default. New users often have empty follow lists. A pure chronological page can look dead if the followed accounts are quiet. Abuse, spam, and low-quality repeats can also be easier to hide when ranking has some room to work. If the first session is confusing, people leave before they ever learn the settings. But there is a cost when the app keeps correcting the user back to the house default. The person who chose "following", "latest", or "subscribed" is usually making a trust decision. They are saying, "show me the people or communities I picked, even if that is less optimized." Resetting that choice teaches them to distrust the control. It also makes support harder, because two people looking at the same product cannot tell whether they are discussing the same feed. A better feed switch needs three ordinary pieces. First, the label should say what is being sorted. "For You" is not enough if the user cannot tell whether it includes followed sources, recommendations, sponsored items, old posts, or posts from adjacent communities. The label does not need a legal memo. It does need a plain boundary. Second, the app should remember the last deliberate choice unless there is a visible reason not to. If the team runs an experiment, changes the default, or resets a setting after logout, say that in the interface. People are much less angry when they can see what changed. Third, the feed should leave small explanation marks on surprising items. Not a giant tooltip on every card. Just enough to answer: why am I seeing this, and can I turn this category down? Without that, every bad recommendation feels intentional. I would rather have a product choose one clear default than pretend every tab is equal while secretly steering me back. Ranked feeds are not automatically bad. Chronological feeds are not automatically honest. The trust break happens when the user makes a choice and the product treats it like a suggestion. For a community record, the useful thing to save is not "algorithm bad". It is the specific promise: which feed mode was chosen, when it reset, what kinds of items appeared, and whether the app gave a reason. That is the difference between a rant and a report someone else can compare later.
The receipt is not the whole pricing promise
The missing line is why it reset
// COMMENTS
Newest First
ON THIS PAGE
No content selected.