skysight-inc/HackerNews huggingface dataset:
>> LLMs aren't making the high quality products,

And who cares exactly? The only real criteria is whether the product is good _enough_ to bring in profit. And rightly so if you ask me.

Also, far too many products build by human _experts_ are low quality. So, in a way we're more than ready for the LLM-quality products.
Americas obsession with nuclear propulsion is a large part of the problem. You can’t switch a nuclear power plant off. It’s always making noise and vibrating. These these subs are always noisier than electric units which can be totally off and totally silent, emitting nothing.

It’s politics that demands the glamour of a huge nuclear fleet. For stealth nuclear power which makes noise constantly and is nuts radiation is an inferior choice.
My money is on: increased cannabis use + social isolation (COVID+short form social media) + more awareness/less stigma of seeking treatment
sturgeon's law

also, just because someone writes poor code doesn't mean they don't know how to write good code - intent isn't always clear, and it's a mistake to assume ignorance based only on the output
Ask and ye shall receive ;-)

https://archive.org/details/MontaigneCompleteFrame/mode/2up

https://archive.org/stream/MontaigneCompleteFrame/Montaigne%...
I think this is only true for teams and apps of a certain size.

I've worked on plenty of teams with relatively small apps, and the difference between:

1. Cloud: "open up the cloud console and start a VM"

2. Owned hardware: "price out a server, order it, find a suitable datacenter, sign a contract, get it racked, etc."

Is quite large.

#1 is 15 minutes for a single team lead.

#2 requires the team to agree on hardware specs, get management approval, finance approval, executives signing contracts. And through all this you don't have anything online yet for... weeks?

If your team or your app is large, this probably all averages out in favor of #2. But small teams often don't have the bandwidth or the budget.
The BeOS guy asked too much from what I recall. I think the BeOS thing fell through before Mr Jobs quietly returned in 1997.
You can get pretty far without any of that fancy stuff. You can get plenty done by using parallel-ssh and then focusing on the actual thing you develop instead of endless tooling and docker and terraform and kubernetes and salt and puppet and ansible. Sure, if you know why you need them and know what value you get from them OK. But many people just do it because it's the thing to do...
Overfitting can be caused by a lot of different things. Having an over abundance of one kind of data in a training set is one of those causes.

It’s why many pre-processing steps for image training pipelines will add copies of images at weird rotations, amounts of blur, and different cropping.

> The more concepts the model manages to grok, the more nonlinear its capabilities will be

These kind of hand wavey statements like “practice,” “grok,” and “nonlinear its capabilities will be” are not very constructive as they don’t have solid meaning wrt language models.

So earlier when I was referring to compounding bias in synthetic data I was referring to a bias that gets trained on over and over and over again.

That leads to overfitting.
Archaeologists Uncover a Medieval Floor Made of Bones
> humans fail more randomly

And often intentionally
So you propose she donates $2B directly to some poor people she knows?

This HN comment section gets more ridiculous every time I take a look at it.
Nuclear energy isn’t CO2 free and there is still no solution for the nuclear waste.

And don’t forget that the plant operating companies themselves didn’t want to keep the plants.
first time I tried it, I asked it to find bugs in a piece of very well tested C code.

It introduced an off-by-one error by miscounting the number of arguments in an sprintf call, breaking the program. And then proceeded to fail to find that bug that it introduced.
> So for someone who may well be quite skilled at K8s administration ...

And running your own hardware is not incompatible with Kubernetes: on the contrary. You can fully well have your infra spin up VMs and then do container orchestration if that's your thing.

And part your hardware monitoring and reporting tool can work perfectly fine from containers.

Bare metal -> Hypervisor -> VM -> container orchestration -> a container running a "stateless" hardware monitoring service. And VMs themselves are "orchestrated" too. Everything can be automated.

Anyway say a harddisk being to show errors? Notifications being sent (email/SMS/Telegram/whatever) by another service in another container, dashboard shall show it too (dashboards are cool).

