- cross-posted to:
- memes@lemmy.ml
- cross-posted to:
- memes@lemmy.ml
I believe this should work. At least some German emergency vehicles now come with filming protection.
The linked web page reads, “Attention! Rubbernecking kills!”
I’m not sure a pseudo QR code on the truck gives off the right message
I actually would really like to know, what it says and would make myself punishable by that
But I think, it looks so inviting to scan it…The way I see it there are two options:
-
You’re in a car and driving past that vehicle. If you don’t have your phone ready already, you won’t get it out in time and won’t be able to scan the code. You didn’t read the code and didn’t need to (because you weren’t rubbernecking).
-
You’re in a car with your phone already out (because you’re expecting a crash) or you’re a pedestrian who takes out their phone to film the crash site. You do read the code and you should see it, because you’re rubbernecking.
I was more thinking about not driving the car myself, but being driven as a passenger
Although it’s obviously a safety issue, when people turn away their focus to checkout a crash - no discussion about that - I was more thinking about the ethical issue of gaffing at injured people
-
Finally, we can build memetic hazards in real life
Wait until somebody actually makes brain implants!
But on the other hand, people have actively used memetic hazards for millennia. Want to star a nice, cozy witch hunt?
Ah, the Basilisk Hack.
(Nothing to do with Roko, btw.)
Getting closer to Snow Crash all the time.
I want a shirt that has a QR code that Rick rolls people.
Modern Day Medusa sounds like a cool band name
Strongly reminds me of Old MacDonald Had a Barcode, E-I-E-I CAR. Basically put a standard anti-virus test string into various sorts of barcode and see what breaks.
Is this theoretically possible?
Well, yes. You could bury code or malicious data in an image, QR or otherwise, and leverage an exploit that during processing of the visual data within the camera subsystem or inter subsystem calls could hypothetically trigger an execution path that results in a different outcome than expected, all without user permission. There is a lot of sw and hw sec controls in play at internal system boundaries and it would be very very difficult to gain privilege enough to fist fuck a phone but not impossible.
With the outstanding level of FR, NFR and Sec testing that companies perform these days it is not likely to happen. It’s not like they push out minimal viable products or something, right? /S
Might have more luck displaying the https://en.m.wikipedia.org/wiki/EURion_constellation
Wasn’t this almost the plot line of Snowcrash?
Not all Phones habe qr code detection in the camera mode
deleted by creator
Idk I use a Pixel with GrapheneOS Camera App
That’s custom software on custom firmware, which is very extraneous to the average consumer…
It’s also not a “released” phone in the sense that Google isn’t selling it in that state.
Every smartphone I’ve had does but every one of them has also asked if I want to follow the link rather than just doing it.
Most do. It’s the only reason they finally somewhat caught on after a rough start when users had to download an app in order to read the code.
I’d be flattered if someone actually wanted to film me with their phone. :(
deleted by creator
So… Everything is a meme now? Screenshots of random text posts are memes?