skysight-inc/HackerNews huggingface dataset:
Why does it matter what actually happened? Can you give a concrete example of when you care the exact sequence of experiments, false starts, and refinements that a feature went through before making it into a PR?
They have a Safari extension that will redirect the searches to Kagi, but you can still manually go to Google.com and do stuff.

https://help.kagi.com/kagi/getting-started/setting-default.h...

Their Orion web browser is pretty nice. I’ve run into a few minor quirks while evaluating it, then tried Firefox, then Safari again, but I keep getting pulled back to Orion.
> The scandal is another blow to the automaker, which had admitted in April to violating standards on crash tests on more than 88,000 cars, mostly sold under the Toyota brand in countries such as Malaysia and Thailand.

Seems fair to mention Toyota in the headline, since that was the brand name people thought they were buying when they got one of these cars.
The thing to do is to repair stuff as it breaks or wears out. In other words, you should be paying out money almost constantly. Naturally you should also prepare for the big stuff, like painting or re-roofing.

The rule of thumb like 1-1.5% per year is a reasonable sort of figure.

We learned this the hard way, early in our marriage. Every year we said 'This is the year of the house' and then changed our minds and travelled instead. Ten years down the track, we realised that all those little costs never went away, but we now had to pay all of them in one hit.

I have another rule of thumb with houses. "Every time you move from one house to another, it will cost you at least 10-20 grand" on top of the actual moving costs. Your furniture won't fit, so you have to buy other furniture that does. Or the toilet in your 'new' house suddenly dies, or your trusty old fridge dies from the shock of moving, or you need to replace your car because some changes occur in your 'new' lifestyle, or something else ...

The biggest thing I hate is when a major appliance dies. You are forced to shell out a lot of money, but you're no better-equipped than you were a few weeks ago.
As a life long Californian, when people tell me California is running out of water my response that California is running out of cheap water.

Calfornia farmers pay $30 to $120 for an acre foot (325,851 gallons or 1,233 cubic meters) which is ridiculously cheap and is wasted growing things like rice (California grows about 20% of the rice produced in the U.S. each year.)
Paying rent by credit card is common in the civilized world. The only exception I know is the US, where I had to use paper checks, as if we're still stuck in 19th century...
I wonder why they didn't include Linux since the project they're building is Go? Most CI tools, I believe, are going to be Linux. Sure, you can explicitly select macOS in Github CI but Linux seems like it would be the better generic option?

*EDIT* I guess if you needed a macOS specific build with Go you would us macOS but I would have thought you'd use Linux too. Can you build a Go project in Linux and have it run on macOS? I suppose architecture would be an issue building on Linux x86 would not run on macOS Apple Silicon but the reverse is true too a build on Apple Silicon would not work on Linux x86 maybe not even Linux Arm.
The tragedy of #OxygenToxicity is that the antidote was known, and was becoming normal medicine, but got forgotten around 1950/1960.

The tragedy of 2020 is how the doctors tried to help their patients with toxic amounts of oxygen. I referred to that episode as the tragedy of #MedicalHyperventilation.

I’m optimistic that regeneration will be the next breakthrough in medicine.
The reason you are asving this is because git is so aweful at managing many tiny commits. So you work around it by squashing. However this is a defect of your version control system.

back when I used hg small commits were not a problem as the branch name remained after the merge and so mostly we were able to treat branch names as the squashed whiae still having acces to the typo commit if needed.
please reread my comment. You have missed the point of it, if you think I'm asking farmers to fix this.
Why don't Muggle-born wizards use Muggle technology to fight Death Eaters?
I think it's partly because the audiences are often not familiar with those statistics details either.

Most people hates nuances when reading data report.
Yeah wifi works better when your ap is shouting from across your property.
interestingly chocolate milk is often made from the yellow milk.
Oooooh, sorry, sorry. I was thinking more about the CSS !

