3,953 karma · joined October 25, 2009
Software developer living in Tokyo, Japan
Previous: Oozou (BKK), Omise (BKK→TYO), Varnish Software (TYO), EnergyRoute Japan (TYO)
I run a small IT consulting business in Japan; feel free to email.
Masking six digits out of sixteen digits is a very common practice in the industry. The first 6 is BIN which is sort-of public data (full BIN table are distributed by Visa/Master only to acquirer/issuer, but some acquirer may provide them for free to a payment processor/merchant), next 6 is not unique enough since it depends on issuer's scheme so last 4 is used for identifying a card with the middle 6 masked.
I don't know about this particular case (and it depends on QSA), but if the number is in any way reversible e.g. a plain hash(card_number), it would put any system that store that hash in a PCI-DSS storage scope. I once worked with a system that solve this issue by having unique salt to each card, but the salt is never exposed outside of PCI-DSS scope. This prevent rainbow table attack, but still open to brute force.
3-D Secure was suppose provide a better security for online transactions by requiring a second factor (e.g. OTP), but it introduces a lot of hassle since it rely on HTTP POST from a client's browser (thus the "Your payment is being processed. Please do not refresh this page." screen), add two extra vendors to trust (ACS/MPI), and the card is still usable with merchants that doesn't enforce 3-D Secure (though I'm not sure if this is the case with India), making the whole scheme similar to having a tightly locked door with a window open wide. The scheme protects merchant more due to liability shift which removes them from being liable to chargebacks.
3-D Secure 2.0 tries to fix the hassle part by requiring merchant and payment processor to send data about the transaction back to the bank (email address, previous transaction info, shipping address, etc. which may be a privacy issue) and letting them decide whether a transaction should require an extra authentication.
Godot has been working well for me under Rosetta (though just a small 2D project using GDScript). Godot 3.2.3 actually supports Apple Silicon[1] although there's no binary build just yet. I've recently submit a patch to MacPorts to enable native Apple Silicon[2] and have been using it since without any issues (so far).
[1]: https://docs.godotengine.org/en/stable/development/compiling...
Timeline:
Sep 19, 2012 - iOS 6
Dec 13, 2012 - Google Maps launched on App Store
I tried running Nextcloud on Raspberry Pi 4 (4GB) a while ago, and hitting performance issue on SD card very fast (initial DB import take very long). I tried to solve this by moving all Nextcloud data into iSCSI disk but RAM & CPU became a problem once I started adding more files. After a week or so, I tore everything down and went back to a VPS instance.
It might works better with Raspberry Pi cluster on Kubernetes, though. (This very Raspberry Pi is now happily running as a DVB streaming server.)
Edit: most -> many
This limitation prevent the model with traditional adblocker where extension and block lists are independently maintained by different parties (e.g. uBlock Origin/ABP + EasyList) so you're stuck with relying on extension maintainer to update their list or download another blocker app when the blocker become unmaintained (where in traditional model you could just subscribe to another list)
(5) Docker Image (amd64)
^
|
(4) QEMU Binfmt (arm64 <-> amd64 binary emulation layer)
^
|
(3) Linux VM (arm64)
^
|
(2) Hypervisor.framework (arm64, macOS native virtualization framework)
^
|
(1) Docker for Mac
Linux Kernel has a feature to allow using a wrapper to execute userspace program based on file header (binfmt[1]). In this case, Linux VM in (3) has QEMU user mode emulation registered as binfmt, so any amd64 binaries are automatically wrapped into `qemu-x86_64-static /path/to/bin` and run. Docker Image itself doesn't run a Linux kernel but use one from the VM host, so this scenario is possible.This is also how multiarch[2] works (for amd64 to arm64/ppc64le/etc.) which might even be what Docker is using. In case of multiarch, the qemu-*-static binary is provided as a container running in privileged mode.
[1]: https://www.kernel.org/doc/html/latest/admin-guide/binfmt-mi...
My guess is this is similar to enemy sniper sometimes can see you through walls. If they're close enough to a wall, then their line of sight is calculated as if they were in front of a wall.
I wasn't even looking for them, but they managed to find me. I still enjoy the game a lot, but combat has been nothing but frustration.
[1]: https://www.polygon.com/2020/12/10/22167436/cyberpunk-2077-w...
[2]: https://www.reddit.com/r/cyberpunkgame/comments/kbwpps/retic...
That being said, I still use AirPods Pro a lot more than both HD800 and HD650 due to convenience of using it even though the sound quality is way worse. Fidelity isn't really much of a concern when I'm doing something else with background music.
I'm very excited about AirPods Max.
> When we used to manufacture TVs, we'd produce them for customers in the southern hemisphere too. When building these, we had to run them through our production lines upside down.
> When the old cathode ray tube TVs were built, the earth's magnetic field was taken into account during the production process. This ensured the current flowed the right way through the TV and so the TV was able to function normally.
[1]: https://twitter.com/SonyUKTEC/status/1228239522166501376
The monitor that are comparable to the Pro XDR Display are ASUS PA32UCX ($4500) or EIZO CG319X ($6000) which usually requires full recalibration every certain amount of usage.
[1]: https://images.anandtech.com/doci/16214/Zen3_arch_5.jpg
Most experiment with 8GB M1 Macs I've seen so far (on YouTube) seems to start slowing down once the data cannot fit in a RAM, although the rest of the system remain responsive e.g. 8K RED RAW editing test. In the same test with 4K RED RAW there were some shuttering on the first playback but subsequent playback were smooth, which I guessed it was a result of swap being moved back into a RAM.
My guess would be they've done a lot of optimization on swap, making swapping less of an performance penalty (as ridiculous as it sounds, I guess they could even use Neural Engine to determine what should be put back into RAM at any given moment to maximize responsiveness.)
macOS has been doing memory compression since Mavericks using WKdm algorithm, but they also support Hybrid Mode[1] on ARM/ARM64 using both WKdm and a variant of LZ4 for quite some time (WKdm compress much faster than LZ4). I wouldn't be too surprised if M1 has some optimization for LZ4. So far I haven't seen anybody tested it.
It might be interesting to test M1 Macs with vm_compressor=2 (compression with no swap) or vm_compressor=8 (no compression, no swap)[2] and see how it runs. I'm not sure if there's a way to change bootargs on M1 Macs, though.
[1]: https://github.com/apple/darwin-xnu/blob/a449c6a3b8014d9406c...
[2]: https://github.com/apple/darwin-xnu/blob/a449c6a3b8014d9406c...
This can be quite tricky since Xwayland's DPI may not always equal to `display DPI * Wayland scale` and while DPI settings in X is global, scale settings in Wayland is per-output. GNOME for instance has HiDPI working for both Xwayland and Wayland windows but with lots of magic going on with the framebuffer. HiDPI for X window in Plasma is still in the works AFAIK.
(This is a blocker for me as well.)
(Meanwhile Nvidia also removed the "error 43" limitation when it detected the card is being run in a VM, so VFIO scene is getting a lot more interesting in this generation.)
...until you start messing with fluid system and oil cracking
https://www.anandtech.com/show/16226/apple-silicon-m1-a14-de...