skysight-inc/HackerNews huggingface dataset:
Logic and SRAM are completely different things in this context. SRAM actually has had almost zero scaling since N7 while logic has more than doubled in density (2x theoretical / 1.5-1.6x real-world shrink at N5 relative to N7, for example, and then N3 gives about 30% real-world shrinks to logic, although that’s less than expected and the good shrinks are going to come from the later N3E node).

As a result we will probably see the pendulum swing back from cache-heavy designs. Going ham on cache was an obviously advantageous strategy at 7nm, you can basically look at it as N7 having been two full node families ahead of the curve on sram density (Samsung is only catching up at 3nm/2nm). But since SRAM hasn’t scaled at all in the last 2 nodes it’s becoming comparatively more effective to spend your transistors on logic instead. You still want big caches of course (and cache can be easily stacked ala AMDs v-cache) but it’s more worthwhile to spend more heavily on logic than it was on 7nm.
I don’t think I follow how that changes the above case.

The per device key can be the password the user sets up. They can remove, change, or share it when they go to resell the phone.
casualty of the failure to build legal remedies and systems that reflect the Internet’s actual architecture.

Help, I am drowning in the irony of Cloudflare of all people making this statement after being the company who normalized service providers kowtowing to internet mobs. Sending threats to the family members of Tier 1 provider executives to get sites blackholed is now a thing because of Cloudflare and they're going to complain a court ordered a block of eleven IP addresses.
> This isn't a space with room for errors, certainly not ones this big.

It is. Comparable systems can and do have errors. You can attach a bunch of nines as an SLA there and Solana would do pretty well in the last months. Especially because it’s only competition in the scalable blockchain space is itself.

> > This does not mean the design is centralised: it's just that it's a peer-to-peer design with bugs. Like all software, ever.

> It does mean it's centralized.

ok.
Allow me to save you a click:

"established scientific facts can be identified via a solid (>95%) international scientific consensus"
Is there such a thing as a scientific fact?

Seems to fly in the face of the philosophy of science, which typically has science as a process of ruling out things that are incorrect and incrementally approximating the truth.
Sort of. We initially fed our cat on demand, but at some point switched to feeding it at set times during the day. The cat adjusted to that, and suddenly all his daily activities - including playing and sleeping - started following a consistent schedule.
I've paid and used Kagi for about six months. I used DDG for a while, but I found myself putting !g after every query (especially when looking for answers relating to programming). With Kagi I very, very rarely need to use Google.

It has some nice features, like lenses, URL rewriting, and the ability to bump sites to the top.

I have a lens for programming. It shows only certain sites, like GitHub and Stack Exchange, and I enable it when appropriate.

For URL rewriting, I have Kagi set to rewrite URLs from Twitter and Reddit to my own self-hosted instances of Nitter [0] and Teddit [1], so that when I open a Kagi result that would've gone to twitter.com, it goes to nitter.mydomain.com, which lets me use Twitter without an account.

Lastly, I use the site bumping feature to move Wikipedia results to the top.

[0]: https://github.com/zedeus/nitter

[1]: https://github.com/teddit-net/teddit
I think companies could test their interview process this way. Fill some positions by choosing from the candidate pool at random (there could be a baseline filter to ensure a minimum level of competence) and compare the random hires with the regular hires to see how much of a difference the interview process really makes.
There would be a multitude of discordant responses to alien contact. Think of all the eccentric tech billionaires, fringe social groups, and isolated national regimes who would feel impelled to pursue their own vision of how contact should proceed.
It's not. In general, people who say it is fall into one of three groups:

1. People who want to censor and/or surveil other people's devices and traffic. These people hate DoH because the entire point of it is to protect against them doing so, and by running over port 443, it's really difficult for them to block it. This is the group that people who say DoH would be a good thing if only it used a network-provided DoH server, or that they wish DoT would get used more instead of DoH, usually fall into.