But even so I didn't check out `-H`, I thought it was just the help flag and immediately thought the comment was a bit lacking, my bad.
Please renew your Buypass ACME (Go SSL) certificates issued before December 22 12:00, 2023.
We have identified an issue within our systems so that these certificates do not comply with certificate issuance requirements. We have corrected the issue, but all still active Buypass ACME (Go SSL) certificates issued before December 22 12:00, 2023 must be revoked.

Renew your affected certificates and install them immediately to ensure that your services continue to be available.

If you need support for the renewal, please comment here on the ACME Community where our staff and Community members will be able to assist.

We apologize for any inconvenience this may cause.

Buypass as
Get yourself some Cougar Gold, it's amazing. Yeah, I know, "it's in a can" but it doesn't matter. In fact, get a couple of cans and shove some into the back of your fridge to age for a year or three and it becomes even more amazing!

https://creamery.wsu.edu/cougar-cheese/flavors/

https://en.wikipedia.org/wiki/Cougar_Gold_cheese
I'm a Gentoo daily driver and I'm also looking real hard at Guix. I already live inside of Emacs, having everything in Lisp seems kind of nice.
Yeah, I was looking at the histograms too, having trouble comparing them and thinking they were a strange choice for showing differences.
Interesting. I'll give it a try, thanks. At first glance it reads like too much magic that I'd have to undo manually, but if it works reliably, it would save some time. Though usually it's not much work to figure out which commit to reference in `--fixup`. In short histories, I usually just use `HEAD~<n>`, instead of hashes.

BTW, thanks for all your open source work. <3 You're an inspiration!
To your point the “Hello World” Win32 C example in Charles Petzold’s earlier editions of Programming Windows is infamous.

http://www.charlespetzold.com/blog/2014/12/The-Infamous-Wind...
If open source devs make a living off it by charging users for money (or PII), the devs should be liable for the code they are selling. It does not matter if it is open source. Whoever makes a commercial offering based on that software must be liable.
How is multipath going to tell radios how to roam between cells?
I recently ordered a new car from Daihatsu, and they called and asked if I still want the car or would like to cancel the order in light of this news.

I’m honestly not that concerned about the safety of the vehicle. They’ve been cheating on safety tests for a long time apparently, and in the real world I don’t think Daihatsu cars have fared much worse than other manufacturers in crashes. It’s also got a lot more safety tech than the car it is replacing, so I think it would be a step up in safety regardless.

Instead I’m more just concerned with the future of the company, whether the resale value of the car will drop, etc. I also do find the scale of this fraud pretty shocking, and don’t want to reward this behavior by purchasing from them.

So probably I will cancel and buy a Honda or Suzuki instead.
I have no idea how you interpret it this way.

How does being liable for damages caused by software or services you sell equate to being an idiot? I just see it as the normal way to do business, and the reason why limited liability (the way I’ve been doing business for more than 2 decades) exists.
And with some success too: Cocoa/AppKit is still hanging around as an actual API that’s still being used by application programmers after 30 years, unlike winapi.
> At the top, we have a not strictly POSIX compliant, multi-argument shebang:

#!/usr/bin/env gsed -nE -f

> It may break on some fringe UNIX implementations, but it is necessary for the system to work.

I think I can vaguely remember that I had issues with something like this on a bog-standard linux. env has the -S option though, which should help on systems where multi-argument shebangs don't work.
Doesn't help with water treatment or sewage handling though.
It is known...by all kids up to the age of 8. Right about the time the truth about Santa Clause, Easter Bunny, and the Tooth Fairy are known.
Saying that ml models aren't open source because you don't have the data is like saying doom isn't open source because you didn't provide a proof the fast inverse square root works: https://en.m.wikipedia.org/wiki/Fast_inverse_square_root

LLMs are just very large magic numbers. That's all there is to them.
I ran Gentoo on my desktop from about 2005 to 2008. The last year of that period I was without Internet access, and when I tried to update the system after being online again, it broke (not surprising, I heard similar stories from users of other rolling release distros since).

