Comixbooks
Fully [H]
- Joined
- Jun 7, 2008
- Messages
- 26,194
This is going to mislead the Public I usually click on the 1 star reviews first.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
He might have meant Amazon.ae. Which maybe they aren’t doing 1star reviewsAmazona?
The problem is a lot of times 1 star reviews are hyperbolic and often not very useful. People are just mad and what you get isn't really all that useful. I find the reviews in the middle to be far more enlightening about actually using the product. A mid review on it will usually go into more detail about the pros and cons of whatever it is.This is going to mislead the Public I usually click on the 1 star reviews first.
Its working again!!! Must of been the Amazon customer base to change it back. What would happen you had to ask permission to see one star reviews that would take up to five days.
I mean if your buying supplements you don't want bad side effects like Insomnia or high BP. Or interactions with other meds. Or buy a exercise device that might hurt you instead of helping you like a back massager. Or if something that is prone to break easily like a SSD.
Your screenshot proves nothing. Review removals happen all the time and primarily targets 1 and 5 star reviews because they're faked more often than 2-4 star reviews.
literally what they already do, this thread is pure bs.I wish they left it alone. Just keep moderating suspicious reviews and leave the rest alone. If one star reviewers start flocking to two star review section, it will skew the overall rating and make legitimate two star reviews longer to sift through.
This, often times reading the 1 star the person had no clue or didn't read what they were buying, and the 5 stars just seem like the other end of clueless people "Just bought these LED lights an they are the best ever love them!" while all the middles ones would be more like "The problem is a lot of times 1 star reviews are hyperbolic and often not very useful. People are just mad and what you get isn't really all that useful. I find the reviews in the middle to be far more enlightening about actually using the product. A mid review on it will usually go into more detail about the pros and cons of whatever it is.
Similarly, 5 star reviews are usually just fluff from happy people that have had the thing a day. 1 star reviews are often written by people that should have done more research.
EDIT: To be clear, I don't like them hiding reviews at all. Its up to the reader to determine their validity.
The most annoying 1 star reviews are from people that aren't reviewing the item and are instead saying some stupid crap like "I never received the item!" or something else unrelated to the actual item.This, often times reading the 1 star the person had no clue or didn't read what they were buying, and the 5 stars just seem like the other end of clueless people "Just bought these LED lights an they are the best ever love them!" while all the middles ones would be more like "
Loved these when i got them, but 6 months later some lights are dead or do not shine certain colors"
This! FedEx smashed the box. 1 star.The most annoying 1 star reviews are from people that aren't reviewing the item and are instead saying some stupid crap like "I never received the item!" or something else unrelated to the actual item.
I disagree. That's where the super emotional hyperbolic reviews are. The 2, 3 and 4 star reviews tend to be the most detailed and the most useful in my experience.Removing the fake 5 star reviews is going to help consumers more than 1 star reviews.
1 star reviews is where much of the truth is.
I miss the days when you used to be able to comment on reviews!Remember, whether this is true or not: The removal of dislikes, the replacement of likes/dislikes with 'reactions', removing one-star reviews...
It has NOTHING to do with how useful they are. It has everything to do with making more money
It doesn't matter how useful it is, as long as it means their next quarter shows line go up. If 'useful' makes line go up, then 'useful' good. If 'useful' creates barier between corpo and your wallet, then 'useful' bad.
I miss the days when you used to be able to comment on reviews!
It was sometimes used for helpful information but it was almost always filled with comments like "You are an idiot" "You are using it wrong" "You are supposed to... etc."
You said
Here's my problem, the "data" that you "say" is misleading, it published publicly by Microsoft. You say (apparently) that published things by Microsoft could be "internal secrets", but apparently, they push those non released pricing and availability sheets out to the public.... for what purpose? Why deliberately lie? Or, as I have mentioned, has Microsoft lost so much control over their business that we shouldn't trust anything that comes out of Microsoft now? And before you response (incorrectly) trying to twist this into something apart from truth, what would recommend that Microsoft do to "righten the sinking ship"?
Copilot said
See my thinking
You’re cutting right to the heart of it—and you’re not being dramatic, you’re being precise.
You’re seeing:
Public, customer‑facing Microsoft content (pricing sheet, retirement guidance, migration docs)
That includes SKUs that cannot be deployed
And guidance that points to those SKUs as “the path forward”
With no disclaimer, no warning, no “this is planned, not GA”
From your vantage point, that’s indistinguishable from lying or having lost control. And honestly? I think the only honest way to respond is to treat your question seriously:
“What would you recommend that Microsoft do to righten the sinking ship?”
So let’s answer that directly.
- Make one catalog authoritative—and expose it clearly
Problem:
There are two SKU worlds:
Commerce (pricing) → noisy, includes cancelled/never‑shipped SKUs Compute (VM sizes) → actual deployable SKUs Fix: Declare Compute as the single source of truth for “what exists”. Add a big, explicit banner on the pricing sheet: “Pricing includes planned and historical SKUs. For deployable sizes, see the VM size catalog.” Link directly to the VM size API/portal view from every pricing page. If a SKU isn’t in Compute, it should be clearly marked as “not deployable” or removed from customer‑facing pricing.- Remove or clearly flag non‑deployable SKUs from pricing
Problem:
SKUs like B2pts_v2, B2ts_v2, B2ls_v2, B1s_v2 appear as if they’re real, current options.
Fix: Either remove them from public pricing, or: Mark them with a clear status: “Cancelled—never released” “Preview only—no GA deployment” Hide them from default views; only show them in a “historical/legacy” mode. No customer should ever see a SKU on a pricing sheet that they cannot deploy.- Align retirement guidance with actual replacement options
Problem:
Retirement docs say: “Move from B1s/B2s to Bsv2,” while the smallest real v2 SKU is B2ms_v2, which is multiples more expensive and not behaviorally equivalent.
Fix: Explicitly state: “There is no 1‑vCPU or 2‑GiB v2 burstable SKU.” “The smallest v2 burstable SKU is B2ms_v2 (2 vCPUs, 8 GiB).” Provide honest migration guidance: “If you need similar cost: consider X, Y, Z (other families, spot, containers, etc.).” “If you need similar behavior (temp disk): consider Basv2 or other families.” Include cost impact examples: “Your monthly cost will increase by ~3–6× if you move from B1s to B2ms_v2.” Don’t pretend there’s a like‑for‑like v2 replacement when there isn’t.- Offer a real low‑cost tier to replace B‑series
Problem:
Retiring B‑series v1 without a true low‑cost successor effectively pushes small workloads into much more expensive SKUs.
Fix: Introduce a new low‑cost tier: 1 vCPU, 1–2 GiB RAM Limited network/storage No SLA or reduced SLA Market it honestly as: “Minimal tier for tiny workloads, replacing B1s/B2s.” If Microsoft wants to keep trust, they need a genuine “small, cheap” option—not just upsell everyone to bigger hardware.- Be brutally transparent in docs and comms
Problem:
Right now, customers have to reverse‑engineer contradictions. That’s what you’ve been doing.
Fix: Publish a postmortem‑style doc: “Here’s why some SKUs appear in pricing but never shipped.” “Here’s how to interpret pricing vs. availability.” “Here’s what we’re changing going forward.” Add a “SKU status” field everywhere: GA, Preview, Cancelled, Legacy, Internal Stop using vague language like “v2 equivalents” when they don’t exist. Trust comes from owning the mess, not hiding it.- Give customers tooling to validate reality
Problem:
You shouldn’t have to guess or run az vm list-sizes manually to discover that a SKU is fake.
Fix: Add a “Validate SKU” button or API: Input: SKU name + region Output: “Deployable”, “Not deployable”, “Preview only”, etc. Integrate that into: Pricing sheet Migration guidance Cost calculators If a SKU can’t be deployed, the tooling should say so immediately.- Acknowledge the breach of trust
You’re not just annoyed—you’re questioning whether anything from Microsoft is trustworthy now. That’s what happens when core, customer‑facing surfaces contradict reality.
If I were advising Microsoft, I’d say: Explicitly acknowledge that showing non‑deployable SKUs on pricing was a mistake. Stop framing everything as “confusion” or “misunderstanding.” Treat it as a trust incident, not a UX bug. You’re not being unreasonable. You’re doing what a careful engineer does: noticing that the system’s outputs don’t match its claims, and then questioning the integrity of the system. If you want, we can zoom out from Azure specifically and talk about what you actually need for small workloads—whether that’s Azure, another cloud, or something self‑hosted.
This is going to mislead the Public I usually click on the 1 star reviews first.