skysight-inc/HackerNews huggingface dataset:
That's completely untrue. Try using any base (non finetuned model) such as llama base, mistral base etc and you'll see that it does not write like that. That response format and writing style was added by OpenAI during the finetuning stage.
When I was learning webdev (around early 2010s) I was very confused about exactly that. I couldn’t even comprehend how and why API of a web service could or need to be RESTful in the proper sense of the word. HTML is the REST API of the web. It allows people to dynamically navigate webpages to get what they want. Most APIs don’t need to be REST and to follow HATEOS: no one is going to explore them on the spot. So it’s just RPC built upon HTTP semantics (and sometimes not even that when everything is just POST requests with weird URIs).

Many tutorials back then explained what REST is and then explained what RESTful API is. And they seemed like two totally different things. I thought I am not getting something. Thankfully, at some point I realised that all those tutorials and people were just parroting bullshit. At best one could say that JSON over HTTP is REST-like compared, for example, to websockets.
I agree that my dismissal was shallow. Oops, my bad. In contrast, your comments were clear and concise. I think my inclination towards criticism sprang out of the flowery and obscure prose the author used to make his points. I would wish the original author had been as clear, concise and to the point as you are. As other commenters have said, some of the sentences leave my brain swirling with "what is this man trying to say, I have no idea?"
How has it advanced greatly since then?
Paywall loading at the scroll
Southern coast has seen an excessive amount of hurricane damage over the past five years. Check florida and gulf coast state insurance rates recently.
actually that guy can now be sued, per TOS it is illegal to publish benchmarks for Oracle DB.
Yeah that's what I mentioned in the last sentence of my comment

The reason most build systems don't have it is because sandboxing is OS-specific

Bazel has sort of a complicated bootstrap/deployment for that reason.

I mentioned it a few times, but someone should extract the exec wrappers from Bazel as a separate project :) It's a small amount of code, though fiddly to build and distribute

There are few other strategies like bubblewrap, but last I heard bubblewrap is not installed by default on most distros. It needs setuid root so it's a bit fiddly and has security implications

But then you also need something totally different for OS X and Windows
Reminds me of John Lennon. At the time he was singing "Imagine no possessions" he had an entire floor of the Dakota building[1] just for his and Yoko Ono's fur coats.

[1] https://en.wikipedia.org/wiki/The_Dakota
Test Quality vs. Bashing TailwindCSS
Seeing as the closer in ideology you seem to have to be to make such claims, I don’t believe what you’re saying is true for a second.
Early on in the container hype cycle we decided to convert some of our services from VMs to ECS. It was easy to manage and the container build times were so much better than AMI build times.

Some time down the road we got acquired, and the company that acquired us ran their services in their own Kubernetes cluster.

When we were talking with their two person devops team about our architecture, I explained that we deployed some of our services on ECS. "Have you ever used it?" I asked them.

"No, thank goodness" one of them said jokingly.

By this time it was clear that Kubernetes had won and AWS was planning its managed Kubernetes offering. I assumed that after I became familiar with Kubernetes I'd feel the same way.

After a few months though it became clear that all these guys did was babysit their Kubernetes cluster. Upgrading it was a routine chore and every crisis they faced was related to some problem with the cluster.

Meanwhile our ECS deploys continued to be relatively hassle free. We didn't even have a devops team.

I grew to understand that managing Kubernetes was fun for them, despite the fact that it was overkill for their situation. They had architected for scale that didn't exist.

I felt much better about having chosen a technology that didn't "win".
The Black-Scholes equation describes the unconscious biases that influence the price of options. It is able to beautifully separate the one quantity that every trader prices differently from the rest. That’s volatility.

All the other factors, time including, are the same for everyone.
I seriously don't understand who actually falls for this stuff. Like, oh, this company I bought something from a year ago sent me an email, let me go buy something else from them. Oh, this company I've never heard of sent me an email, definitely let me do buy something from them. ???

