skysight-inc/HackerNews huggingface dataset:
I'm not entirely certain what the conclusion of the essay is, ultimately. It argues that central banks have been reducing the "neutral" rate over time, and lowered interest rates indicate an economy that needs to induce demand. it argues that an aging population demands less. It also argues that income inequality contributes to reduced demand. These are things I understand.

But it just ends in arguing that choices can be made about income inequality and "Let's get to work". What is the work, precisely? [Asking genuinely. I'm not a wealthy person who can buy a politician or give poison money to an academic institution to teach my philosophy. I don't know what the essay wants from me.]
They can do that. The cat is out of the bag. Worst case they can just use GPG/PGP, S/MIME or a bunch of other ways. Backdooring a communication medium just means they won't use it in the first place.
This explains why several of my Go programs needed the occasional restart because of terribly slow transfers over mobile networks.

These weird decisions that go against the norm are exactly why I hate writing Go. There are hidden footguns everywhere and the only way to prevent them is to role play as a Google dev backend dev in a hurry.
JA3 – A method for fingerprinting SSL/TLS Clients
Do you have an unbiased source? Both that website, and the only piece of research linked to at the bottom of the page, are from heavily biased sources (Attachment Parenting International and Journal of Attachment Parenting). None of the primary articles under "Research Related to This Principle" support the quote you highlight (least as far as I can tell, maybe I missed!), and the specific quote doesn't link back to any specific study. Not only that, but...

>Until that time, a child depends on his parents to help him calm down and learn to regulate his intense feelings.

Again, you're ignoring the fact that parents absolutely do tend to their children emotionally during sleep training. I highlighted that in another response to you earlier, as well as this very comment chain. You even edited your comment and acquiesced to support a version of it at six months, and now you're back admonishing the practice as "dangerous" altogether?

Edit: I am not saying you shouldn't hold your own views. Do what you want with your kids as long as you and your family are happy. Just ease up on telling others they are wrong - they are just as right for their family as you are for yours.
Newtonian Physics is not a fact, but a whole theory. I think that the author is talking about facts within a theory.
Your distinction is not useful for someone who needs help understanding what qualifies as "fact as we know it".

It could easily be misconstrued as a counter example to the quote in the article, which it is only in the strictest, most pedantic sense. In any reasonable interpretation, Newtonian Physics is still true.
I call it "send to Kindle".
Exactly. I was sympathetic with the author until it suddenly turned into “the white man is oppressing me.” Blah, blah, blah - whatever.
Seems completely broken on mobile?
Perhaps reflective of the times.

A browser becomes less and less an agent of the user with each passing day.
I think one of the most insightful things I've learned in life is that books, movies, articles, etc. have warped my perception of the "elites." When you split hairs, there is certainly a difference in skill/knowledge _but_ at the end of the day, everyone will make mistakes. (error-prone wetware, haha)

