Yes, that's all true, all potential issues in theory. I'm still not seeing why this points to or supports the (valid) claim of incompetence in the FBI. That seems to be the angle most posters in this thread are taking, and it seems...misguided to me. Tilting at windmills. Let's call out the admin for their real failings, not nonsense like this. Getting your gmail account hacked does not reflect on you as a professional.
it's definitely newsworthy, no doubt there. but i see so many people in this thread pointing to this as somehow a failing of the fbi, which it's not. i'm all for calling out this administration for its many many failings, but this is not one of them, and calling this a failure of the administration just hurts the credibility of everyone pointing out real issues with this administration.
I'm no fan of this administration, at all, but this seems like a big fat nothingburger. They hacked a personal gmail account, not a government account, not government infra. Why is this not a failing of Google instead of the government? And surely the hackers would have eagerly released anything damning, but nothing damning seems to exist. What am i missing here?
This doesn't seem to work at all, at least for me.
First, the test claimed that my connection suffers from isp header injection but didn't actually indicate which headers my isp might be injecting, or even what the consequence of thus is.
Second, it claimed I am using my isp DNS, which is not correct.
I agree with you, and especially identify with the last sentence. However, I’m fed up with Apple and Google, and any alternative that doesn’t tie me to Google and has all functioning hardware and usable 5G or at least LTE with reasonable specs is a major win in my book. I’ve preordered the FLX1s. The FLX1, which is no longer in production, had a replaceable battery, but lack of a replaceable battery or non-pure Linux in an alternative phone certainly isn’t going to keep me chained to Apple or Google.
CORS doesn’t protect you from anything. Quite the opposite: it _allows_ cross origin communication (provided you follow the spec). The same origin policy is what protects you.
I honestly can't believe how unreliable Github is. Outages are commonplace. It boggles my mind how nothing has been done to address the reliability regressions that have been creeping in ever since MS took over.
Caution to anyone who clicks this link: mute your speakers first, or else you'll have to deal with blaring obnoxious music via an auto-play video that isn't visible without scrolling.
That's a site-specific partial exemption from the same origin policy, as far as i can tell (without further context at the moment). Not a difference in how CORS works generally across Safari.
CORS is frustrating for a lot of developers as it can be tough to gain a complete understanding of the spec, and an understanding of the same origin policy is required. But implementation of the CORS spec(s) isn't notably different across modern browsers, now that IE is out of the picture. CORS was a real nightmare in IE. Microsoft even introduced an XHR cousin named XDR in IE10 to handle cross-origin requests, and it wasn't even a complete implementation of CORS.
Sounds like you’re projecting a bit. Lots of reasons one might be up at 6, other than hype or a “meme”. For me, it’s the only time I have to work out (with a job and smaller kids).