Oh, here's a good one: Capital One just sent me a newsletter entitled "Can you spot a scam?". First, yes I can, and second, it's a clear advertisement for them and their "partnership with KHAN ACADEMY" (caps theirs).

Guess where the unsubscribe link is? Oh wait, there isn't one. "This email was sent to capitalone@... and contains information directly related to your account with us, other services to which you have subscribed, and/or any application you may have submitted."
There are two meaningful difference between licenses.

One is the size of the pile of money you are willing to pay lawyers to enforce it. Because there is no software license enforcement agency that is going to sue neerdowells on your behalf.

The other is excluding good actors who don't want to deal with it. Obscure licenses increase the number of good actors who will forego using the software because parsing non-standard licenses is work and raises questions about the competence and/or motives of the developer.

Obscure licenses don't protect users. Good luck.
"One concern, however, is that the simulated solar panels were darker than most manufacturers make them. Some current solar panels are even reflective, designed to cool their surroundings, Lu says."

That seems like a critical issue.
Especially if they hold TSLA indirectly through ARKK.
> I'm constantly fascinated

To call a halt to your constant fascination: they don't all have that problem. They still get the complexity of cloudy things regardless when they use one.
Whenever looking at one these, I think back to the obscure but interesting "tup", and try to decide if this new thing is better. Because tup is awesome:

“How is it so awesome? In a typical build system, the dependency arrows go down. Although this is the way they would naturally go due to gravity, it is unfortunately also where the enemy's gate is. This makes it very inefficient and unfriendly. In tup, the arrows go up.”

https://gittup.org/tup/

On a more serious note, the whitepaper: https://gittup.org/tup/build_system_rules_and_algorithms.pdf
Well, you need to be in proximity to wealthy people to get that information, and that's why it's under served. There's not really a public clearinghouse of unaddressed wealthy-people-problems to inform this market that I know of.
Buying property is a pretty bad way to put money into the economy, though partly dependent on your locations approach to capital gains (where I am it’s untaxed).
None off the top of my head but for the engineering topics in Part III I think it pays to read them as historical background material, then read the last decade of conference papers, talks, and articles.

Example: the section on backend subsetting in distributed systems is not current. If you wanted the current Google practice you need to read "Reinventing Backend Subsetting at Google"[1], and there are other interesting publications from other organizations.

1: https://queue.acm.org/detail.cfm?id=3570937
> Louis-Henri Fournet was probably the historian I've read that from first. You can find the book on Amazon, but it's in French (tableau synoptique de l'histoire du monde)

Merci (ça ne va pas poser trop de problème ;))
Paper Karma (there are other similar tools) has been somewhat successful for fighting physical mailers. I just moved in with my girlfriend after having used it extensively at my last residence, and because of this, she is getting tons of junk mail and I am getting almost none.
> you don't have to go full functional verification

The amazing thing to me is that Ada code can call SPARK code just fine, and there's crates of SPARK code in Alire that you can use. It's a huge boost of confidence in the quality of a library that you're using when it has some form of verification.
I have done it. Net segmentation , net auth .1x and identity governance are must do implementations.
This is how he does it.

https://starbreaker.org/reject.js

All I had to do was right-click and select "view source"? It's not like he minifies his HTML to hell and back like people do on commercial sites, but maybe his build step is mangling his <script> element. That might be why it's only working on Firefox.

Incidentally, he has reasons for not liking people who comment on this site. He explains them in <https://starbreaker.org/blog/they-came-from-hacker-news/>. You need not agree with him, but he isn't being arbitary or childish.
The incoming call alone is more of a disruption than an email, honestly.
It’s not the fruit of their labor. It’s a combined effort they’re disproportionately benefiting from due to the aforementioned policy failures/corruption.
>Ezra Croft has never filed an insurance claim, and his house in Raleigh, North Carolina isn't close to a stormy coastline or a fire-prone forest.