But it just so happens I set up a virtual machine running Gentoo but a few days ago, with no clear idea of why or what for. What a remarkable coincidence.

Gentoo requires the user/admin to put in a lot more work than mainstream distros like Debian, but in return you get such a high degree of control and choice that the system, once it's up and running, feels more like a pet than a piece of software.
"Comedies involving diamonds and/or nuclear weapons"
Show HN: Neutral.News – neutralize any news source
submit a URL (or download the extension) for neutralization. Strips bias and emotional language and delivers just the objective, salient facts. Great for browsing biased internet sites.
Looking for critical feedback and sites that don't work correctly. Working on an automated version that displays the last 10 stories or so submitted.
Discarding ideas out of hand is easy & cheap. Why do you think this so absolutely unacceptable an idea?

A factory seems like a big space where there could perhaps be a predictable well known radio spectrum, and where that spectrum could reliably be monitored for stability. Unlike most spaces, there's a lot of possibilities for controlling the environment well, if you wanted; no end-user devices allowed, nothing but known systems.

This feels like you could very quickly get to some kind of known state. "We will be able to send priority signals within under 2ms." Or some such quality metric. Keep a signal analyzer going: any time this isn't met, everything goes into an independent failsafe shutdown mode until the issue is debugged and started up again.

Our instincts to judge & discard ideas & possibilities is so dangerous, is such a deep human peril. Your instinct feels like it comes from a good place, feels correct, but ultimately, this is acting in fear uncertainty & doubt, & your execution rests on no contentions other than it's own self certainty.

I think we must be much more thorough in our thinking & arguing, must not leap to discard ideas so quickly totally & casually; FUD must be rooted out deep within ourselves & challenged. Let not progress be onstructed by meek wills.
https://web.archive.org/web/20231229204119/https://www.econo...
I've asked dang et al to release data on astroturfed threads and haven't heard any response whatsoever. They have the data but aren't willing to share it seems. Why is a different question. As persona management (sockpuppetry) tech gets better it becomes much more difficult even with the data to prove.
In my opinion if one could choose between a well executed and instant rebase versus a well executed and instant merge, one would be a fool not to choose a rebase every single time.

In practice too, I also almost always choose rebases, BUT there are a few caveats here that are worth making…

As a general rule rebases for more than a small number of commits in cases where conflicts are non trivial can take significantly more time and patience for the developer performing it. Instead of fixing the conflicts in one swoop, you have to sometimes resolve conflicts repeatedly in the same areas of code. If the conflicts are extensive this can be a very unpleasant experience even for experienced developers.

For less experienced or less skilled developers each of these conflicts poses an opportunity to mess up. Since there are more of them when rebasing, there are also more opportunities to mess up. If the developer is in a rush or is simply impatient, I would also expect them to mess up more in a rebase than a merge.

Yes, ideally we wouldn’t have massive branches that need to be rebased with many conflicts, but in practice if you are working on a codebase where a lot is happening frequently by lots of people in the same parts of the code or code is moving around, there are often no really good alternatives. While perhaps more changes can be made incrementally than people often admit (especially if you include feature flags and the like to allow for transitions — though those can come with their own pitfalls), in practicality, not everything can in practice be done without having longer branches (and not having unreasonably large changes in a commit). Sometimes large changes just need to be brought in together.

Slow reviews or at least slow code reviews at the same level of effectiveness in the review can pose problems as well. If you want it properly reviewed in the safest possible way you really want no new code in the branch being merged to after the review begins — allowing a clean fast forward merge from the rebased branch, but that can be impractical in some codebases with a lot of activity.

Merges can still be messed up and until recently it was quite hard to even see the merge diff to debug a bad merge, but there are admittedly fewer steps where you can mess up.

All that said, I’m still a huge advocate of rebasing, but I get it that not everyone is up to the task. Sadly most developers have tons of awful, broken, and incoherent commits on their own branches that they never clean up. Until you can convince them to at least do fixups and cleanup the commit histories on their on branches with rebasing, arguing for rebasing over merges towards trunks is pointless.