Go to the machine once the spare disk as already been resilvered, move it where the failed disk was, plug in a new disk that becomes the new spare.

Boom, done.

I'm not saying all self-hosted hardware should do container orchestration: there are valid use cases for bare metal too.

But something as to be said about controlling everything on your own infra: from the bare metal to the VMs to container orchestration. To even potentially your own IP address space.

This is all within reach of an individual, both skill-wise and price-wise (including obtaining your own IP address space). People who drank the cloud kool-aid should ponder this and wonder how good their skills truly are if they cannot get this up and working.
72 requests per day _per user with a naive feed reader_. This is a small personal blog with no ads that OP is self-hosting on her own hardware, so blocking all this junk traffic is probably saving her money. Plus she's calling attention to how feed readers can be improved!
It can be useful. I run a latency sensitive service with global users. A cloud lets me run it in 35 locations dealing with one company only. Most of those locations only have traffic to justify a single, smallish, instance.

In the locations where there's more traffic, and we need more servers, there are more cost effective providers, but there's value in consistency.

Elasticity is nice too, we doubled our instance count for the holidays, and will return to normal in January. And our deployment style starts a whole new cluster, moves traffic, then shuts down the old cluster. If we were on owned hardware, adding extra capacity for the holidays would be trickier, and we'd have to have a more sensible deployment method. And the minimum service deployment size would probably not be a little quad processor box with 2GB ram.

Using cloud for the lower traffic locations and a cost effective service for the high traffic locations would probably save a bunch of money, but add a lot of deployment pain. And a) it's not my decision and b) the cost difference doesn't seem to be quite enough to justify the pain at our traffic levels. But if someone wants to make a much lower margin, much simpler service with lots of locations and good connectivity, be sure to post about it. But, I think the big clouds have an advantage in geographic expansion, because their other businesses can provide capital and justification to build out, and high margins at other locations help cross subsidize new locations when they start.
There are plenty of CLI applications that need to be low overhead. E.g. postgres can call a wal archive command for backup purposes, and I specifically remember work being done to reduce the startup overhead for backup tools like pgbackrest / wal-e.
Nuclear waste in one sense is not a big problem, because it's so compact.

If you think of wind, you need to cover vast areas of a country to generate meaningful amounts of energy.
Let’s do coal then!
I'm keeping a detailed log of my activities in orgmode. But only because I have to input the hours in another system. It is interesting that even though the categories summarized are from the org-clock-table, I write small descriptions on each category for each day. For instance I might have multiple entries throughout the day for "Client X - Report", but I summarize what I've actually done in the notes. At the end of week I export it and archive with the clocktable along it, using a narrow-subtree. I also paste them in an archived section with the Year/week so I keep track of the activities and they are searcheable. So far, the clock tables themselves have been most valuable to me, especially for review purposes. Still, I believe a brag document complements this quite well and is something I plan to restart doing.
XSS injection using undeclared charset encoding and ISO-2022-JP sniffing
I’d be curious to hear more on Attempt 2. It sounds like the approach was basically to ask an llm for a score for each comment. Adding specifics to this prompt might go a long way? Like, what specifically is the rationale for this change, is this likely to be a functional bug, is it a security issue, how does it impact maintainability over the long run, etc.; basically I wonder if asking about more specific criteria and trying to define what you mean by nits can help the LLM give you more reliable scores.
> because they are intended to be consumed by apps, but are not app-specific

Well, good luck designing any standard app-independent protocol that works and doesn't do that.

And yes, you must handle two nested levels of branching. That's how it works.

The only improvement possible to make it clearer is having codes for API specific errors... what 400 and 500 aren't exactly. But then, that doesn't gain you much.
As interesting as that site is, and as much as I sympathise with the author's plight, that site's behavior is so anti-me that I'm going to ignore it whenever/wherever it pops up. I'm not trolling the author, I'm not calling them names or anything, I was just interested in the technical stuff. I wish them good luck.
Yet there is a lot of outcry that Elon Musk bought the election with his ~100 million dollars.

