skysight-inc/HackerNews huggingface dataset:
The problems with Prop 65 go beyond that. The legislation itself effectively made no attempt to define what it means for something to cause cancer. The commission put in charge of enforcement ultimately decided it would mean anything that current scientific evidence suggests has a 1 in 100,000 risk of eventually causing cancer if you are exposed to it for an entire lifetime. Subsequent lawsuits clarified that a substance must be included even if the risk is only proven to exist in non-human animals.

Ironically, I never even knew this, but apparently the proposition only exists because Jane Fonda thought it would draw left-leaning voters to the polls to hopefully vote for Tom Bradley over George Deukmejian in the 1986 race for California governor. She and the other proponents didn't even think the proposition itself would pass. But the proposition did pass and Bradley wasn't even elected!
Sadly, while gemma-2-27b-it is available (as a Preview model) on the AI Studio playground, it didn't show up via API on list_models() for me.
ACLU challenges section 702 surveillance in neo-Nazi's prosecution
Not really one domain in particular, just internal services in general. In many cases, the field is intended to be required in the first place. If not, surprisingly 0 isn't a real answer a lot of the time, so it means none or default: any kind of numeric ID that starts at 1 (like ticket numbers), TTLs, error codes, enums (0 is always UNKNOWN). Similarly with empty strings.

I have a hard time thinking of places I really need both 0 and none. The only example that comes to mind is building room numbers, in some room search message where we wanted null to mean wildcard. In those cases, it's not hard to wrap it in a message. Probably the best argument for optionals is when you have a lot of boolean request options where null means default, but even then I prefer instead naming them such that the defaults are all false, since that's clearer anyway.

It did take some getting used to and caused some downstream changes to how we design APIs. I think we're better for it because the whole null vs 0 thing can be tedious and error-prone, but it's very opinionated.
Alot of folks won't have iPhones.

You can get a darn decent Android for 200$ unlocked, and if your really struggling a 50$ phone will get the job done.

No one will suffer if they can't get an iPhone.

A lot of folks also can't do math. I pay about $20 a month for my phone plan, and I paid $700 for my phone up front. AT&t isn't giving phones away, you end up on a more expensive plan that's around $80 or so and then they'll tack on 30 bucks for the phone.

If you're lucky the bill credits will cover the entire cost of the phone, but over two years you've still spent an addition 700$.
if you must know, there is a policy to handle cookies. There is also a manager for all the cookies. This manager tracks all the cookie handlers. The cookies themselves are stored in a cookie store. While legend has it Arthur Van Hoff designed this whole setup, if you look closely in java.net, the author of CookiePolicy, CookieHandler, CookieManager and CookieStore is actually Edward Wang. Anyways it is not important. Since one cannot maintain a session without session cookie, effectively the entire human population on the internet works in the cookie factory.
Wound care is bullshit when it’s not fraud. My dad was getting billed $12,000 weekly for treatment of bedsores due to neglect when he was inpatient. The procedure took under 15 minutes.

Compromised patient, injured due to basic incompetence, A Medicare probably paid a million dollars or more to treat it.
Until we find the political will to do that, creating products that fuck over journalism is shitty.
> This is complete bullshit

That may be your belief, but it is not, and beliefs mean little in the face of reality.

Saying the same thing in a more formalized way (so there can be no ambiguity), it is inherent in the 1:1 unique input to output relationship that is required for each state transition on a state graph, for the system's property of determinism to be preserved.

No disrespect intended, but you don't seem to have actually taken or learned important parts regarding this subject matter.

> computability theory has nothing to say about which (if any) cognitive tasks people can do that AI cannot.

You are incorrect. The very first video in that linked coursework (from MIT) provides a counterexample to this statement. The professor clearly states this is impossible, and the proofs that come later in the class prove it.

This statement is an over-generalization based in fallacy.
Python just has to rot13 the scheme and hash the encrypted schemes.
Ibuprofen, paracetamol, rest?

