Assuming, of course, that one's body _does_ naturally produce insulin. I'm glad it and other artificial sweeteners exist and are as prevalent as they are.
To add on to this, there's no standardized way of indicating what needs to be typed out and what needs to be replaced. `foo --bar <replace me>` might be a good example command in a README, but I had to help someone the other day when they ran `foo --bar <test.txt>`, not realizing they should have replaced the < and > as well as just the text.
Normally yes, but the L1 Lagrange point always would have an unobstructed view of the sun. Granted, L1 is a lot further away than LEO (~3x the distance to the moon), so that makes it harder and more expensive to get to
They also somehow broke scrolling via the scroll bar, swipe to go back, and jumping to text search results on iOS! This is the first site that I’ve seen break so many browser features.
oncontextmenu and ondragstart are preventDefault'ed _unless_ you are in a input/textarea e.g. leaving a reply. Truly bizarre and pointless. I've done something similar in a nonsense corporate context to stop people copying certain sensitive date, but at least I knew it was pointless.
In Firefox you can shift+rightclick to bypass that (disables the event), or completely disable the event by changing "dom.event.contextmenu.enabled" in about:config.
Very perplexed about this too. The only reason I can come up with is to prevent people from copying the content?
But that doesn't make much sense either TBH. The page's content is not obfuscated, so this does nothing to stop a content scraper script. Plus, even a not particularly technical user can just turn on reading mode and get at the text anyways...
Disabling highlighting and right clicking is common in some places in East Asia such as Korea.
As to why this is done I have no idea. Especially since you can circumvent the disabling of these abilities. Although you have to resort to OCR when a site decides to render the text as an image.
I typed "The quick brown fox jumps over the lazy dog", clicked "Check Everything", I get a brief spinner, and
[plugin:vite:import-analysis] Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.
or nothing happens
Edit: if I open the editor, type the same text, and then click "Fact Check", I get the same error
Oh, it is because we set a global check limit, 1 per second (we didnt think we would get so many users, got 500 in the last 30 minutes) We will fix that. But a simple reload should suffice
"According to a 2022 study from the Environmental Protection Agency, the average weight of a car is 4,094 pounds."[1]
Going from 1 person of 200lb to 4 people totaling 800lb (in a 4,000lb car) increases the damage by less than an additional car (4,800 / 4,200) ^ 4 = 1.71