It's all political bias in play.
It’s madness. I push back on recording. I don’t need contemporaneous comments transcribed and stored in some database to be rolled out for ediscovery in a decade.
That was never true except in the case that the required hardware resources were significantly smaller than a typical physical machine.
Yep. I had someone tell me last week that they didn't want a more rigid schema because other teams rely on it, and anything adding "friction" to using it would be poorly received.

As an industry, we are largely trading correctness and performance for convenience, and this is not seen as a negative by most. What kills me is that at every cloud-native place I've worked at, the infra teams were both responsible for maintaining and fixing the infra that product teams demanded, but were not empowered to push back on unreasonable requests or usage patterns. It's usually not until either the limits of vertical scaling are reached, or a SEV0 occurs where these decisions were the root cause does leadership even begin to consider changes.
So you have two AIs colluding against you now. Who is holding the AI-assist to account? It's like who polices the police, except we understand human psychology enough to have a level of predictability for how police can be governed reliably, we don't understand any truths about an AGI because an AGI will always have the doubt of it deceiving, or even making unchecked catastrophic assumptions that we trust because it's beyond our pay-grade to understand.

There are so many ways we have misplaced confidence with what is essentially a system we don't really understand fully. We just keep anthropomorphizing the results and thinking "yeah, this is how humans think so we understand". We don't know for sure if that's true, or if we are being deceived, or making fundamental errors in judgement due to not having enough data.
>Boxing for example could calculate the amount of kinetic energy brought to the table and how much of it landed or was sidestepped. How much was absorbed? Not easy to do, but also not impossible

It would be pretty difficult to do in a combat sport without sensors. As I understand it fencing has participants' blades wired up for this exact reason. How would you measure how hard a punch landed from a distance? You could put sensors in the gloves, but some of the time the punches bounce off the opponent's forearms, so you could get a false 'powerful' rating from a blocked punch.

Worse, some of the best punches aren't the most powerful in a kinetic sense, but just happen to very accurately land in the right spot on an opponent's chin. Or they're well timed and the opponent doesn't see it coming, so their surprise makes the strike more damaging. Even if you could precisely measure punch impact to the head from a distance, you'd be missing out on some excellent punches that are less powerful but set up by accuracy & timing. So yes it's basically impossible to measure in any way but subjectively
While it might be nice if the article spelled out the header, I do believe that there is more than implication present.

> 00:04:51 GET /w/atom.xml, unconditional.

> Fulfilled with 200, 502 KB.

> [...]

> A 20 minute retry rate with unconditional requests is wasteful. [...]

And If-Modified-Since makes a request conditional. https://developer.mozilla.org/en-US/docs/Web/HTTP/Conditiona...
> 72 requests per day is nothing and acting like it's mayhem is a bit silly.

72 requests per day per IP over how many IPs? When you start multiplying numbers together they can get big.
Actually the profession is already taking big hit. Expecting at least partial replacement by LLMs is _already_ one of the reasons for the reduction of new jobs. Actually _replacing_ developers is one of the killer apps investors see in AI.

I'd be impressed if the profession survived unscathed. It will mutate to some form or another. And it will probably shrink. Wages will go down to the levels that OpenAI will sell their monthly pro. And maybe 3rd world devs will stay competitive enough. But that depends a lot on whether AI companies will get abundant and cheap energy. IIUC that's their choke point atm.

If it happens it will be quite ironic and karmic TBH. Ironic as it is its our profession very own R&D that will kill it. Karmic because it's exactly what it did to numerous other fields and industries (remember Polaroid killed by instagram, etc).

OTOH there's no riskier thing than predicting the future. Who knows. Maybe AI will fall on it's own face due to insane energy economics, internet rot (attributed to itself) and what not.
That the point is being repeated to no effect ironically illustrates how most modern people (westerners?) are detached from reality with regards to food.
Energy costs are now back to levels seen before the Russian war against Ukraine, so it is unclear why the Energiewende should be at fault.