From https://www.nytimes.com/2018/01/27/opinion/sunday/surgery-ge...: if you "no longer feel the pain you will no longer know what your body is telling you. You might overexert yourself because you are no longer feeling the pain signals".
> That last thing was their crime

Taboos are bullshit. Either something is a clearly articulated, written, rule with an enforcement mechanism, or it's fair game.

Prescribing doctors are responsible for the opioid epidemic. Doctors failed in their duty of care to patients. Doctors massively overprescribed, failed to track their patient's medication usage, and failed to spot addictive behaviour. Why aren't we holding them responsible? Simply because that's hard to do?
Saving someone a click and a bunch of streaming services irrelevant to the question.

"To watch CNN's US Presidential Debate online, it will be streamed in full and for free on the CNN YouTube channel."
My fault, I did read the article but I overlooked the ConnectRPC mention.
My only evidence is that my RSI got better once I started using Vim full time. Of course, Vim forced me to learn to touch-type and I also never used Emacs, but I'm just going to go ahead and attribute the cured RSI 100% to Vim and assume every other editor causes it. That's my "research" tells me, at least! :D :D ;)
yeah, it might be a reasonable choice for mechanical parts like keyswitches and hinges. i think keyswitches with a wearout life of a billion cycles keyswitches isn't infeasible either, but testing them to verify the cycle life could be challenging
Most countries do without them now and have always done without them except in special cases such as palliative cures. You get opioids during recovery in the hospital, but not once you're discharged. You might get codeine rarely, but that's it.
That came up in the original post with whether an obfuscation could be an acceptable workaround; but it came up that Apple really doesn’t like obfuscation techniques. The workaround for now is a compiler flag that excludes problematic code from iOS builds.

I’m still asking though why, if Apple doesn’t like apps which use this protocol, the sandbox is not intervening; as surely an approved app could have a malicious web view.
There is a version of sheets in both App Stores and I believe you can run the android version on chrome OS
Fraudulent Transfer...

From Reddit...

Piercing the corporate veil would mean disregarding the corporate form entirely. It usually comes up when the owner-manager of a company fails to distinguish the corporation as a separate entity with its own purpose and finances, using the company as a personal piggie bank or otherwise going about life as usual and not going through the motions required of corporations under the law.

What plaintiffs have alleged against the Sacklers is different, and specific to bankruptcy. Perdue is out of money and is bankrupt, mostly because it caused billions of dollars of damages to hundreds of thousands of people and to the states (which now have to clean up the opioid mess). But not that long before it went bankrupt, it was swimming in money. Perdue didn't use those profits to avoid harming people. Nor did it keep the money on hand to pay potential tort claims from the people it was harming. Instead, Perdue's officers and board of directors (that is, the Sacklers) approved dividends of billions of dollars to be paid to the company's shareholders (that is, again, the Sacklers).

The plaintiffs in various lawsuits have alleged that the Sacklers knew that the profits were temporary and the bill would come due, so they purposefully got the money out of the company while the getting was good. More technically: it is alleged that Perdue's owners received assets that were transferred from Purdue with actual intent to hinder, delay, or defraud creditors.

One thing you absolutely are not allowed to do is use your company to rack up a bunch of debt or liability, take all the assets out of the company, and then declare bankruptcy and expect to get to keep the money. We call that "fraudulent transfer," and if a court finds that you did fraudulent transfers from your company to your personal bank account you will be ordered to pay that money back to the company (so it can use that money to pay back its creditors and other claimants). The company still exists, it's a distinct legal person (so not technically piercing the veil), you just took the company's money as if it were a profit when you knew full well the company couldn't afford to pay out profits.

