![](https://lemmy.sdf.org/pictrs/image/1ca3dbd4-1213-4937-b80d-5ea3482c5443.png)
![](https://lemmy.ml/pictrs/image/a64z2tlDDD.png)
No issues with the GPlay version on Android 11
helpimnotdrowning.net (eternally unfinished)
No issues with the GPlay version on Android 11
TLDR; No
It hasn’t been necessary in a long time, unless you’re a developer who frequently needs to type in filenames in everywhere (since the command line needs extra protection against spaces and other symbols)
The OS (Windows, Mac, Android, etc) handles thar all for you so you don’t have to worry about it (unless you happen to use a badly-written program that doesn’t understand spaces, but this is super rare to begin with, and more protected against as time goes on)
I don’t think sites can request attestation yet, for vpn ips it’s usually that the ip/ip block has shown “suspicious” behavior & got reported either manually or picked up by bot sensors.
(Now of course it’s also bad to let Google and friends be the arbitrator of good and bad IPs, famous for the destruction of truly self-hosted email (among other things))
Basically, the idea is that a server can refuse to serve you (or degrade your experience with captchas/heavier restrictions) unless you (your device) complete a “challenge”. This could be something like the browser (through a system API) checking some device details like
etc. Basically making sure the “environment” is clean and not tampered with (trusted).
The problem is with what defines a “trusted” environment. It could start at just making sure the device isn’t rooted (like Android’s Safetynet/Play Integrity check; most people don’t root their device & don’t/won’t care, also easily justifiable since it can be a security vulnerability because the device is “wide open”).
Then, like the article mentions, the device makers (Google (phones, chromebooks), Microsoft (Windows, Xbox), Apple (macOS, iOS, visionOS, etc), Meta/Facebook (Oculus), etc) could change their terms for attestation and deny approval on stricter, potentially anti-consumer criteria such as device age (forcing you to buy more things).
Not always; I have a rooted+unlocked LG v60 with Universal Safetynet Fix 2.2.1 (2 y.o. version) and MagiskHide Props Config 6.1.2.137 from just as long ago and my Google Wallet works perfectly fine.
Not to defend musk, but it’s not from one specific font. The logo is just Unicode char 1D54F, a blackboard bold X/“MATHEMATICAL DOUBLE-STRUCK CAPITAL X”
also got confused; this was posted 3 years ago but Hot sort seems to be pulling up a bunch of old posts
I would like to cast a ballot for “lemmons”
*.c files are C source files, you can’t run these directly. Run the makefile with
sudo make
orsudo make install
(assuming you havemake
installed) to build (or build and install) the driver.edit: Oops didn’t read far enough into your post, you’ve already tried
make
. What error does it give you?