2. People who have a workflow that it breaks. In most cases, there's some setting or workaround for that workflow that still lets you use DoH for most Internet queries, though.

3. People who say it's making the Internet more centralized or bad for privacy. These arguments are valid to say "don't everyone use Cloudflare as your DoH provider" but not to say "don't use DoH even with other providers", since there's no reason DoH servers have to be any more centralized than regular DNS servers.
Okay, but this whole essay is just a well-argued, well research personal opinion. That's kind of what an essay is. I'd like to know what I'm supposed to do with it.
I am not an expert but I think there are ways to safely co-sleep, but chronically sleep-deprived parents tend to not be able to follow the rules consistently
Babies cry because they have little other ways to communicate. And yes, generally it is because of something negative.

That negative could be 'leave me the fuck alone and stop bothering me' though, just in baby language - crying. Yes, even to a parent.
Can you tell me what happened to Tornadocash again? Besides that, if privacy was at all a concern for crypto bros we’d see something like XMR be the default from the start.
Previous submissions (note: they're frequent):

https://news.ycombinator.com/from?site=kagi.com
I was about to ask exactly this. I did a few iterations and it converges pretty fast, nice to know someone went the extra mile to see exactly how many iterations it would take. Annoying if you were doing it by hand, but not that bad really.
The article is way too opinionated about „golang is doing it wrong“ for a decision that neither has a right or wrong.

Nagle can make sense for some applications, but also has drawbacks for others - as countless articles about the interaction with delayed acks and 40ms pauses (which are pretty huge in the days of modern internet) describe.

If one uses application side buffering and syscalls which transmit all available data at once, enabling NODELAY seems like a valid choice. And that pattern is the one that is used by GOs http libraries, all TLS libraries (you want to encrypt a 16kB record anyway), and probably most other applications using TCP. It’s are seeing anything doing direct syscalls with tiny payloads.

The main question should be why LFS has this behavior - which also isn’t great from an efficiency standpoint. But that question is best discussed in a bug report, and not a blog post of this format.
>You can only get away with that sort of debt for so long.

Kevlin Henney has recently suggested we should stop calling it technical debt, and start calling it technical neglect instead.

Managed debt is a useful thing, if you ignore debt, you end up out of business.
I should probably have also pointed out that Sol has a greater Nakamoto coefficient than eth.
Can anyone else compare this to you.com, which is a similar concept in regards to increased privacy? I plan to sign up for Kagi tomorrow, but having used Kagi until I ran out of search on the free version, you.com seems to offer more features specifically in regards to YouChat and ability to preview certain results. It's also free for right now but wonder if they plan to go the ad-supported route in the feature, which would be a deal breaker for me over just paying a monthly plan like you do with Kagi.
Watch him talk with Bret Weinstein who is an Evolutionary Biologist. It might give the ideas a lot more justice than that.
Sortilege is a good thing. Right now we have an ostensibly democratic system where elected representatives take part in another election among themselves about which one of them gets to have pre-emptive veto power over all legislative proposals for 2-6 years (in the US).
Has there ever been an advertising-supported product that turned out to be respectable/useful for its users in the long run?

We all know how Google turned out, and that's despite themselves admitting early on that an ad-based search engine would have misaligned incentives.
The default link color wasn't made for dark mode, therefore it stands to reason that it will not have an optimal readability then. It hasn't suddenly become unreadable, the requirements changed. And under the new requirements it is not readable for many people. I wonder if calling a color scheme that arguably reduces eye-strain and increases battery life on modern monitors an abomination is a good idea. These kinds of stances usually result in unconstructive arguments.

Luckily we aren't constrained to a dark mode, or a light mode for that matter.
So everyone can choose what they consider the best for them.
Potentially this has a hole: if a wrong time is set initially, then wrong certificates may be trusted, so spoofed TLS sessions with compromised (and expired) certificates would work, potentially giving a way to install something malicious. It requires some massive spoofing on the outside though.

If the initial NTP addresses are within a datacenter LAN (say, 10.x.x.x, etc), they are likely harder to spoof. Should be fine their case (servers).
No, it's just standard web developer laziness. They haven't made it IE only, they just broke the less popular browser, and likely anything else that is not chrome/blink, because chrome/blink is the new IE: its bugs define "correct behavior" it shipping something means "it's standard", no different from the "IE is the internet" era (and just like chrome there was a long period where IE was the best browser, before devs started targeting it alone).
im thinking in the context of pre-judeo christian society.

these tablets are close to 4000 years old.

being possesed by gods was an in thing, a believe demons were a prechristian idea as well, so if witch, and demon could be interchanged somehow, i think that fits the era.
This would be sufficient if features were a yes/no binary of supported or not, but sometimes browsers implement features but get them wrong, or incompletely.
I'd like to use Kagi but I can't make it a default search engine in Safari. Until then, DuckDuck it is!
Honest questions:

1) What are the downsides to having your search history monetized? Is it the ads served to you across websites that use the same network?