One big difference between the concepts is this: If Perdue's corporate veil were pierced, the Sacklers would be personally on the hook for all the harm their company caused -- they could lose their bank accounts, vacation homes, nice cars, artwork, everything, as if they themselves (rather than "Perdue") had been the ones going around knowingly fueling a drug addiction crisis. Whereas if they merely engaged in fraulent transfer of assets, the Sacklers are only on the hook to give back what they fraudulently took from the company during the period it can be proven that they knew of the looming liability -- limited to the statute of limitations, which I think is around 6 years. So all the money they made before that, and all the money they have from non-fraudulent sources, is safe from creditors.
I'm trying to convey how legal conservatives think, as someone who is one. I am, on many policy issues, quite liberal. I think rich people should pay more taxes, people should drive EVs, etc. But ultimately I care more about the rules--especially the rules about who makes decisions and where power is allocated--than I do about what people or outcomes. I'd rather see 3C of global warming than administrative agencies operating contrary to the tripartite system of government the Founders designed. I care more about the Constitutional rules for allocating power to states than I do about what citizens of those states might do with that power. Etc.

Issues like abortion and environmental laws just happen to map onto particular legal issues as an accident of history. If state-by-state legislation leads to widely legalized abortion, for example, I don't think most legal conservatives would support a Roe-like judicial decision ginning up a "right to fetal life" (which actually exists in Germany). If Congress passed environmental laws itself, instead of outsourcing it to an executive agency, I don't think most legal conservatives would be looking for ways to second-guess Congress's judgment.

You actually see this in Europe. The legal system in European countries tends to be pretty boring, because they have more social cohesion and can legislate things according to the rules, rather than hacking up the system. The equivalent of Roe, for example, doesn't exist in continental Europe. In an irony, Emmanuel Macron criticized Dobbs when it came down. But France never had anything like Roe. And after Dobbs, France passed a constitutional amendment addressing abortion, which is exactly how legal conservatives would say you should handle the issue!
Because I know what opinion I have.
>The user is the most happy with your app that they will ever be. This is the point where you hit them with a review request.

Is this satire?
> The so-called "right tool" is also considerably more expensive on AWS.

I am currently in the process of reducing out AWS service coverage. I'm not sure if I've phrased that right, but reducing the amount of scalable services that they suggest and offer and that were promoted to the company I work for.

It's a numbers game, if you are serving a lot of clients, or processing a lot of things, AWS is fine, next question is, what is a lot?

All things are relative to workloads of course, but lets say you're serving 1 million requests a day, not concurrent, but overall, if you have an API gateway tied to aws lambda or step functions etc. Okay, I can understand you might want to scale up some of the 'workload' services.

Out of those 1 million requests, it's worth a companies time to take the step to evaluate, "Hey we have a contract with AWS, maybe a fixed price contract, but do we need it ?"

Fast forward after you realize maybe 10%~ lets say can be left as 'scalable' because they're CPU intesive or they could be consolidated to be a single 'microservice'. Great, now you have your scalable workload, the rest can be thrown on a single server..

> Since our architecture mandates that clients access data via APIs then the clients aren't affected by the change.

Architecture by definition should be forward stable. It shouldn't mandate anything, it should just facilitate the requirement. How you implement it isn't an architects concern (in theory).

AWS kind of makes a lot of tech debt here that is hard to justify to the people above. Because they've already paid. So now as a software engineer, I found a ~40% saving possible, but it doesn't sound right.

I'm honestly getting to discouraged with things. The MAX client list we will ever look at I was told was max 500 people. Maybe 200 concurrent.
"Soon"
https://x.com/LechMazur/status/1806366744706998732
I've heard C-suite literally say: "if there's no logging, there can be no evidence"...
Why do you suggest that the web version of sheets is faster than the swift or Java versions? I haven’t tried them, and certainly haven’t benchmarked them, but I would imagine they’re faster.
It is an unfortunately anthropomorphizing term for a transformer simply operating as designed, but the thing it's become a vernacular shorthand for, "outputting a sequence of tokens representing a claim that can be uncontroversially disproven," is still a useful concept.

There's definitely room for a better label, though. "Empirical mismatch" doesn't quite have the same ring as "hallucination," but it's probably a more accurate place to start from.
Enough people seem to love artificially low up-front prices, even if it costs them more (in money and headaches) in the long-run. See: Spirit Airlines, Ticketmaster, and restaurant fees and tipping.
Seems to have worked for gluten, at least. i.e. Consumers look for "gluten free" labelling rather than "This product contains gluten" labelling.