It requires more from the developer upfront. If your developers are good it will require much less from a maintenance perspective but the reality is that having a team of capable developers who are willing to do the work is not something one can take for granted in most places.
Well, the difference isn't that great. You wrote: “the memory associated with the old version could be freed once nothing would want to access it again.” So all it really takes is something wanting.
I've talked to the Hooks folks, and they have disaster recovery storage plan for their cheese spread throughout the country to survive various natural disasters.

edit: 15yr Hooks is heavenly too
Just in case it wasn't obvious from the article, there is a tar file with STL files for the controller from 'Thingiverse' and lightburn files for the wood parts as well as the 48x32 include file that drives the display and reads the joysticks, this is used to build all games upon. The file is here: https://jacquesmattheij.com/48x32.tar

If you make any improvements I'd love to hear about them, soon I'll have a gitlab repository up with all of the code related parts as well as a schematic for the hardware (though it is so simple that if you just read the include file you'll know exactly how to hook it all up).

Best of luck with any re-creation efforts, if you run into trouble feel free to mail me (email in profile).
They are all Unifi APs from 2 different upgrade cycles. 3x UnFi AC Pro and 3x Unifi NanoHD.

After I got the newer NanoHDs, I just kept the older AC Pros around for 2.4Ghz devices and exterior coverage.

Same SSID and they are all hooked up the same controller etc, so clients can roam.
Happy 14th Birthday, KrebsOnSecurity
Exactly. To analogize to history history: OP wants the version control history to look like a collection of primary sources. Here's the president's daily calendar, there's the letter he received on April 24 from a small child in Wisconsin. In this model, it's up to future code historians to piece it all together into a story.

When I go back and look at the git history, I would much rather have had someone do the work of compiling the story for me at the time. Commits are your chance to document what you did for future programmers (including future you). If you insist on them faithfully reflecting every change you made over the course of three days, then future you will have to piece that all back together into a coherent story.

Why not take the chance to tell the story now, so that future you can skip all the false starts and failed experiments and just see the code that actually made it into main?
And what?

I've had cheddar cheese in the UK. I've had cheddar cheese in the US that was imported from Cheddar England. I've had cheddar cheese in the US that was made in the US. I have absolutely no idea what all the hand-wringing is about. What's wrong with American cheddar? Is there some sub-par brand out there that is sold in the majority of grocery stores in coastal America but not in the grocery stores in middle America? Are we just up in arms because some brands add some coloring to it?
VSCode is noticeably laggy on my 2019 MBP 16in to the point that I dislike using it. Discrete GPU helps, but it still feels dog slow.
The US picks extremely difficult battles to fight in a way its citizens deem acceptable, and they aren't wars of conquest. Those factors are going to make it very hard to point at a simple winner.
Thanks for linking to the actual directive!

In light of it, I think the article I found didn’t link to it out of sloppiness, because their summary seems reasonably accurate to me, and the fine article didn’t link to it because they want to spread FUD, as the text you quoted directly contradicts some of the fear mongering in the original article.
The next innovation I expect to see on HN is a service that, on a set schedule, gathers articles about a set of topics that you follow, prints them out onto paper, and delivers them to you as a bound volume for easy perusal.

This has a number of advantages for privacy (there's no way for the publishers to know how much time you spent reading each story), offline-first availability (dead-tree is the ultimate), and sharing (you can hand someone the entire volume rather than just a link to it, and they get the whole contents, all offline).

It really sounds like it could be the hot new thing, if only some forward-thinking VC would invest in it.
Cheddar isn't American, it's English. America hasn't "allowed" anything here, because they've been coloring it in England since the 17th century.

And you're wrong about "yellow cows", in a way. Cheddar was first made in the village of Cheddar in Somerset, England, and the milk did have high levels of beta-carotene because of the local breeds eating the local grass. The original cheddar was yellow without anybody adding coloring at all.
Honestly, I think that a lot of people on HN are just difficult. I don't know whether it's learned or biological, but there's clearly a driving urge for some of these folks to just argue the most pedantic nonsense until the oxygen is all gone.

I find it hilarious that someone would be deeply offended by AI colorization of scenes from 100+ years ago, which are impossible to recreate and many showing glimpses into the past which would otherwise be mostly forgotten. The reason that they get millions of views is because it gives modern people the opportunity to make the shocking realization that times change, but these people are not so different from us.

One has to wonder if someone angry about the introduction of artificial color is also angry to realize that actors are playing characters and comedians are not just making up funny jokes while you watch.
Please provide receipts or contracts showing you purchased said software from them, before you can sue.
Ice cream used to be made of polar cows milk until the 50s. The world of food is truly bizarre.
Dropbox Dash: Search All Your Apps, Tabs
Yes, that is well known, but it doesn’t prevent the issue in TFA.
Portal 64: First Slice, is out of beta [video]
In hungary the brand name of KUKA (of orange robot arm fame) become genericized to mean any kind of trash bin. I heard it happened because they produced the first widely used garbage trucks in Hungary and they had their brand name written on the trucks (or perhaps even on the garbage cans, depending on where you read the story). So much so that the garbage trucks are called “kukás autó”, and the profession of garbage collection itself is just called “kukás”.

A long long time ago I built a robot out of a garbage can to celebrate this weird connection: https://youtu.be/LFD63moEUkw?si=qDQ54dVNIvOG8nrM
Cleo the Mysterious Integral Solver
Scientific American:

https://www.scientificamerican.com/podcast/episode/podcasts-...
I dunno. Did you take a poll or something? There are tons of small local creameries and chocolatiers around.
I have three 5/AC access points in my house. All broadcast the same two SSIDs: 2.4Ghz+5Ghz and 5Ghz only). I have 802.11r Fast Transition enabled in OpenWRT to improve roaming, but have never quantified a benefit. Each AP is set on different channels to minimize overlap.
But notice that this feature was present in several generations of the chip.
Well, what will a future war look like?

We're never going to fight WW2 again, because all the great powers have nuclear weapons now. The US army will never take the field in a straight up slugfest against Russia or China.

So that leaves non-nuclear regional powers. But you simply don't need a whole-of-society mobilization to fight Iran. The phase of active combat against Iran will not take years-- it won't take months.

If we really needed to, we could be building millions of Jeeps again. But we don't need to, and won't need to.
I don’t really have a usecase for even more battery life, so I’d rather have it run faster
To add to that: throughput isn’t just about bandwidth, but also latency (BDP) but more importantly (in the case of WiFi) jitter and packet loss.

Even if your WiFi supports 1Gbit most of the time, tcp will throttle back to slow start (IIRC - the linear one) upon packet loss. And time to recovery depends on RTT. When I measure I always get inconsistent results on WiFi, whereas ethernet+fiber is butter smooth.
Does it?

My only gripe is that for whatever goddamn reason Android isn't able to detect what specific subset of WPA2 Enterprise config the AP actually wants/supports and the UI seems to constantly change around over the years, a common annoyance in large campus networks where the admins don't stay on top.
Good to know I have commercial options for overcoming my laptop shame at interviews. /s
If you shop at Costco, try their aged Balderson cheddar - 2 years or older. Incredible! (Though that may be canada-only, I'm sure the US Costco carries something similarly great)
Hi, Thanks for the interesting comparison. What I would like to see added would be a build on a 8GB memory machine (if you have one available).
If the open source devs charge for their software, they should have the balls to accept the liability for whatever they are selling.
`nvim scp://devhost/main.c`
The internet is made of tubes. And tubes are made of circles.

2024 is the year of PHP.
> Application error: a client-side exception has occurred (see the browser console for more information).

When I open the page.
Web browsers can render more than just HTML, can't they? Plain text at the very least, many do PDF as well.

That function really seems like it should be in the browser anyway. The server serves, the renderer renders.