it does not upload audio clips unless you opt in during the first use of assistant
well, and text will obviously get sent if assistant activation results in a google search, pretty sure actions like setting a timer run fully locally without any feedback to google (except general anonymous analytics data which is not that “scary”)
well it’s an improvement…
basically the tracking is still there but runs locally on your phone, so google only knows this
someone with ip 1.2.3.4 is interested in sports, cats and videogames and is looking to purchase a new monitor
(and the info is sent with every ad request, statelessly) google promises they won’t associate these requests with ip addresses, but I won’t trust them.
instead of a full log like:
user x with tracking id 12345 visited catworld.com at 10:34:56 PM and stayed there for 35 seconds
user x with tracking id 12345 made a purchase on website shoptech.com and was scrolling through the monitors page for 10 minutes.
it’s still tracking but it sucks less i guess…
and making it a default is probably a great move
(I’d rather opt out of any form of tracking tho)
i use sync. there’s nothing even close to the quality of the client. (The onlt client that implements material you in a fun and usable way, sync is usable one-handed)
I had been using Liftoff for a while (before switching to Sync as soon as it came out), which i quite liked but it feels a lot worse than sync
web env. integrity is not as bad as people make it out to be.
yeah I absolutely agree that it’s terrible and also a bad idea (we don’t need MORE drm in our browsers, I’m looking at you, Widevine (although firefox worked around it by running drm in an isolated container)), but it’s main purpose is to detect automated requests and effectively block web scraping with a drm system (it ensures two things: your useragent can be trusted and you’re a real non-automated user), NOT detect ad blockers. It doesn’t prevent web pages from being modified like some people are saying.
there’s a lot of misleading information about the api as it doesn’t “verify integrity” of the web page/DOM itself.
it works by creating a token that a server can verify, for example when a user creates a new post. If the token is invalid, server may reject your attempt to do an action you’re trying to perform. (this will probably just lead to a forced captcha in browsers that don’t support it…)
Also, here’s a solution: Just don’t use Chrome or any Chromium-based browsers.
you misunderstood it tbh.
it’s supposed to be used as a way to skip bot verification if the requests are signed by a drm system which includes your unique id (coming from google account or google play id), and one of the goals of the actual proposal is keeping existing extension working AND keeping web pages working without drm.
of course i don’t want any drm in my browser, but it’s kinda already there anyway…
it will likely make the experience worse for non-drm users because they will get hit by more advanced and sensitive bot verification systems or rate limits which is kinda bad but not the end of the world.
y’all are just overreacting and spreading pure bullshit.
it’s not even supposed to be used to verify DOM elements, just that the user is using an official Chrome/Chromium browser, and is not automated.
basically it’s just SafetyNet.
it will not kill js addons.
they don’t offer reasonable free tiers (I don’t have a reliable source of income and i just need it for hobby stuff) and I’m unable to sign up with either of those with my ukrainian credit card anyway (they all reject both my credit and debit cards)
well i haven’t tried signing up for azure yet but I don’t have much hope
also I don’t care about it’s cdn features, i need a dns server and a way to proxy ipv4 traffic over ipv6 (and cloudflare tunnels for ssh)