If I were the FDA I'd standardize the nutrition label to have a clearly labelled allergen section in which you can reliably use to check that the product is free of X allergen. Of course a naive implementation of this would mean that water bottles and stuff will have a big long list of "gluten free, peanut free, dairy free" so it probably requires a bit more thought.
Using TeamViewer is a security breach.
Rome is on the Tiber, which flows directly into the Tyrrhenian Sea (via Ostia, which was Rome's "Oakland" and had its own sizeable population in antiquity). London, Thames. Paris, Seine.

(Closer to MENA and the Levant, and you'll find that antiquity cities almost entirely exist on the Tigris, Euphrates, Nile, etc. You can find inland Silk Road ksour in countries like Morocco, but these too exist along seasonal rivers, and have correspondingly lower and nomadic populations.)

I don't particularly disagree about climate change, and I think a lot of the coastal Southern US is in for a rough awakening in the next 15 to 30 years. But things haven't been so peachy inland either (the Midwest has had both more numerous and more severe floods, tornadoes, etc.). NYC's weather is also certainly going to become more extreme, and the city's response so far has been unimpressive.
Tunable entangled photon-pair generation in a liquid crystal
Pull parsers can deal with arbitrarily large messages too. And they also do one pass over the input data.

Yeah if you're unfamiliar, SAX is like this (pseudocode):

interface SAXCallbacks {
void onBeginToken(string name);
void onAttribute(string key, string val);
void onText(string text);
void onEndToken(string name);
}

void parse(Reader input, SAXCallbacks yourCallbackImplementations);

Whereas pull parsers are like this:

enum Token {
Begin(string name),
Attribute(string key, string val),
Text(string text),
End(string name),
}

class PullParser {
void open(Reader input);
Token next();
}

They are much easier to use because you can trivially write a recursive descent parser:

void parseThing(parser) {
let token = parser.next();
if (token == Begin("foo")) {
parseFoo(parser);
} else if ...

Whereas with SAX you're going to end up with some monstrous hand-coded state machine like

class ThingParser {
enum State {
ParsingThing,
ParsingFoo,
ParsingFooExpectingAttributes,
ParsingFooExpectingEndTag,
...

So painful. Honestly it's so obviously the right way to do tokenisation and parsing that I have yet to see another language that even has names for them. They all just use pull parsers. Nobody else does callback-based parsing like SAX because it's obviously ridiculous.
I don't mean simply that the DMV might sell your information; I mean that given your name and some basic information, I can potentially just generate your valid ID. Millions of drivers license IDs are essentially public. It's always a little weird to me to see people treating them like hazmat. I sort of get why? Hazmat whatever you can? But an Illinois drivers license for a 40-year-old is public.

Imagine if, until relatively recently, a social security number was a truncated MD5 hash of your name and birthday. That's the flavor of the problem here.
I would expect an open source feature flag solution today to support https://openfeature.dev/
Is that protein isolate different than my isolated whey protein workout shake
See no evidence, hear no evidence
I don't see any updates in the archive since then
https://www.albartlett.org/
Devs I think are somewhat withdrawn, as a result of being under the yoke of ticket delivery. Being given the trust respect & capacity to roam & improve as we wander about systems is rare; we're judged on how quickly the task at hand is done. This is such Luddite, chained-to-the-machine endpoint that we are at.

And it skips past so much of the raw joy & auto-enrichment loops that happens when there's time allotted to discovering and improving the system as you go. DIYers have such amazing enrichment loops, making systems work better for themselves all the time. Not just the much vaunted fast delivery now, but the ability to keep iterating & expanding & delivering without your constructs starting to clash & thrash.

I love love Fogus's 100:10:1, on having many tangible places outlined where one might do something. Still dedicating yourself to something, but also giving yourself permission to hop around. Follow what feels good.
https://blog.fogus.me/2015/11/04/the-100101-method-my-approa...

[Ed: s/yolk/yoke/, thanks for the fix folks!]
Jan 8, 2024....
I’m not sure what the big deal with the url handler is, but I can’t imagine it causing remote code execution or other actual malicious behaviour.

At this point Apple seems to be using simple substring matches, so if there is any exploit vector the malware authors can circumvent the check using "itms" + "-services" or something more sophisticated like ROT13.
100% correct and I appreciate the additional details! I couldn't come up with a good analogy to explain you want the emitter as a separate and unique element from everything else involved in a tube — oversimplified in the process.
I'm gonna go ahead and be a stinky and say I'm lukewarm on DadBod (as a name, the plugin is awesome). It's just a reference to a well-liked tweet he made and otherwise the only thing it really has to do with databases are the initials. I actually remember he released it under a different name and someone opened and issue saying it was a missed opportunity to call it "dadbod," lol.

Other good ones with more double meanings:

- PROJECTionist
- unimPAIRed
- COMMENTary
so, with respect to steel, i think a steel case in a sweaty pocket will rust rather quickly and comprehensively, even if it's a good steel. often alloying elements that improve steel's mechanical properties make it more prone to rust rather than less so

i'm guessing the drill press was not in working condition after the 20 years of moisture, and i'm assuming you mean something like 'in a basement with relative humidity that reached 100%' or 'with the bottom resting on moist soil' and not 'under dripping water for 20 years' or 'underwater for 20 years'

i don't really have a good way to machine steel anyway, and it's inconveniently heavy. aluminum is amenable to wood rasps and drills

i think probably embedded in silicone or paraffin wax or something would be better than just stored in nitrogen. gottta be careful of static buildup tho

while i sympathize with preppers in some ways (i, too, value autonomy) i think they might be a hard group to market to. a friend of mine occasionally reads survivalist board forum and there's a lot of toxic ultra-right-wing stuff there; i don't want to be lynched for not supporting trump

you can of course do secure encryption on any general-purpose computer unless you're trying to defend against side-channel attacks. i ran pgp on a 286, and we have more efficient algorithms now

long-distance radio is potentially interesting but i agree that it's probably a different piece of hardware; short wavelengths can only go short distances unless they're bouncing off the moon or something, and you need a long antenna to transmit long wavelengths efficiently, although efficiency isn't a significant concern for reception (at transcontinental-capable wavelengths radio noise is a bigger concern than noise generated inside your amplifier). so for long-distance radio you probably need a large, fixed antenna installation rather than a pocket computer

my concern with pneumatic-to-electric power is that it's probably hard to make reliable. but i don't really know
The transition to documented humanoid robots might take less than a decade.
>Pretty sure RMS wouldn't like it

And we need to care about that for what reason?
Yesterday I was at a Bikeshop and was discouraged to buy a wheel hub motor eBike compared to a bike with these motor next to the crank. Apparently if you change your wheel (i.e. having a flat), you loose your warranty from a supplier(not going to name).

So a big negative for me is the added complexity and dependency on bike shops for simple things as changing wheels.
haha, "excels"
Jail for the execs.

Loss of license for the nurses and doctors.

People died but the money matters more?
So? Congress passes "CAFE" style standards requiring that every large bakery offer a fraction of their SKUs as allergen-feee variation, or pay a "cap and trade" fee to a baker who does.
> The 50 cal on top turned to point at me, I dropped the pear cannon and walked away

Pretty sure I would have dropped something else and RUN away
> zero consequences

Zero fucks given: "None of those companies responded to multiple requests for comment from 404 Media."
> But instead they live in fantasy of becoming next Netflix and burn in billions of dollars in debt.

Hell, even ~15+ years ago I knew not to fall for cargo-culting arguments of "come work for us; when we're as valuable as Facebook the stock we'll pay you with will make you a billionaire". Yeah, ... sorry, not moving to Silicon Valley and try to haggle for coffee with imaginary invaluable stocks.

So, I can't believe that ... for all their money's worth, these companies can only come up with "when we have as much users as Netflix, we'll be billionaires".
[dupe] https://news.ycombinator.com/item?id=40810084