2) Does personalized weighting lead to echo chambers like, say, Reddit?

I need to try this out but I'm curious about how they will defeat SEO. To me, that is what has made Google search results less helpful to me the past several years and would lead me to look elsewhere.
> Was there ever a missed approach due to a cell phone not being in air plane mode? How was the cell phone located?

Here's a story of an interference event where they went missed:

https://www.quora.com/On-my-last-flight-before-landing-the-p...

A quick search through the NASA ASRS database shows several reports where the ILS or VOR receiver was behaving erratically, sometimes during descent. In some cases the crew was able to land visually, in others the crew crew had enough time to ask passengers to switch off phones and the problem went away.

See: ACN 695049, 321746, 307150, 277118, 200510, 161347, 364464, 467979

https://asrs.arc.nasa.gov/search/database.html

Most of these are older reports, take that as you will. It's entirely possible LTE doesn't interfere with the ILS/VOR. I honestly don't know.

Note also that this only lists reports made through NASAs reporting system. There are other reporting systems used by commercial operators (i.e. ASAP) that I can't easily query.

If I expand the search to include 5G interference, I get 97 recent results. That's a different issue, but at least worth mentioning to show that interference is still a general concern. I'm not going to list all of those, but you're welcome to query for them at the above link.

> What would happen if the cell phone was in the luggage in the cargo bay?

Then they would use one of the other contingency options I already mentioned to land visually or using other sensors. Still not a "safe" situation if this happens when you're close to the ground. If this were to happen during a Cat III approach, it would be extremely bad.
The article is an extended intro for a book the author has written. Perhaps the book mentions these things? Have you read it?
I got criticized for not just hard coding the runway names in a billing app. I said don't y'all know these are the end times and we are at the early stages of a pole shift. I had the last laugh a few years later when the runways changed.
> if i could paid and get API access for my own apps

Assuming it's paid per search, just screen-scrape the thing? There's no reason they'd care what client you use to access it if you're paying for each request.
I wonder to what extent they did it for practicality and to what extent they did it because they could.
The article doesn't fulfill the promise of the title. Not only does it not explain how to identify a scientific fact (who samples the 95% "consensus" and who decides what to ask, for example?), it doesn't even define the term, despite multiple uses.

The reason is, of course, that there are no scientific facts. There are hypotheses, theories, and observations. There is a scientific method, which attempts to connect them together.

This is a deeply unsettling perspective to a lot of people who demand something science can't deliver but which religion can, and I'd count the author among them.

Whenever an author starts tooting about "scientific facts" I sense an agenda. And it's often followed by demands that I submit to it.

Elsewhere, the author pitches the book like so:

> My new book Identifying Future-Proof Science argues that we can confidently identify many scientific claims that are future-proof: they will last forever (so long as science continues). Examples include the evolution of human beings from fish, and the fact that the Milky Way is a spiral galaxy. ...

https://petervickersphilosophy.com/publications/

