this post was submitted on 23 Apr 2025
2 points (100.0% liked)

[Moved to !iiiiiiitttttttttttt@programming.dev, check pinned post.] iiiiiiitttttttttttt.

893 readers
1 users here now

you know the computer thing is it plugged in?

Moved to !iiiiiiitttttttttttt@programming.dev.

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] ironhydroxide@sh.itjust.works 2 points 2 years ago* (last edited 2 years ago) (3 children)

I get someone made a hilarious mistake.

But why would you not even test the code before gluing them to all the tables?

Or before sending the code to be etched?

[–] HexadecimalSky@lemmy.world 2 points 2 years ago (1 children)

I think since its not so much btoken as pointing to a local file, I think they may have tested it on the one device they made it, so it worked...on that device.

They should have 100% tested it on other devices

[–] ironhydroxide@sh.itjust.works 1 points 2 years ago

Guess I'm showing my age then. Because the intended end use device is obviously a phone, I assume they used their phone to generate the qr, send it out to etch, and test the result. I can't use my phone for shit like that. To me that is much more a real screen type of job (generating the qr code, generating the gcode in lightburn, etc) done on a computer, instead of a tablet/phone

[–] Harrk@lemmy.world 1 points 2 years ago

I created a QR generator website and you have no idea. I get emails from people saying they’ve printed the codes before discovering it goes to the wrong place (sometimes even to my own site!) and if I can fix it. No... check your codes before they go to print!

The funniest one I had caused me to get a huge spike of traffic on Christmas. It was so weird and left me clueless for weeks, until I got an email from somebody wishing to cancel a subscription.

I don’t sell subscriptions or anything at all!

Turns out somebody printed a QR code into a smartwatch instruction booklet that went straight to my site… The ad revenue was insane tho!

[–] rustydrd@sh.itjust.works 1 points 2 years ago

Might have been a temporary link (e.g., shortened URL) that passed tests initially but stopped working later on.