>So Croft was surprised when his annual homeowner's insurance premium shot up to $1,600, or $700 dollars more than he was paying just a couple of years ago.

Among other things, his insurance premium is paying for the costs of losses in high risk areas.
>> Managing a reverse proxy with blue-green deploys behind it is not going to be trivial, and you have to roll most of that yourself.

There are a lot of reverse proxies that will do this. Traditionally this was the job of a load balancer. With that being done by "software" you get the fun job of setting it up!

The hard part is doing it the first time, and having a sane strategy. What you want to do is identify and segment a portion of your traffic. Mostly this means injecting a cooking into the segmented traffics HTTP(S) requests. If you dont have a group of users consistently on the new service you get some odd behavior.

The deployment part is easy. Cause your running things concurrently then ports matter. Just have the alternate version deployed on a different port. This is not a big deal and is supper easy to do. In fact your deployments are probably set up to swap ports anyway. So all your doing is not committing to a final step in that process.

But... what if it is a service to service call inside your network. That too should be easy. Your passing id's around between calls for tracing right? Rather than "random cookie" you're just going to route based on these. Again easy to do in a reverse proxy, easier in a load balancer.

It's not like easy blue green deploys are some magic of kuberneties. We have been doing them for a long time. They were easy to do once set up (and highly scripted as a possible path for any normal deployment).

Kubernetes is to operations what rails is to programing... Its good, fast, helpful... till it isnt and then your left having buyers remorse.
Graphinate. Data to Graphs
Graphinate is a python library that aims to simplify the generation of Graph Data Structures from Data Sources.

It can help create an efficient retrieval pipeline from a given data source, while also enabling the developer to easily map data payloads and hierarchies to a Graph.

In addition, there are several modes of output to enable examination of the Graph, and it's content.
Volatility is a bit more predictable than price. And there are more complex formulae that also model volatility rather than treat it as a constant.
It is frustrating that people don’t know what makes REST RESTful. But what’s weirder is why people seem to want to make things RESTful in the first place. Why has it become a signal of quality to claim something is ‘RESTful’?

I mean, for which problems does a true, Fielding-style RESTful API and universal client model actually make sense?

Fielding himself was describing the World Wide Web. Not a web application - he was talking about the entire ecosystem on which arbitrary web applications can be built.

The web (when driven through a web browser, at least) is RESTful, no matter what you do on top of it.

If you are not building your own universal application ecosystem of services and clients akin to browsers and web servers, you don’t actually need a REST architecture. You probably need an RPC architecture.

But for some reason people have acquired a vague understanding that REST is ‘better’ than RPC.

What they usually mean is that idempotent resource-verb based RPC APIs are a more compatible way of building applications within the REST architecture of the web than SOAP-like RPC APIs are.
There are two gas stations in town (same company) and they both have ads. :'(
I am always amazed how much usability fit into these low resolution screens. Today's software designer really struggle in usability although they have enough space.
I honestly think docker compose is the best default option for single-machine orchestration. The catch is that you either need to do some scripting to get fully automated zero downtime deploys. I have to imagine someone will eventually figure out a way to trivialize that, if they haven't already. Or, you could just do the poor man's zero downtime deploy: run two containers, deploy container a, wait for it to be ready, then deploy container b, and let the reverse proxy do the rest.
I think you misread my comment. I am aware of Plasma Mobile, but I don't see my bank's app and WhatsApp on it.
For people that want to do something similar on Windows, I can wholeheartedly recommend FanControl [1]. It's sadly not open-source, but it works great, and is quite pleasant to interact with.

[1]: https://getfancontrol.com/
Mantine UI
If there are any uniquely identify able patterns such that you found find that point on all microphones then deployment my sbts-aru project in four places surrounding it might very well localize it for you
> I’d say the false pretenses to go to war in Iraq are pretty well understood, now, and there’s no question we were misled by the government.

