That key binding was added for interface compatibility with Internet Explorer, which is less important these days. If you'd like to disable it now, go to about:config and set browser.backspace_action = 2.
I'm not sure why it was introduced as an amendment for a bill about distributing federal education funds, but I'm sure there's some justification in the legislative process.
Anyway, this is very clearly tailored towards the current Epic vs Apple/Google fight, right down to disallowing "retaliation" from platform providers.
I'm not sure it's even accurate to say that Wayland closes one of the holes when the hole Wayland closes isn't part of the system's security boundaries. It's like installing a deadbolt in a door standing in the middle of a room.
Firefox Sync encrypts all data client-side; Mozilla has no way to read it. Chrome also supports client-side encryption as an optional feature using an additional passphrase.
MS and Google have already said so. Flash will be blocked from loading in every version of Chrome next month, and the next version of Chrome to ship will remove all Flash support entirely from the codebase. Chromium-based Edge will follow suit.
Enough folks have replied that transactions are the way to go, but I just wanted to add that whatever interface tool you use for your database may have an option to force you to commit your transactions manually. For example PostgreSQL's default 'psql' shell has the "autocommit" option which, when disabled, requires you to manually 'commit;' before any changes take effect.
I looked for a way to disable the media keys feature when it landed in Developer Edition and it seems to be only in about:config. The key is "media.hardwaremediakeys.enabled".
Not a gossip column, political reporting. This is appropriate because this is a political story. The subject isn't the case against Google but the internal conflicts in building the case.
The WinRAR post doesn't say that the file was submitted to VirusTotal, only that the CA said it "looked like a file used by hackers". Either there was no VirusTotal record for it or there was and WinRAR omitted that fact because it weakened their argument.
You are misunderstanding. WinRAR's implication is that the CA is lying about the 570 MB file because they didn't mention it until WinRAR challenged them on the VirusTotal justification for revocation, and because they were unable to provide the file in question or any evidence that it exists.
"Growth hack" is an industry euphemism for "unethical practice." You can tell it doesn't literally mean "growth hack" because it's being applied here to the website that Alexa currently ranks #152 worldwide and the typical excuses about how you need to get a little dirty when you're a tiny business just getting started don't remotely hold water.
Firefox's private browsing feature blocks tracking scripts. Edge's doesn't as far as I can tell, and I haven't looked into the behavior of smaller Chromium-based browsers.
You're allowed to link GPL'd code that you own against your own closed codebase, because the GPL is just the terms under which you license your copyright to others. See also: "open core" and dual-licensed software.
The concept for SimCity was inspired by how much fun Wright had playing around with the map design tool for Raid on Bungeling Bay. The design of SimCity was inspired by Wright's research on urban planning and system dynamics during its development.
I love AutoHotkey, and it works wonderfully in the niche of writing a bunch of tiny UI- and workflow-smoothing functions, like how an Emacs user gradually builds up tweaks in their config file. The one time I tried to use it for scripting that required more than the most basic logic, I ran screaming back to Python. Over a decade of well-meaning development and reasonable design choices have resulted in AHK growing a syntax Frankensteined together from Basic, JavaScript, and batch script. Thankfully the upcoming AHK 2 is cleaning up a lot of the mess.
I wanted to link that not because of the "there's an XKCD for everything" meme but because it makes an interesting point: sabotaging roads isn't difficult now, with human drivers. There's no reason to assume it would suddenly become a substantial threat when autonomous cars are commonly adopted. An issue worth considering and accounting for, but not worth public worry.
As noted in a recent (and very busy) thread, Chrome sends an installation-specific ID to Google domains in a special header. This can easily be used as an identifier for tracking in the absence of cookies, and it's an advantage that Google's competitors lack.
The policy that the system is intended to implement requires suspending customer accounts for detected fraud but not for cases of sabotage, so it needs to judge intent until the policy is changed. I would imagine that the current policy was designed under the assumption that traditional click fraud would be the dominant form of fraud and so making it more difficult would be the highest priority. Simply removing detected fraudulent traffic without enforcing a ban would make it easier to test and iterate on fraud bots without burning as many accounts. I don't think there's an easy answer.
The fascinating thing here is that Google's systems are required to make a judgement of intent. Is this ad fraud ordinary fraud that's intended to increase payouts, or is it intended to be caught so the account is suspended? From the scammer's perspective, there's no reason not to play both sides: test fraud patterns to see if they're detected, and when they get caught just redirect the bots towards extortion victims. No matter how well Google's detection system works, the scammer gets paid.
2020 was a common pivot year used in the "windowing" workaround to the Y2K bug. 2-digit years < 20 are defined as 20XX, while years >= 20 are defined as 19XX.
The important point here is that there's no minimum length for code to be copyrightable. It simply needs to be original and at least minimally creative. Since at least thousands of other developers have found the snippet to be useful enough to directly borrow rather than writing an equivalent, it sure looks copyrightable to me.
You don't need to develop for HTML/JS directly to target the browser as a platform. (Not to say it's not an option worth considering, just that you can get the delivery benefits from other stacks.) Many current engines can build for the browser as well as native applications: Unity, Godot, GameMaker, OpenFL come to mind.
Technical details aside, it describes two methods of performing delegated rendering on Mac. One uses public APIs and causes a "reduction in performance and increase in GPU power consumption." The other uses the reverse-engineered CAContext API.
That's true. (And this is tangential anyway.) I do think that a greater familiarity with how the government works could help in that moment of panic, reducing the self-doubt of "I don't think this sounds right, but what if I'm wrong?"
There are a few common scams that directly demand Google Play or iTunes gift cards from the victim. The most depressing one I've heard about is a phone scam where the caller claims to be from the IRS and demands that the victim pay some overdue taxes in the form of gift cards. This is common enough that I've seen notices specifically warning about it on the gift-card displays at drug stores. The fact that this scheme apparently works says a lot about America's civics education.
The basic economic angle of it is that video games are a hit-driven business. Large publishers especially during the 1990s have a diverse product portfolio that can cushion moderate failures with the income from hits (more so during the 90s than today). When a small studio is growing its games and budgets to keep up with player expectations, the relative safety of a publisher can be tempting compared to sticking it out independently and betting the company on each game.
There's a great wiki called The Cutting Room Floor that collects odds and ends found inside video games: remnants of cut content, differences between regions and revisions, and about a thousand examples of this sort of hidden message.
ReCAPTCHA v3, the version I was referring to in what you quoted, doesn't have an audio CAPTCHA or any kind of fallback option at all, which is part of what makes it so much worse than v2. (The other part is the privacy implications of adding thorough behavioral tracking to every part of a website.)
That's correct. ReCAPTCHA v2 is the one where if your opaque, invisible ML humanity score is below a threshold it makes you squint at weird little photo squares and try to figure out whether the part of a bumper at one edge is enough to count as a car. ReCAPTCHA v3 is the one where if your opaque, invisible ML humanity score is below a threshold the website just breaks in unpredictable ways until you either give up or (for highly technical users) notice that ReCAPTCHA is at fault and interact with enough Google services to raise your score before trying again.