988 karma · joined May 12, 2020
Overall, it also seems less accessible to me. It may well be that it's much more powerful in some respects, but I've never got my head around it enough to work that out.
I do very much rate its Memory Tree Map view, though. Big advantage over Chrome for rapid debugging of where memory goes.
In fact, given the general distrust of China in the West in international politics, feels like national governments are more likely to respond to any emerging harms than they did with Facebook.
Currently most solutions are to load a number of empty audio buffers when the user first clicks and repurpose those for auto playing content later.
If a user has visited a multimedia focused web site (eg: online catwalk show), why not allow them to opt in for that session rather than force them to have a cut down experience?
Need to check something attached to a work email (hello Slack) but purposefully not got work email set up on your personal device? Good luck
I worked on a media heavy fashion site a few years ago and dealing with Safari not allowing you to dynamically add new audio/video elements with auto play (or to auto play at all in low battery mode) was a real headache. By default it’s great, just offer the option to get permission for experiences that require it.
https://techcrunch.com/2022/03/15/facebook-2018-breaches-dpc...
I also know that I don't know any phone numbers but my own from memory.
Glad they settled on those either way, because adding 200kb of uncompressed URLs and heading text for tracking is madness.
Does not contain: "quotes don't give" "quotes dont give"
Nor does the cached version: http://webcache.googleusercontent.com/search?q=cache:https:/...
Yes, as someone pointed out, there are tokenized versions down at the bottom, but that exact string does not exist.
So first of all it's just not true.
Second of all, if your consumers are all complaining the results do not match what they are searching, it might make more sense to listen. Adding quotations marks like that to find an exact string should be a huge red flag that the user is only interested in that string – why then would "it's in an offscreen meta tag of a cached version of the actual site" be anything other than a bad result?
Genuine question, my knowledge of server security is low-to-middle.