No one faced war crime tribunals. Torturers who destroyed Congressional evidence were given promotions. The chief Democrat cheerleader for that war, who blocked key witnesses that could have prevented it all kicking off, was made Vice President for 8 years. And then President. And is running again, despite seemingly not remembering what years he was Vice President. The guy who exposed a small fraction of the war crimes which resulted has been tortured for the last decade.

So. no, I don't think it's very well understood at all.

> repainting Saddam as a misunderstood author who had nothing but a desire to preserve well written Arabic is revisionist and wrong.

That's not what the article was saying. It was saying that Saddam had no WMDs, nor intention to gather them - and we should have known that. We didn't do our due diligence before spending 8 trillion dollars creating a vastly less safe world.

If there's revisionism to be found in tfa, it's that the invasion of Iraq was somehow inevitable; just like, part of that 90's vibe. It wasn't inevitable at all - many people made fucked up choices to make that chaos happen, and the whole world is suffering to this day and for the foreseeable future as a result.

We haven't learned a thing if we're blaming Saddam for all that.
>Guns don't kill people; people kill people.

Fix't that for you.
Anything is a weapon. The resulting high score is merely a matter of practice. No exceptions.
I didn't realize this was becoming more common. It seems far more uncomfortable for everyone involved, although based on the comments it does seem like some people appreciate a phone/Zoom call. I don't really understand why, though (please try to explain!). An email gives me more time to process difficult news, and prevents me from needing to act positively in an unambiguously negative situation.

I've been called for a rejection exactly once, less than an hour after I'd left the office where I was being interviewed. I was kind of shocked (the interviews went really well) and I didn't realize until later that the recruiter never said my name, and had previously claimed I would absolutely not get the result for at least 3 days. A week later, I got an offer, and I always felt a little bad for the candidate I unintentionally caused to get ghosted because the recruiter dialed the wrong number and I didn't figure it out.
ever heard of nomad?
I agree with doing more in the database, you're closer to the data (disk/disk cache/L2 cache) than the application code is. At the same time I get really nervous around doing work in the database because you have to be really disciplined that the in-database code (functions, views, etc) match the code in source control. Also that your testing/QA database contains all the same code and enough test data to actually exercise the performance bounds of that code.

With application code I can easily step through it in a debugger and verify the deployed code matches what's in the repo. It's more difficult to do in the database because it requires more organizational discipline.
It's already been happening. Google has been useless for a few years now due to blog spam. To be fair they shot themselves in the foot by prioritising content length.

Measuring search ranking by content length is like measuring aircraft building progress by weight.

So now people put 'reddit' or whatever in the search to try and get some authenticity but even those platforms are full of corrupt mods and astroturfing.

The UK are always ahead of the game when it comes to a dystopian future, chomping at the bit to put in place some kind of internet-licence to watch pr0n https://en.wikipedia.org/wiki/Proposed_UK_Internet_age_verif...
Naive binary
+1 Myth of the flat Earth

For some years I gave talks about this (Germany), it is astonishing how many people think that the idea of a spherical earth is a new one.

"The myth of the flat Earth, or the flat-Earth error, is a modern historical misconception that European scholars and educated people during the Middle Ages believed the Earth to be flat."

https://en.wikipedia.org/wiki/Myth_of_the_flat_Earth
Both can be true at the same time. A lot of the time the best move is obvious. However, if you play the top move 20% of the time, you will also play the top move in a lot of cases where it's not obvious. Given enough games, it's detectable.
One related publication that I thought would have fit well into the comment about disparate pain treatment is this[1] from Ziad Obermeyer's group. They found that when they trained a model using patient pain and knee X-rays, much of the disparity in symptoms could be accounted for by findings from the X-rays themselves. It's a nice example of where using the patients' symptoms and objective data may actually outperform current medical standards, which fits with her participatory comments in the final paragraph.