The German malaise is more likely tied to the shift to EV, the weakness of Germany's car industry and a general slump in China which are all hitting at the same time.

An aging population and an increase in social benefits are likely also part of the issue.
These accounts like yours and this report of PTSD don't line up. Both of them are credible. What's driving them crazy but not Old Internet vets?

Could it be:

- the fact that moderators are hired and paid
- that kids are young and a lot more tolerant
- that moderators aren't intended audiences
- backgrounds, sensitivity in media at all
- the amount, of disturbing images
- the amount, in total, not just bad ones
- anything else?

Personally, I'm suspecting that difference in exposure to _any kind of media_ might be a factor; I've come across stories online that imply visiting and staying at places like Tokyo can almost drive people crazy, from the amount of stimuli alone.

Doesn't it sound a bit too shallow and biased to determine it was specifically CSAM or whatever specific type of data that did it?
What happens when it passes? I've never had that kind of thing, but I did find "internal family systems" therapy useful and have wondered if those extreme conditions might be extreme manifestations of the same concepts. If so, there may be a way to tame that stuff.
I count myself as a pretty decent fan of boxing. To argue that the rules are not already being gamed is pretty shallow. Winning by points is pretty much standard. Providing one additional judge that auto-tallies wouldn't kill the sport.

And I do believe the sport would benefit from, say, 3d reprojection to see a different view, or a heat map of hit vs throw locations, or a reproduction of movement throughout the ring.

Other sports have had these deep stats for a long time, and boxing has what, jab counts, points, and knockdowns? Come on. I love the sport and I love data.
Yes, it’s a cultural problem. Europe has had stagnant economies before—indeed, that was the norm for a lot of the 20th century. What’s disrupting everything is immigrants.
Fair enough. For the record, I'm also planning to build my own very mini "framework" based on just lit-html.

Is yours shared publicly anywhere? I'd love to check it out for inspiration.
That much is clear, yeah. The VPN they use may not be a service advertised to public and featured in lists, however.

Some of the new traffic did come directly from Tencent data center IP ranges and reportedly those bots signed themselves in UA. I can’t say whether they respect robots.txt because I am told their ranges were banned along with robots.txt tightening. However, US IP bots that remain unblocked and fake UA naturally ignore robot rules.
Don't forget judges, especially the ones in this case ...

And it used to be priests who had to deal with all the nasty confessions.
"Methanol is always a purposefully added substance at some point if it is anywhere near poisonous levels."

That's usually true. Adding methanol to ethanol can be either deliberate or accidental. Where I am (Australia) methanol and pyridine used to be added to ethanol as a denaturant so it could be sold without liquor tax and it was sold as 'Methylated Spirits' and labeled 'POISON'. If I recall the amount of methanol was 15% and the pyridine was 3%. Methanol was set at 15% with the deliberate intention of making the 'spirits' toxic and the pyridine to make it foul tasting (and pyridine itself is also toxic). At those percentages both denaturants were similar enough to ethanol as not to interfere significantly with its primarily purposes—as a solvent, fuel, etc.

Nevertheless, that didn't deter diehard drinkers/alcoholics from consuming methylated spirits and the effects on their health were catastrophic—blindness and death.

Several decades ago both methanol and pyridine were removed and replaced with denatonium (aka Bitrex) as the denaturant, which is not toxic at the level necessary for its purpose. Nevertheless, the product is still sold as 'Methylated Spirits' with the fine print calling it 'ethanol solution 95%, UN 1170', and the warning changed from 'POISON' to 'CAUTION'. The logic behind the change being that it was 'safer'—read it cost the State less in medical expenses.

I think the UK has done something similar and no doubt a number of other countries have followed suit, except I believe the US makes ethanol harder to get and usually substitutes isopropanol/rubbing alcohol for domestic use (someone in the US please update me on the rules there).

