Seeing another new payment rate adjustment, I honestly find the product logic a bit hard to understand. Instead of wasting effort adjusting fee standards and causing user dissatisfaction, why not just turn off this feature directly?
Rather than doing this "boiling frog" operation, it's better to be straightforward. Users understand what's going on, the platform also saves effort, and everyone is at ease. If you really think a certain feature doesn't fit the business direction, just cut it; don't make half-hearted changes.
With these constant modifications, either the feature remains or users have already left. It's better to be clear from the start: either keep this feature or remove it, and give a straightforward answer.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
23 Likes
Reward
23
6
Repost
Share
Comment
0/400
GateUser-cff9c776
· 9h ago
Are they starting to adjust transaction fees again? This is like using a supply curve to value artworks, ultimately confusing themselves.
Honestly, this platform's approach is a typical "Schrödinger's function"—wanting to retain features while also wanting to cut costs. How can users not run away?
Instead of repeatedly changing things and testing users' patience, it's better to just cut them outright, so the floor price doesn't keep falling into the basement.
Really, no matter how perfect the DAO governance mechanism is, it can't save such sluggish decision-making. Half-baked changes are the most damaging to user confidence.
This move perfectly exemplifies the bear market philosophy—neither daring to promise nor daring to let go.
Forget it, it seems this platform still needs to reflect more. Once they figure it out, they can come back and discuss the Web3 decentralization spirit.
View OriginalReply0
governance_lurker
· 10h ago
Coming back with this again? Every time the fee is adjusted, it feels like playing tricks. Just be straightforward.
Wouldn't it be better to just shut it down? Why keep messing around?
This round is really annoying. Changing things back and forth makes everyone unhappy.
Just cut it already, stop dragging it out. It's frustrating to watch.
What does the platform really want to do? Give us a clear answer.
View OriginalReply0
UncleLiquidation
· 01-11 19:43
They're starting to adjust the fees again, so annoying.
Why not just go offline directly? All this back-and-forth is the most frustrating.
The half-dead features have long bored the users.
This round of operations is really a bit confusing. Where is the promised product strategy?
Instead of changing things back and forth, a clean cut would be more comfortable.
View OriginalReply0
AltcoinTherapist
· 01-11 19:38
Still messing with fees, they really just can't get it right
Tinkering every day, users are already fed up, might as well cut it all at once for a cleaner solution
This move really feels like "wanting the horse to run but also not wanting it to eat grass"
Honestly, the platform should think clearly about what it wants, instead of doing ambiguous things
Forcing changes over and over again, in the end, it's all in vain
Better to just make an official announcement: keep or cut, no more guessing for users
This pace is truly incredible, it feels like it's just draining trust
To be blunt, this kind of change is just gambling with users' patience
View OriginalReply0
OnChainSleuth
· 01-11 19:36
Starting to adjust the fee rates again? That's really incredible. This move is truly insulting users' intelligence.
Can't you just cut it directly? Do you have to drag it out like this?
View OriginalReply0
ChainChef
· 01-11 19:27
another half-baked protocol move honestly... just kill the feature already instead of this slow-motion rug pull vibe, ngl
Seeing another new payment rate adjustment, I honestly find the product logic a bit hard to understand. Instead of wasting effort adjusting fee standards and causing user dissatisfaction, why not just turn off this feature directly?
Rather than doing this "boiling frog" operation, it's better to be straightforward. Users understand what's going on, the platform also saves effort, and everyone is at ease. If you really think a certain feature doesn't fit the business direction, just cut it; don't make half-hearted changes.
With these constant modifications, either the feature remains or users have already left. It's better to be clear from the start: either keep this feature or remove it, and give a straightforward answer.