I totally get it though. I mean, as a recent example, look at FTX. I knew SBF and was close to working for Alameda (didn't want to go to Hong Kong tho). Over the years I thought that I was an idiot for missing out and that everyone there was a genius. Turns out they weren't and not only that _everyone_ got taken for a ride. VCs throwing money, celebrities signing to say anything, politicians shaking hands, etc.

Funny, I did see a leaked text when Elon was trying to buy Twitter, SBF was trying to be part of it and someone didn't actually think he had the money, so maybe someone saw the BS.

All that aside tho, yea, this is something I forget and "re-learn" all the time. A bit concerning if you think about it too much! I wonder if that's the same for other fields of work. I mean, if there was an attack on a power grid, how many people in the US would even know _how_ to fix it? Are the systems legacy? I've seen some code bases where one file could be deleted and it would take tons of hours to even figure out what went wrong, lol.
That doesn't make much sense. There are all sorts of socket and file descriptor parameters with defaults that are situational; NDELAY is one of them, as is buffer size, nonblockingness, address reuse, &c. Maybe disabling Nagle is a bad default, maybe it isn't, but the appeal to "OS defaults" is a red herring.
I thought xistenz was also great. some body horror present though.
With discussion: https://news.ycombinator.com/item?id=34125958
> There are many cases where all of humanity has been doing something that we only recently decided was wrong. For instance, slavery.

Not really comparable because we decided it was morally wrong, not that we were wrong about its effects. Its not like humanity used to think slavery was good for the slave.
In the UK you get six month's paid maternity leave, and that is in a country being run into the ground by right-wing idiots.

In most European countries it's 12 months.
Happy 13th Birthday, KrebsOnSecurity
You missed the part about many inefficient system calls. You want buffering to happen before the thing that has a relatively high per-call overhead.
I'm using Go's default HTTP client to make a few requests per second. I set a context timeout of a few seconds for each request. There are random 16 minute intervals where I only get the error `context deadline exceeded`.

From what I found, Go's default client uses HTTP/2 by default. When a TCP connection stops working, it relies on the OS to decide when to time out the connection. Over HTTP/1.1, it closes the connection itself [1] on timeout and makes a new connection.

In Linux, I guess the timeout for a TCP connection depends on `tcp_retries2` which defaults to 15 and corresponds to a time of ~15m40s [2].

This can be simulated by making a client and some requests and then blocking traffic with an `iptables` rule [3].
My solution for now is to use a client that only uses HTTP/1.1.

[1] https://github.com/golang/go/issues/36026#issuecomment-56902...

[2] https://blog.cloudflare.com/when-tcp-sockets-refuse-to-die/

[3] https://github.com/golang/go/issues/30702
We actually have "quiet zones" in second class here (Netherlands), but it's a bit of a hit-and-miss type of thing. Usually when I've (politely) asked people to stfu I've gotten a reasonable reply ("oh, sorry, didn't realize"), but sometimes not so much, or just say "okay" and continue. Sometimes I don't bother because I'm not in the mood, or the people seem unlikely to be receptive.

1st class tends to be rather expensive. Depending on where you live, even 2nd class can be quite expensive.
Fundamentally, it costs Paul time and money to serve Peter a webpage, and that becomes a problem when millions of "people" (read: bots) show up and ask to be served every webpage on Paul's website. That's where the nature of "free speech" ends, when your actions impact someone else negatively (which is why, even in the US, you have the right to speak freely but not the right to force others to listen).

Solving this in a way that doesn't block tons of regular users (since doing so would cause the site owners to drop Cloudflare) is precisely where nearly all of Cloudflare's $15B market cap comes from.
There's a lot of vigorous dissent here because lying requires intent: One's statement(s) must be intended to deceive people. I think this formally/technically correct dictionary-wise, but kinda missing the point.

If your goal is to help people understand media better, they do need to know that most media deception is accomplished by simply avoiding relevant facts rather than voicing outright falsehoods. In other words, as a media consumer, your primary question should be, "What are they not telling me?" This is why it helps to multi-source your news.

That is a very instructive lesson to learn - something we should teach kids in school, really.
What is easier, watching a movie or making a movie? Or do you think those are equal in effort?
I understand. But they are naive, misguided, conflicted, and stuffed with money. There is no evidence that giving platforms to hucksters, Nazis, racists, or conspiracy theorists moves any conversation forward in any helpful manner. But there's lots of evidence that giving lies more airtime gives those lies more teeth and those teeth more flesh to chew on. These idiots are eroding the populace's ability to reject malicious actors right out. Which is what we should be doing. There is no need to rehash the fact that hating Jews is a bad thing. Lex should apologize and take a course in media literacy.
The default is glinux, most of the company are using chromebooks.
One of these days we'll find that One Weird Trick For A Good Social Network.
>* you're saying that someone should be allowed to drive in wrong lane or drive in middle of road and only get punished when they actually crash into someone?*

I'm saying that the law should not be able to punish them if they haven't caused actual harm. If they do cause actual harm, I have no problem at all with these things being treated as aggravating factors that increase the punishment.

> Can't punish a corpse, can't resurrect whoever you killed.

That's just as true under our current system as it would be under the kind of system I have been describing. But under our current system, as I have pointed out, people lose respect for the law in general when the law punishes them when they haven't caused actual harm. That doesn't seem to me like a good thing. Nor does it seem like a way to reduce the amount of actual harm people cause. Loss of respect for the law in general means people are less likely to pay attention even to laws that do relate to actual harms.
At first I was like "Yeah buddy, preach on". Then came the next thought:

Then what. Site providers will still will want to know and this likely results in a browser detection excalation arms race pushed to JavaScript.

I still think servers shouldn't get to know so much about browser clients, certainly not PII-level details (PII-level being the norm as it exists today).
I'm pretty convinced that every foundational OS abstraction that we use today, most of which were invented in the 70's or 80's, is wrong for modern computing environments. It just sucks less for some people than for other people.

I do think Golang's choice of defaulting to TCP_NODELAY is probably right - they expect you to have some understanding that you should probably send large packets if you want to send a lot of stuff, and you likely do not want packets being Nagled if you have 20 bytes you want to send now. TCP_QUICKACK also seems wrong in a world with data caps - the unnecessary ACKs are going to add up.

Issuing a SEND syscall every 50 bytes is also horrendously CPU-inefficient, and certainly should be expected to trigger pathological cases.

At this point, the OS is basically expected to guess what you actually want to do from how you incant around their bad abstractions, so it's not surprising that sending megabytes of data 50 bytes at a time would trigger some weird slowdowns.
> The Chrome team insist that this behavior is a bug, but it is actually in line with this particular version of the spec.

Or, why any other browser is the new IE. /s
The GNU and/or GNU-Linux terminal is the killer app.

* M-Windows WSL2
* Cygwin
* Mac OS X
* ChromeOS Crostini (Debian Linux VM)
* Linux (of course)
Same, but hearing stories from other parents makes me believe we are just very lucky that our baby is responsive to this empathic approach.

Also white noise app cuts down on the whinyness before sleeping tremendously.
There are several easter eggs if you keep scrolling.
I sometimes forget I have my VPN on and don't ever realize until I randomly hit a captcha or youtube tells me I'm in a different country. I'm surprised so many people are getting these because I can go hours without seeing one with my VPN on. I not only have ublock but other privacy things which cause more problems (cookies) than captchas.
It's... complicated but I assume the GP meant new drug product exclusivity [1] which is a process by which a pharmaceutical manufacturer can get a short window of exclusivity for a new approved use without rights over the original patent. That exclusivity is largely for generic manufacturers [2] though and it's separate from the patent patent term restoration [3] the FDA grants to patent holders to help with the time it takes to get to market.

"Re-patent" would mean something different like Shire patenting Vyvanse by adding an amino acid cap to amphetamines, changing it enough that it becomes a new drug with a new patent. That would require clinical trials and all the expense that goes with them.

[1] https://www.fda.gov/drugs/cder-small-business-industry-assis...

[2] https://www.fda.gov/drugs/development-approval-process-drugs...

[3] https://www.fda.gov/drugs/cder-small-business-industry-assis...
I just hope it won't cause prices creep. CPUs and GPUs were already gradually getting more expensive for same kind of levels with recent generations and this rush to the newest node would only make it worse, unless increased scale of production will help lower prices.
That's fair, though I still think R7 and Messi would have faired much better given superior training (physical, mental, and strategy) and nutrition they have had over their careers.
> this shatters the myth of Google(r) superiority. It turns out people are universally entities comprised of sloppy, error-prone wetware.

Golang was created with the specific goal of sidestepping what had become a bureaucratic C++ "readability" process within Google, so yes. Goodhart's law in action.
Is cloudflare self appointed? I was under the impression that they were a service provider that people hired/employed/used?
How can you call it a defect when it might have been a deliberate decision? Your whole post sounds like you're upset Google didn't hire you lmao
> So, in your view, we should just stop regulating gambling, drinking, drugs and firearms?

Yesmeme.gif
I guess for them it would be more like a three - four with the leading one - digit number, would it not? Did they have a 60 x 60 multiplication table at hand? I am almost tempted to try it out, I would guess that it should be doable in two hours in modern notation.
I got fired from a training placement in 98 for sending a NET SEND message to the internal Novell Netware 4.xx based mail server, stopped the mail for about 30 mins.
> Generally speaking, it is a mechanism that helps enforcement of regulations related to owning and operating a vehicle.

Ok, so this is basically the same argument other people have been making. My response is the same as it has been to others.
I do, as I like to bookmark stuff that I find interesting to share or look up again later. Having it disappear at a whim with the only hope being that it was archived such that I can access it makes the web a bit less meaningful to me.
Finding out that something's gone after looking for it is already happening often enough, there's no need to increase that.
The "On gigabit fiber" part is true, though.
Can you elaborate? Your suggestion not to turn it back on would result in the OP having to suffer slow upload speeds despite having available bandwidth order of magnitude larger. How is that a good outcome?
When certain iOS devices are factory reset, they default to cellular data being turned on (and available using Apple-provisioned carrier credentials) to use mobile data service to activate even without connecting them to a local network.

I know at least a cellular iPad Mini has done this to me when I didn't want it to. (I was doing an experiment for a year where I try to keep Apple from knowing my location, via Wi-Fi VPN routers and no location services. FWIW, the experiment failed because of surveillance features like this.)
I seem to recall someone mentioning it as "coming eventually." Hopefully that proves to be true.
First half yes, second half no. Everyone quickly finds out that chromebooks cant hack it spec-wise, even for simple chrome remote desktop.
Since the study was released; I was waiting for a class action against Hershey to occur. The original study I believe used California defined lead and cadmium levels though, so I assumed it would have occurred in that state under the terms of no warning on the chocolate.

Aldi's (Grocery Store chain) chocolates were low in heavy metals for those interested.
Seems that they have done just that.

https://github.com/pixelfed/pixelfed/pull/4037
The basic problem, as I've written before[1][2], is that, after I put in Nagle's algorithm, Berkeley put in delayed ACKs. Delayed ACKs delay sending an empty ACK packet for a short, fixed period based on human typing speed, maybe 100ms. This was a hack Berkeley put in to handle large numbers of dumb terminals going in to time-sharing computers using terminal to Ethernet concentrators. Without delayed ACKs, each keystroke sent a datagram with one payload byte, and got a datagram back with no payload, just an ACK, followed shortly thereafter by a datagram with one echoed character. So they got a 30% load reduction for their TELNET application.

Both of those algorithms should never be on at the same time. But they usually are.

Linux has a socket option, TCP_QUICKACK, to turn off delayed ACKs. But it's very strange. The documentation is kind of vague, but apparently you have to re-enable it regularly.[3]

Sigh.

[1] https://news.ycombinator.com/item?id=10608356

[2] https://developers.slashdot.org/comments.pl?cid=14515105&sid...

[3] https://stackoverflow.com/questions/46587168/when-during-the...
Reality: sleep training enters the picture only after all the things you've mentioned have been checked first.

Even from a pragmatic point of view, it's hard to imagine otherwise, because all of those underlying reasons are quick to check and (usually) quick to mitigate. You don't even consider sleep training until exhausting every other option, because literally everything is easier than any of the sleep training methods.
SACKs are the second most important/useful TCP extension after window scaling. SACKs have had basically universal support for more than a decade (like, 95% of the traffic on the public internet negotiated SACKs in 2012). Anyone writing a new production TCP stack without SACKs is basically committing malpractice.
> Python doc peaked for me with the 1.x “library index to keep under your pillow”

I can see why that’s nice, but I find it odd to be described as a peak. While the details of the standard library it documents have evolved, I don’t see how the current version (linked from the main docs site with the same “keep this under your pillow” line) of the same portion of the docs is any worse:

https://docs.python.org/3/library/index.html
Interesting. Some of this data isn’t easy to access for me in Canada but yep, they’re in a similar space.

Funny because I’m from Australia, but never transacted property over there.
You can just ask him here; he's the 12th busiest user on HN ('Animats, the name of his ragdoll physics engine).
Exactly. There’s no reasonable world where the kitchen lamp should remain out while you (try to) drive to the store.

