• 44 Posts
  • 2.76K Comments
Joined 2 年前
cake
Cake day: 2023年8月4日

help-circle
  • So we write a JS library that you can pull in with your favorite client-side JS package manager that pretends to do ID and face scanning, but just green-lights everything. It tells the user “ok, look at your screen and 3… 2… 1… ok, we got your face scan now hold your ID up to the screen and 3… 2… 1… yup, you’re 100% over 18 all right, yessirree.” And we only admit it’s not actually doing shit in the fine fine print. And anyone can lock their content behind that and if the state of Mississippi or whoever comes after the website admin, the website has plausible deniability. “It’s whaaaaaat? I was scammed? Really? It doesn’t actually verify? Oh, well, I’m so very sorry Mr. state prosecutor sir, I never realized. I’ll get that fixed right up. Wouldn’t want innocent seventeen-and-a-half-year-olds exposed to any mention of… whispers: nudity.”






  • It’s usually not terribly noticeable except on certain games (I think Celest was one example I heard) or if you’re speedrunning (which was why it bothered me so much specifically). Basically, pressing one of the D-pad buttons can often register a different D-pad input even if the operator of the controller presses in exactly the correct part of the D-pad.

    The way the D-pad is constructed is that the part your finger makes contact with is a plastic piece that pivots about a “post” and when you tip it one direction or another far enough, it presses on a pressure pad on the controller’s motherboard. The problem is just that the “post” is about… maybe half a millimeter shorter than it ought to be, so it pivots a little less than it should and pancakes a little more than it should, resulting in the wrong pressure pad being hit.

    That’s already way ore info than you asked for. Lol. But if you want even more info, this YouTube video has a simple fix and this 3D-printable part on Thingiverse is about a more sophisticated fix. I’ve tried both and can confirm the latter is a little bit better in my experience. The former fixed the misinput issue, but made D-pad down a bit less responsive. The latter, I have no complaints about.