172 karma · joined August 10, 2023
The app is not impartial in the content it chooses to push. I got identified as a target for very specific content and in the context of this discussion, it's the polar opposite of what reddit used to be.
you'll see this behavior fade in the presence of someone who they themselves perceive as superior by whichever metric
>5.1. Incomplete Isolation > >The secure context definition in this document does not completely isolate a "secure" view on an origin from a "non-secure" view on the same origin. Exfiltration will still be possible via increasingly esoteric mechanisms such as the contents of localStorage/sessionStorage, storage events, BroadcastChannel, and others.
>5.2. localhost > >Section 6.3 of [RFC6761] lays out the resolution of localhost. and names falling within .localhost. as special, and suggests that local resolvers SHOULD/MAY treat them specially. For better or worse, resolvers often ignore these suggestions, and will send localhost to the network for resolution in a number of circumstances. > >Given that uncertainty, user agents MAY treat localhost names as having potentially trustworthy origins if and only if they also adhere to the localhost name resolution rules spelled out in [let-localhost-be-localhost] (which boil down to ensuring that localhost never resolves to a non-loopback address).
>6. Privacy Considerations > >The secure context definition in this document does not in itself have any privacy impact. It does, however, enable other features which do have interesting privacy implications to lock themselves into contexts which ensures that specific guarantees can be made regarding integrity, authenticity, and confidentiality. > >From a privacy perspective, specification authors are encouraged to consider requiring secure contexts for the features they define.
This does not qualify as the "this" in my original comment.
You are also biased in the way you only see what came to be and ignore what did not.
1. not all browsers are the same
2. there is no official standard
3. even if there was, standards are often ignored
4. what is true today can be false tomorrow
5. this is mitigation, not security
Saying things like "it's unreasonable to eat meat and fish" a very ignorant in more than one way.
https://m.youtube.com/watch?v=gB9n2gHsHN4
If you want to learn more about the fascinating world of fractals.
i agree that the cognitive load in a language like js which is not prepared to accommodate this paradigm is not worth it
even when deciding to use Haskell we need to weigh the pros and cons wrt the project's goals
now correct it for number of sold phones each (estimated by looking at the 70 most popular models) and we'll get why they said 1/4.