Pop the stack a few levels, replace the lamp, then decide if you need more WD-40 right now or can get some the next time you’re out.
.. and now I look you up and see "created: 22 hours ago"

So you're not even a real HN'er. Why don't you tell everyone who it is who's so free with the insults? Or are you scared to take responsibility for them?
Vine was around for quite a while too. well, 2013-2016 at least.
Since the article doesn't mention the word 'experiment' once I doubt it's even discussing science but rather 'scientific orthodoxy' which is something else entirely and should never be categorised as 'fact'.
The seed for an LFSR is just the starting value for its cycle; it can be any value in the cycle, and it's public anyway in that you can think of each output of an LFSR as the "seed" for the next output.

But in the case of the "taps", yes, you would want to treat those as a secret if you didn't want someone to predict the next value in the cycle. An LFSR by itself might not be a complete solution for IDs for public consumption, but it does neatly solve the need for pseudo-random non-colliding IDs. Whereas NanoIDs are able to generate values with a ~1% probability of collision over some time period, LFSRs can generate values with a 0% probability of collision over their entire bit space. (And they're composable!)

It looks like NanoIDs are entirely random values reduced to a specific alphabet (https://github.com/ai/nanoid/blob/main/index.js) -- which is approximately similar to:

tr -dc _A-Z-a-z-0-9 < /dev/urandom | tr -d '/+oO0lLiI1\n\r' | head -c $num_chars

...but with a really nice collision estimation tool attached.

So if you want randomness in your IDs and you still also want to guarantee 0 collisions, then you can always just append a randomly-generated value to the output of the LFSR, and then feed that into whatever widget you want to use to convert it into a public ID, if you think it's necessary.

But the edge case of collision prevention at really large scales has always seemed to me to be much harder to solve than the edge case of ID enumeration giving up anything valuable (in a well-designed application).
You can't stop fingerprinting. I wish you could, but you can't.

But you CAN make it enough of a pain to cut down on the number of half-qualified Web monkeys who try to use the information in ham-handed ways. You can stop just handing the information over for free to people who might want to casually exploit you. You might even make it harder for some more sophisticated and/or committed actors to do it; for example, if I'm an ISP running a middlebox and trying to fingerprint all the traffic that runs through me, I can't use JavaScript. And you can save some bandwidth in the process.
At this point, this problem has caused me dozens if not hundreds of hours of waiting on slow transfers. It is evil. Maybe I should disable all my neighbor’s routers or convince the local authorities to open more 5Ghz spectrum… but it is what it is.
SBF is a good actor. I got it. `Fraus Omnia Vitiat`
Switched to Kagi 2 months ago, can't recommend it enough.

It's not that it's better than google (although it is for some types of searches). It's that it's not worse. Bing and DuckDuckGo are worse than google. I tried to switch to DDG many times, but fell back to google at least 1/3 of the time.

I haven't googled a single thing since switching to Kagi. Easily worth the $10/mo to not have my search history monetized, and to work with a company whose incentives are maximally aligned with giving me the content I am searching for.

Kagi also has nice features like personalized upweighting/downweighting of certain websites.

The Kagi team is also super responsive to feedback. I've submitted a few bug/feature requests that have gotten fixed within a week or two.

It's amazing that a small team can compete with google.
Your example isn't great because newtonian physics is still correct and used everywhere.

I agree with your point, reality is certainly not statistical, and e.g. there would have been circles in which heliocentricity or a flat earth or some pre-germ theory of disease would have been agreed upon fact. Arguing that those aren't science is hindsight, at the time they would have been learned consensus.
So we one more step away from SMT, and next generations will be more and more NUMA.