It’s possible it reduces the probability of things like wrongly answered stack overflow questions from being used, so it might actually work a bit.
Kinda like how with image generation, you get vastly better results by adding a negative prompt such as “low quality, jpeg artifacts, extra fingers, bad hands” etc, because the dataset from boorus actually do include a bunch of those tags and using them steers the generation to do thing that don’t have features that match them.
Being years behind Firefox is kinda the whole point of PaleMoon, the user interface is based on Firefox 4-28 and the rendering engine (Goanna) was forked from Gecko back in 2016 to remove all the new stuff Mozilla kept adding to it.
A single raspberry pi that draws maybe 3 watts, and fraction of a watt standby draw per device?
Also, 10w draw for a year is 87kWh. And you probably have more than just one light in your house.
Takes time to switch. Normally these things would be done sensibly and with enough time allocated for the changeover, not by an executive order that’s active immediately and may or may not actually be something the president even has authority to do.
The US federal government by law has to follow what names the United States Board on Geographic Names tells them to, and the executive order demanded they change it. He could have changed it to the Gulf of the King Donald Trump That Had Absolutely Nothing To Do With Epstein Honest, and that would officially be the name for it every US federal employee would have to use.
Nobody else has to use it though, but most companies follow what each local government says to not have issues with borders and stuff.
Because GitHub really doesn’t want to be the webhost for releases. They want you to spin up a website and provide downloads from your own server, and only link to github for the code.
ŚĆŻRŹĘĄMŚ
“Grey if it’s in England, gray if it’s in America.”
Same as tire vs tyre, center vs centre and so on.
One notable difference between X11 and W3C is the case of “Gray” and its variants. In HTML, “Gray” is specifically reserved for the 128 triplet (50% gray). However, in X11, “gray” was assigned to the 190 triplet (74.5%), which is close to W3C “Silver” at 192 (75.3%), and had “Light Gray” at 211 (83%) and “Dark Gray” at 169 (66%) counterparts. As a result, the combined CSS 3.0 color list that prevails on the web today produces “Dark Gray” as a significantly lighter tone than plain “Gray”, because “Dark Gray” was descended from X11 – for it did not exist in HTML nor CSS level 1 – while “Gray” was descended from HTML. Even in the current draft for CSS 4.0, dark gray continues to be a lighter shade than gray. Some browsers such as Netscape Navigator insisted on an “a” in any “Gray” except for “Light Grey”.
But they will work, and according to the spec, you have to build your system so that it can handle those cases. Obsolete doesn’t mean incorrect or invalid, just a “you shouldn’t do this any more”.
Obsolete Syntax
Earlier versions of this standard allowed for different (usually more liberal) syntax than is allowed in this version. Also, there have been syntactic elements used in messages on the Internet whose interpretation have never been documented. Though some of these syntactic forms MUST NOT be generated according to the grammar in section 3, they MUST be accepted and parsed by a conformant receiver.
“A bigot is someone intolerant of others’ differing ideas, races, genders, religions, politics, etc.”
I am very intolerant of the differing ideas of nazis, the far right, the westboro baptist church etc, so from their point of view, I’m a bigot.
They are simply pointing out that “racist” and “bigoted” are just as ambiguous in the exact same way as the “evil”, “harmful”, “good”, “negligent”, “bad”, “unethical” etc he mentions for the other licenses.
“bigot noun a person who is obstinately or unreasonably attached to a belief, opinion, or faction, especially one who is prejudiced against or antagonistic towards a person or people on the basis of their membership of a particular group.”
If being a bigot is good/bad/evil/harmful/unethical or not depends entirely on who is calling you one, and what you or society thinks of them. If you think that just because someone is a MAGA/Nazi/Tesla owner that they are bad, congratulations, you are a bigot.
Ye. I have all Ikea smart stuff, by default everything is running a local mesh network with physical remotes and that light switch backup.
You don’t even need to connect any of it to the net, buying a hub to get app & google home/alexa/etc control is entirely optional with the exception of a few sensors, like the moisture/water leak one. And even then, the app & hub work on local wifi with no internet anyway.
BT 5 has max bandwidth of 2Mbps, which would in theory be enough for “CD quality”, i.e 44.1khz/16 bit raw uncompressed audio, as that’s around 1.4Mbps. In real life conditions it isn’t. AFAIK aptX lossless gets close by doing some compression.
But if you go full audiophile levels and start demanding lossless 192khz 24 bit audio, that’s 10Mbps and not even remotely possible over BT no matter what you’d try.
“discard changes” button - the 5000 “new file created” changes, specifically.
There’s also the version with examples if you want to know exactly what and why it breaks.
And the git that collects all of these in one place, if you want to really nerd out.
It is still in early access and optimising the game is their current goal according to the road map, though as the whole concept of the game is about simulating every NPC properly at all times it’s always going to be really heavy game to run.
And you are right about accessibility making resource hungry games more common - they allow indies to make projects and use concepts that would have been scrapped as technically non-viable by a publisher before. Shadows of Doubt started development back in 2015, which would have meant reducing the scope of the game until it ran on a PS4. Being indie, they could just do whatever instead, and now it’s going to be enough if they can make it run acceptably on a PS5.
Sure. But the IPv6 implementation is a bit like if we went “you know the y2038 problem of 32 bit numbers, and how goin under 1970 is sometimes hard? Lets solve it by making it start from the big bang and store time as a 256 bit integer so we don’t run out until year 3.1 x 10^69”.
IPv6 is big enough for 340,282,366,920,938,463,463,374,607,431,768,211,456 unique addresses. Are we expecting to create an universe consuming army of exponentially replicating paper clip converting robots that each need an IPv6 address or something?
IPv6 is big enough to give 10 billion unique addresses for every grain of sand on earth and still have some left over. Just in case we need to, I guess.
Which would still not be perfect because “foo@bar”, “foo@[123.123.123.123]” and “💩 @[IPv6 :::1]” are all technically valid email addresses.
It looks like the only validation that doesn’t block something valid pretty much would start and end at “It has at least one @ symbol, and something on both sides”.