https://www.thenile.dev/blog/uuidv7#why-uuidv7 has some details:
"
UUID versions that are not time ordered, such as UUIDv4 (described in Section 5.4), have poor database-index locality. This means that new values created in succession are not close to each other in the index; thus, they require inserts to be performed at random locations. The resulting negative performance effects on the common structures used for this (B-tree and its variants) can be dramatic.
".
1. Users - your users table may not benefit by being ordered by created_at ( or uuid7 ) index because whether or not you need to query that data is tied to the users activity rather than when they first on-boarded.
2 Orders - The majority of your queries on recent orders or historical reporting type query which should benefit for a created_at ( or uuidv7 ) index.
Obviously the argument is then you're leaking data in the key, but my personal take is this is over stated. You might not want to tell people how old a User is, but you're pretty much always going to tell them how old an Order is.
Out of curiosity googled for Sentinel (which was one of the other dongles back then), seems somebody is now providing a bypass/emulation service: https://sentineldongle.com/
(not affiliated with this, just googled Sentinel like 5 minutes ago and this showed up).
How long until the AppleTV will look like your own in-home billboard? At least on the NVIDIA Shield you could just not install the update that changed the homescreen to incorporate ads (or install an alternative launcher). With the closed eco system of the AppleTV, the options are probably limited if/when Apple decides they need to extract more money from you by blastering ads all over the interface.
Projectivy Launcher, for Nvidia Shield Home Screen.
Before that I was building a rooted firmware and downgrading from that awful advert ridden update. I also tried Dispatch as a home screen replacement, but Projectivy wins.
Denuvo anti-tamper DRM doesn't use kernel level tricks, it's all userspace and works just fine on Linux/Proton.
It's the kernel level anti-cheats that don't work on Linux. And some user level anti cheats (like AntiCheat Expert) that only work on the Steam Deck as they check the CPU/GPU of the system and refuse to work if it's not the one in the Steam Deck (which also means those don't work on platforms like the ROG Ally).
github repo with only pre-compiled binaries coming from npmjs. These days anything from npmjs should already raise red flags, let alone something pre-compiled without sources.
Tbf the new trusted publishers goes a long way to improving this (not used by this package by the look of it). I migrated a few of my packages to it, and now:
- publishing with an API token is forbidden, must use the specified workflow w/ OIDC auth
- an explicit approval step in GitHub is required to run the publish workflow (you can also set a time delay, similar to time release safes)
Bro the source is locked and precompiled no body even the author cannot edit with malicious binaries. Thats y people used to publish binary to ensure stability. Instead of pulling from git each time.
Also mentioned on HN https://news.ycombinator.com/item?id=45323008
reply