In a place where recording audio requires consent from all parties, I don't think it matters whether "all the processing is on-device" given that the law was probably written with tape recorders in mind. If I buy a device that can record audio, and place it in my home where unsuspecting guests are recorded by it, whether that recording is transmitted to the manufacturer or stays within my home seems irrelevant.
On the one hand, I wouldn't expect too many variations here (the vast majority of devices probably use 48 kHz and 24-bit output, a few use 44.1 kHz and/or 16-bit, etc.) but just like DPR and all the other properties with a very small set of popular values in practice, you only need a bit or two from each measurement to eventually have a high quality fingerprint.
This is a huge stretch, but if this problem exists in not only the PC versions of Chrome/Firefox but also the Android/iOS versions, then theoretically the app store reviewers could flag the browsers for facilitating this behavior against app store guidelines. In practice, apps of such caliber as popular browsers might be a bit above such reviewers' pay grade, so to speak.
This is nonsense. Safari also supports Web Audio. Safari does not, however, support Microsoft Windows, which is why the article author didn't mention it.
Moreover, all web browsers on iOS have to use Apple WebKit, so Web Audio support is not actually the fault of the non-Apple browser vendors.
Does anyone else get tripped up by the word "avoid" being positioned to apply to each item in the series, but then logically it must only apply to some (the first and second out of 3) items?
No, I've never seen Google Photos reflected in any Google Drive interface (web, OS integration, etc.) which on the one hand makes sense (think of Google Photos more like a database-driven black box app than a hierarchical filesystem) but on the other hand Google Drive does show gdocs, gsheets, etc. (which is also sort of a black box app, as the "files" seen in GDrive are merely lightweight stubs).
Only in storage quota views do Photos and Drive (and Gmail, etc.) commingle.
> the web applications like Google Photos are annoying but they take away all of this
They minimize it but don't take it away. A content creator must personally place their creation into multiple storage solutions, regardless of whether those solutions are cloud apps or local disks or anything else. In a world where disk failure is the only failure mode, sure, you can outsource the work of disk redundancy to a company, but it's not. The person you outsource to could decide to deny you access! Losing your cloud account (credential theft, alleged ToS violation, bankruptcy, etc.) is also a very real failure mode, albeit far less frequent than disk issues I suppose.
Perhaps the bad behavior is failure to remove a compromised (botnet) device on your network that has been attacking one or more sites that use a popular security solution.
"Broken link" is not an accurate way to describe this situation.
- Censorship bypass tools triggering destination server's firewall (suspicious TLS fingerprint or connection characteristics, or bad proxy IP)
- Bad ISP (e.g. one ISP IP address or range of addresses shared by so many users that could create collateral damage if one or more user gone rogue)
- Actual botnet/hidden residential proxy exit node on the same IP/local network (e.g. TV boxes or SDKs embedded inside apps that users are not aware of)
- Strict privacy settings (unlikely to cause 403 straight away), or obscure browsers (also unlikely, but can trigger firewall because of connection fingerprint/characteristics)
Your 4th hypothesis is equivalent, not "other," to mine. But I agree that it could be anything you mentioned, as all of them have crossed my mind as possible reasons why I experience "verifying you are human" and "find the motorcycles / busses / traffic lights" more often on my residential ISP than on my cellular or work ISPs, and the unknown botnet/exit node seems most probable (by far) when considering my own traffic. I never have the 403 problem discussed here, luckily.
When the Pandora music service launched, I remember reading about how it worked (predicting what you might like next) and it explained how they don't need to know anything about the songs at all (such as genre, tempo, instrumentation, place of origin, year of release, language, etc.) to predict what else you'll like. They simply identify other users with a similar history to you, and deliver to you some of the stuff that those other users had listened to that you hadn't listened to yet. If you abandon a song (suggesting that you don't like it much) then you become a bit less associated with the users who play that song a lot.
I don’t think that works well for movies and tv shows because there is way less datapoints than music (they are way longer, meaning we don’t consume that many films/episodes). A song is also generally more focused, you generally have one tempo, level of energy, and limited instruments. A move on the other hand is a mix of so many art forms. If you only rely on what your cohort voted for you’re missing so much information to make an actual good recommendation.
Netflix system seems to work for their goal, which is to increase revenue, but it’s not a great system for the user satisfaction
reply