The first claim is laughable. Without a path for abiogenesis (there is none yet), claims this specific about evolution are anything but "fact." And the tautology of classifying the Milky Way galaxy as a galaxy makes me wonder if the author has problems with basic logic.
not much longer 'till it straight up tells me to take the highway to the danger zone
> the site owner deliberately accepts that some small percentage of
users won't be able to access the site

I disagree with this because I don't think those site owners are
fully informed.

So far, arguments for Cloudflare paint its users as helpless and
clueless. Simultaneously they are fully cognisant of the complexities
and consequences.

I rather think they see a tick-box on a webmin form that says "Block
Evil Hackers", and never give it a second thought.

But you raise a good point. Perhaps Cloudflare are primarily guilty of
misrepresenting their product.
Regarding docks, unless you need USB3 speeds for some reason, get a display port 1.2 to HDMI adapter which also has power delivery and a USB2 port.

This is the most compatible dock you can get as its just generic display port 1.2 and a passive passthrough of the onboard USB2 controller - no drivers needed.

Then buy a cheap 7 port USB2 hub and chain it off the single port of the adapter.

This will run you about $30, will do 4K @60Hz, and have enough USB2 ports for webcams, mic, keyboard, mouse etc. which wont come anywhere near saturating a USB2 bus let alone a USB3 bus.

I've used this for macs, various Windows laptops, Samsung phones and it works perfectly and reliably for a few years now.
I've been using kagi as a paid customer since August 2022. My experience is that for programming related tasks it is much faster to find a useful answer/discussion/site. The most compelling experience I've had with it was during a road trip across Europe. Using the country selector allowed me to find succinct search results for signs, shops and regional attractions. The few times I did comparison searches using google.co.* search the results were more confusing than the kagi results.
Sorry to hijack, but I have a somewhat similar question: any recommendations for a SFF or Mini PC that can adequately run the latest Fedora for home productivity purposes? Web browsing mainly and light gaming.
Right the management would be in charge of course. They would decide whether a given TDEBT-issue should be worked on as a "secondary project" perhaps or not. I think they would still appreciate having the knowledge of the technical debt their company is taking on. You don't need to do anything about (technical or other kind of) debt until you have the money and will to get rid of it. But it's still valuable to know about it I think they would agree.

There's so many kinds of discussions going on in developer communications. Establishing a channel for technical debt within a project would seem to be not the worst waste of time.
>It’s non-transferable (i.e., can’t move it from the account), but it doesn’t list death as the end of the license.

Non-transferable doesn’t mean “can’t move from the account”, it means “legally belongs to the original person to whom it is issued, and cannot be transferred to another person”. Transfer by inheritance at death is…still transfer. A non-transferrable license expires when the entity to whom it was issued ceases to legally exist.

> It’s non-transferable (i.e., can’t move it from the account), but it doesn’t list death as the end of the license.

They don’t need to, since the underlying general law requires you to be alive to legally exist and have property rights in anything, including an Amazon account (unless you are a special entity created by law, like a corporation, which has its own rules.)
You know getting to the point of absurdity is the point of reducto ad absurdium, right?

Hypo?
If they are important enough, add an exception.
Can they just not turn the active document into the file I just exported the workbook as?
Agreed. The post should be titled 'Go enables TCP_NODELAY by default', and a body may or may not even be needed. It's documented, even https://pkg.go.dev/net#TCPConn.SetNoDelay

To know why would be interesting, I guess. But you should be buffering writes anyways in most cases. And if you refuse to do that, just turn it back off on the socket. This is on the code author.
It's an option, with a default. Arguably (I mean, I'd argue it, other reasonable people would disagree), Go's default is the right one for most circumstances. That's not a "defect"; it's a design decision people disagree with.
I can't help but feel that the pricing is backwards.

I understand funding the growth of the business but $120/year per-person isn't going to fly.

Imagine trying to explain to your family why they should switch - oh, that is four accounts - nearly $500/year.

