And in countries such as Germany you are legally required to be an employee if you only work for one company. The government will sue the company or if not reachable, they will sue the employee.
> Europe's GDPR makes the entire EU two-party consent
False. A business might be required to inform you that they are recording, but many EU member states have one-party consent laws otherwise. For instance, Finland, Sweden, Latvia, Denmark, Netherlands, Poland and Italy.
In theory it doesn't, in practice it does. New hardware only trusts the MS first party CA out of the box (not even the 3rd party one for booting e.g. Linux distros!) and many systems do not allow removing the MS CAs from the trust store.
OTOH, once the original Microsoft-signed SecureBoot keys for both Windows and Linux became compromised in recent years, triggering the need to blacklist those keys in everyone's firmware which requires an unprecedented worldwide need for a timely firmware update only if available from the original motherboard manufacturer, along with corresponding OS updates to match, neither of which has been fully accomplished yet, there was no-one to rely on other than Microsoft to mitigate the snafu.
More than just amusing, to "quote" Ballmer: "This is by design."
You're the one who is confusing threat models - namely the threat model I care about and the one Microsoft cares about. One has microsoft as the source of trust and one has them as an adversary.
> "source of trust" is a technical term, and not a judgement about trustworthiness.
No, its both. And when there is a mismatch then you have a problem.
Ublock origin (on firefox) appears to completely block spotify ads in my browser. At least I assume that's what's blocking it. Have never heard an ad on a free account...
18? That's ridiculous. I'd understand 14, but at 18 it's not too rare to live alone and have a full time job. And even before, access to maps or Wikipedia is generally quite useful. It's the social media that's the main issue, and not the other features.
SSE is cool, but as others have pointed out, this isn't that. I also wouldn't call this Comet: almost unilaterally, Comet referred to using it in concert with JS/Ajax and usually was just a fancy way of saying long-polling (though I admit it's a bit broader than that in truth). What CGI:IRC did was different: it streamed HTML directly. More to the point, it didn't use chunked encoding or any kind of framing in the body. It just kept the connection open and kept sending HTML in realtime. I don't think this ever had a term associated with it, or at least I was never aware of one.
Woah! I completely and entirely forgot the term "forever frame" existed.
Another term you don't see too often these days is the "holy grail" layout. I definitely remember the days of messing with negative margins and clearfix to get my page layouts to look nice while still working in IE 6 :)
I think you're right that Comet refers more to the JavaScript techniques that came from those "forever frames".. but to me it was all about the streaming HTTP hack at the heart of it.
I guess it's academic now :-)
Regarding holy grail layout and IE6.. so you're telling me you're a masochist!
SSE came along much later. At the time it was common-ish to just slowly send HTML tags. I think at some point there was a gorgeous hack where they dynamically rendered and sent GIF frames with the messages of the chatroom.