Since the advent of denatonium as a denaturant, it seems to me there is no need to add methanol and I reckon it ought to be highly illegal to do so. If ethanol/methanol mixtures are needed for some purpose then they should be strictly labeled and denatonium a mandated additive.

What concerns me is the accidental addition of methanol to ethanol (to 'Methylated Spirits'). I use a lot of ethanol in the form of Methylated Spirits for cleaning and as a solvent as it's a much cheaper substitute for isopropanol and I've noticed occasionally that its odor is very different (once every 3 or 4 months on weekly purchases). In fact, I've noticed the odor of formaldehyde on more than one occasion (and that's not the only impurity I've detected by nose).

This tells me there's very little control on the distribution of industrial solvents (in this class that is). I'd suggest tanks/tankers, etc. aren't properly flushed when changing product and or such. If distribution equipment isn't being cleaned properly then people aren't being careful and worse could easily happen.

From my experience it seems to me it's still a very risky business to assume that 'industrial' ethanol is actually just that (95% ethanol, 5% H2O and trace denatonium). There's no way I'd ever risk drinking the stuff—that is assuming I could stand the taste of the excruciatingly bitter denatonium.

I'd be interested to know how other countries now handle the rules in regard to ethanol distribution.
1 is super interesting.

I’ve found it’s nice to talk to an LLM about personal issues because I know it’s not a real person judging me. Maybe if the comments were kept private with the dev, it’d be more just a coaching tool that didn’t feel like a criticism?
<ctoHatTime>
Dunno man, it's really really easy to set up an S3 and use it to share datasets for users authorized with IAM....

And IAM and other cloud security and management considerations is where the opex/capex and capability argument can start to break down. Turns out, the "cloud" savings comes from not having capabilities in house to manage hardware. Sometimes, for most businesses, you want some of that lovely reliability.

(In short, I agree with you, substantially).

Like code. It is easy to get something basic up, but substantially more resources are needed for non-trivial things.
Apple Explores a Face ID Doorbell and Lock Device in Smart Home Push
I use them to:

• Build toys that would otherwise require me to learn new APIs (I can read python, but it's not my day job)

• Learn new things like OpenSCAD

• To improve my German

• Learn about the world by allowing me to take photos of things in this world that I don't understand and ask them a question about the content, e.g. why random trees have bands or rectangles of white paint on them

• Help me shopping, by taking a photo of the supermarket that I happen to be in at the time and ask them where I should look for some item I can't find

• Help with meal prep, by allowing me to get a recipe based on what food and constraints I've got at hand rather than the traditional method of "if you want x, buy y ingredients"

Even if they're just an offline version of Wikipedia or Google, they're already a more useful interface for the same actual content.
Governments have long made repeating some unrecorded conversations illegal. Those conversations are called “privileged communications”. For example, a doctor or a lawyer can be charged with a crime for an unauthorized disclosure of a privileged communication, even if the communication was not recorded.

The problem with two-party consent laws is that they make illegal ONLY the recording of conversations that the participants are otherwise free to disclose to others. In those situations, the government CANNOT claim it is seeking to protect anyone’s privacy, but only people’s “right to lie” about their conversations. That is NOT a legitimate governmental interest.
I doubt it was idiotic but simple corruption.

The coal power plants are the reason for high prices and huge profits for the energy companies.

The „botched“ exit from the exit from the nuclear exit brought them additional billions in compensation.

People like Söder, who now want nuclear energy back, threatened to resign if the shutdown is delayed.
Of course, they don't want nuclear waste anywhere near them, nor do they want wind turbines or power lines.

And they were in power for 16 years.

They then left the problems to their successors, who are now being blamed for it.

It's at least partly true of the SPD
Fully agree. And if you want to take it to the next level (and have a large budget), Oxide [0] seems to have neatly packaged this into a single coherent product. They don't quite have K8s fully running, last I checked, but there are of course other container orchestration systems.

> Go to the machine once the spare disk as already been resilvered

Hi, fellow ZFS enthusiast :-)

[0]: https://oxide.computer