Instead I think the pricing should be something that is 'set and forget'. $10/year with an annual payment would probably be enough to get me to sign up.

Then the issue is scale. I remember old Twitter revenue models being discussed - $1/user/year - once you have 10m, 100m users etc the business will be well funded.
Cries logical Bobby to Ned, will you dare

A bet, which has most legs, a mare, or no mare.

A mare, to be sure, replied Ned, with a grin,

And fifty I’ll lay, for I’m certain to win.

Quoth Bob, you have lost, sure as you are alive,

A mare has but four legs, and no mare has five.

- from A Panorama of Wit, 1809, p. 53
The source code of the black box is open, you can read it. And its tests.
Golang has burned me more than once with bizarre design decisions that break things in a user hostile way.

The last one we ran into was a change in Go 1.15 where servers that presented a TLS certificate with the hostname encoded into the CN field instead of the more appropriate SAN field always fail validation.

The behavior could be disabled however that functionality was removed in 1.18 with no way to opt back into the old behavior. I understand why SAN is the right way to do it but in this case I didn’t control the server.

Developers at Google probably never have to deal with 3rd parties with shitty infrastructure but a lot of us do.

Here’s a bug in rke that’s related https://github.com/rancher/rke2/issues/775
It's not that simple. Large SRAM arrays have the same problems that DRAM has: how much charge do you need to drive into the row and column lines to select the cell you actually want to have active. You can't push it too high because then power consumption goes bonkers. You can't make the wires too small because then they can't pass the power required to drive the entire array. In short, hardware is hard with designers needing to make crazy multidimensional tradeoffs.
Kagi is great for the kind of searches I do -- mainly searching for wikipedia articles, stackoverflow questions, etc. If I ever want to buy a product I don't know much about, I usually spend some time reading the megathread on whatever niche subreddit there is on the topic.

When I search Kagi for "best headphones" the first link on the page is to /r/HeadphoneAdvice, which is probably where I'd want to go. There are some not as good results down the page, but I never would have even seen them because the 1st link is what I wanted.

For "python exceptions" the top links are all to the python.org docs about exceptions, which is almost certainly what I wanted with that generic search.

If I search "steve jobs" or really <any famous person or event>, I want the wikipedia article 99% of the time, and that is the #1 result. I've gotten increasingly frustrated with google in the last few years that they've gone away from this behavior for lots of searches. Sometimes the wikipedia article isn't even on the first page.

So, for my use cases, Kagi is behaving totally optimally for all these searches.
It does work correctly once you change useragent string though.
You guys had this convo before, in 2015, on what the interaction of the two settings should be doing:

https://news.ycombinator.com/item?id=34180239
Exactly this, especially for small purchases like ebooks. This was a big fraud signal for us, I think over 5 cards would auto flag every subsequent order for human review. Probably the most effective signal we had.
You could try and reduce the possible effect by controlling for disease severity. If it reduced the effect a large amount it'd strengthen the case that the effect is actually due to RA disease severity. Actually I'd be a bit surprised if the authors didn't do that for an observational study.
I think my C is getting rusty, but "write" operates on a file descriptor, doesn't it? It's unbuffered. The buffered versions are things like printf and puts.
Writing this from my X1 Carbon (with my M1 MacBook Air also next to me). I'd be particularly interested in what experience folks have had running Linux on ThinkPad X1 Nanos.

Note on your methodology: a purely numeric vote is an automatic win for Lenovo simply based on market share, so you should ask people about problems, if any.
Waez
Being in another country trying to access some things in the US i get blocked all the time. It lead me to canceling one of the services because i got sick or playing the vpn game
All of those things have to be checked immediately every time they cry. The Ferber method, mentioned elsewhere in the thread, says to not even check on the baby for longer and longer periods after they start crying.

During the daytime, if they start crying and you haven't solved the issue, you don't just start ignoring them. Why would you do so at night?