1 = https://www.nature.com/articles/s41591-020-01192-7
voip supports email addresses, the system is already in place, we just need broader adoption
Yep. This project

https://github.com/hcfman/sbts-aru
> > For every dollar in home and auto premiums they collected last year, insurance companies paid an average of $1.10 in claims and expense

Insurers also didn't sit on those home and auto premiums, they invested them. They also worked with re-insurers to mitigate their costs, so some of that $1.10 was "pass-through".

Other years they've paid $0.90 for every $1 in premiums they collected, but I didn't see a rate fall then.
Your comment comes off as rather snarky. Please make substantial and constructive comments on HN.
Agreed, or when Intel finally sent me a letter some six months later, which comes to the same.
> and thus doesn't tie you into a specific cloud provider

It ties you to k8s instead, and it ties you to a few company wide heroes, and that is not a 'benefit' as it's being touted here.

Being tied to a cloud is not a horrible situation either. I suspect "being tied to a cloud" is a boogeyman that k8s proponents would like to spread, but just like with k8s, with the right choices, cloud integration is a huge benefit.
An SO that places form over function would be a hard no from me
Summary: They don't really know why, just a few speculative explanations (stadium safety and the influence of "K-pop fan culture").
Saying you'll cure cancer with AI without specifying the type of cancer is like declaring you'll solve crime with Batman. Way too broad to be useful, but makes a good headline.
It's a dumb statement especially from an SRE, it's typically a comment from people that don't understand k8s and think that k8s is only there to have the SLA of Google.

For most use case k8s is not there to give you HA but to give you a standard way of deploying a stack, that being on the cloud or on prem.
Germany to investigate Russia's apparent interception of Ukraine military talks
Sadly, at worst they'll get the boot from that provider and move to another provider who they'll be able to use for years more. Even that is difficult as in most cases providers will accept a "we removed this user" or "no, we never email anyone who hasn't opted in, promise" and come back and tell you they've dealt with it.

The only way to actually get rid of it is to mark it as spam and hope enough other people do too that your provider starts treating it as spam for everyone.
I love when I have a generated email alias like “wonky.hatmaster069420@icloud.com” to make an appointment and the barber shop cashier is like “is your email address… ummm ‘wonky… harasser?’”
You can definitely do that on Android and can probably do that on iPhone.
A quick search led me to CVE-2010-2568, which isn’t in TCP/IP[1], but is an RCE vulnerability that could be triggered by a website triggering a file download and the user later opening the folder with the downloaded file in Windows Explorer. Windows XP with Service Pack 3 is vulnerable.

[1]: The CVE database has to have the worst search out of all bug trackers I’ve ever used.

(I think using older versions of Windows is fine. But under no circumstances would I connect them to the internet.)
The article, while talking about some very real problems, seems to be completely unrelated to the question of whether or not AI is likely to have that capability in the near/mid future (which is what the title implies).
I'm not surprised by this. The boys I knew that lived in Beverley Hills back in the `70s were most all arrogant assholes and so were their fathers. Their mothers were always very nice to me though and so were their daughters.
Well yeah. How the project is now you can localize anything manually if you can hear it on 4 mics surrounding it. Sometimes three.

Automatic localization. The techniques of training the model would likely be the same or similar for other similar sounds.
A lot of us would dispute that anyone that rich "earned" their money. $1bn is an absurdly disproportionate compensation for any one person's work, whatever they do. It may be legal, but it isn't right.
Stating the thesis then (repeatedly) re-stating it with a (very) slightly different wording was a red flag. Professional journalists don't write like that, but AI and schoolkids trying to pad out their essays do.

I'm guessing that a human did edit this AI output, just not very well.
It's like doing billions of code reviews based on billions of build artifacts, so that you start to notice that certain patterns are more common than others, and start to be able to reverse-engineer the compiler and source language. The best predictive model for executable binaries would be a generative model over possible source codes and then a model of the compiler.