Technology

74180 readers

3581 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago

MODERATORS

L3s@lemmy.world

enu@lemmy.world

technopagan@lemmy.world

L4s@lemmy.world

L3s@hackingne.ws

L4s@hackingne.ws

452

HP fails to derail claims that it bricks scanners on multifunction printers when ink runs low (abcnews.go.com)

submitted 2 years ago by L4s@lemmy.world to c/technology@lemmy.world

34 comments fedilink hide all child comments

HP fails to derail claims that it bricks scanners on multifunction printers when ink runs low::HP Inc. has failed to shunt aside claims in a lawsuit that it disables scanners and other functions on its multifunction printers whenever the ink runs low

you are viewing a single comment's thread
view the rest of the comments

[–] hoot@lemmy.ca 102 points 2 years ago (13 children)

Do people not know what "bricking" means? This article is about HP disabling features if the printer runs out of ink.

If they bricked it, it would be unrecoverably broken, never to function again.

[–] mwguy 73 points 2 years ago (4 children)

A more accurate term would be that they ransom the functionality of the product they sold until you pay the ransom.

[–] fubo@lemmy.world 20 points 2 years ago* (last edited 2 years ago) (3 children)

Or maybe they engineered a "multifunction" device with shitty error handling: if any subsystem has an error, all functions fail, even those that don't depend on that subsystem.

A junior engineer filed a bug report about it and submitted a patch that allows subsystem errors to gray-out only certain functions in the UI.

The PM didn't consider the bug launch-critical enough to merit an engineer's time to review the patch. One senior engineer did briefly look at the patch and said "sorry, we can't alter the UI without brand & design review, i18n, and a lot of shit you don't wanna do."

The system shipped with the bug intact. The PM was rewarded for launching the product on time, and got promoted into a different position.

A year later when the users start fussing, the people on the team say "we never heard of that problem."

(This is hypothetical. Tech companies do be like that sometimes though.)

[–] SlopppyEngineer@discuss.tchncs.de 13 points 2 years ago

And if this was in the first version, everybody would understand. If it's still in version 5, it's by design.

load more comments (2 replies)

load more comments (10 replies)