skysight-inc/HackerNews huggingface dataset:
Children, who on average get a minimum 15 years of education and guidance before they're entrusted with anything serious. And yet we expect perfection from budding AI upon or a few weeks after its release. Crazy.
I can't see why a jitter plot with dark lines marking the quartile wouldn't be strictly better for this.
Key missing component: CAFE needs a rewrite. US emissions laws have a cutout so that larger vehicles have less stringent emissions requirements. The problem is that this is no longer a gap it's a chasm. Slight hyperbole but a Japanese kei car many Americans would love town own muat do closer to 50mpg, while a monster pickup can do 15mpg. It ends up that a small car can cost $15,000 and the giant pickup costs... $15,000. Many consumers compare the two and wonder if the econobox is really a good choice.

The bright shining hope: Most Americans do not want these big cars. Legislation is making small vehicles less competitive, when it should be the other way.

AKA - we have good, cheap(ish) electric trucks now. Legislation doesn't need to worry about farmers who can't afford electric anymore.
It’s really hard to describe, but not even audible words. Just the idea of words, I have to actually speak to hear the words.
Is there a popular protocol that uses this scheme today? I've often thought that this would be a superior way to transfer/sync data. and have always wondered why it wasn't common.

The closest I can think of is the old FSP protocol, which never really saw wide use. The client would request each individual chunk by offset, and if a chunk got lost, it could re-request it. But that's not quite the same thing.
Inverting a general-purpose cryptographic hash function in the quantum setting is (roughly) as hard as it is in the classical setting.

(Roughly because of Grover’s algorithm, but there are algorithms that perform similarly or better on classical machines. Which is why modern hash functions have relatively large margins anyways.)
Literally in the article.
Studies like this always seem to me to be a formality.

The conclusions are what the person paying for the study wants them to be.

If a local municipality is anti-car, they will run a study justifying adding bike lanes everywhere, even though once they are built you never see bicycles in them, and they create more difficulty for cars by narrowing or taking away lanes.

Or they'll install "traffic calming" speed bumps, chicanes, or curb-extension bottlenecks on neighborhood roads when (almost) nobody in the neighborhood wanted them.

On the other hand, if they are pro-development, their studies will show that a new or widened road will lead to more business development, more jobs, more tax revenue.
I follow https://social.tomtaylor.co.uk/@lowflyingrocks

Most of them are pretty far away but there are a few each month within lunar orbit, about 400,000 km
I will be honest, while the project is actually neat, it showcases some of the issues with technological advancements as related to society ( and happens to also touch on one's exposure in a big city ). One could easily imagine a scenario ( or scenarios ), where this could be misused.
Yes quite correct. The Corporation is a local council, it collects the bins and operates one primary school.

There's always this misconception that it's some sort of lawless wild west. If it was, I assure you every company in the world would be based there!
What are you talking about?
You can still tip in Europe. In fact, if you tip at bars enough at the rate of 1-3 EURs per drink , you'll end up getting free drinks and significantly better service.

That was the best part about being in Europe. Tips were appreciated whereas in america, wait staff expect them and feel entitled to absorb 25% tips.
Don’t really care about advice from the guy who invented an incredibly non pragmatic programming language. I also honestly had to look up who he was. So his sage advice hasn’t brought him much fame.
Gen Z added a new one :)

https://i.redd.it/j5txdt2np1v71.jpg
I can think of them no problem, but I don’t visualize them it’d more that I think of their abstract representation.
I love this kind of project.

A lot of states are working on legislation that includes requirements for watermarking AI generated content. But it seldom defines AI with any rigor, making me wonder if soon everyone will need to label everything as made with AI to be on the safe side, kinda like prop 65 warnings.
The level of noise went up dramatically after the first year. I read that this is part of the panel aging. It hasn't gotten worse since then. My two biggest gripes are high brightness areas don't work on large portions of the screen. A windows file browser is basically unusable.

The heat is probably what will eventually get me to replace it.
>well there is usually not option to forgo work as money is needed for survival... So their only option is to take work that is less than they might think they are worth

Is this somehow bad? Everything is only "worth" as what people are willing to pay for it, and labor isn't any different.
> You have all these restaurant operators crying that getting rid of tippers puts them out of business

They're not exactly wrong, I suppose. A restaurant isn't in the business of food, they are in the business of letting the patrons feel like they are kings for a moment of their life. Being able to throw some shilling at "the help" is part of the experience.

I've experimented with not offering tipping as an option when I have worked on the floor and customers become quite irate about it. I was actually a little taken back at first, but it makes sense when you stop and think about why the business model exists.

That's not say restaurants couldn't pivot into a new business model, but outlawing the old model would absolutely see that business go under. Anything else would be in violation of the law.

> there's no contract, no constitutional guarantee that you're allowed to be in business.

Fair enough. But by the same token, it is curious that there are calls to end the experience customers crave and one that provides a pretty good living for those doing the work. All parties are making the transactions voluntarily.

> If tipping is made illegal, you can expect meal cost across the board to rise by about this much to make up the difference.

Indeed. Which is way better for me as it is easier for me to skim my margins off the top. Humans aren't perfect calculators. They wouldn't notice a few cents here and a few cents there in my favour. The law prevents me from taking a margin from tips, though, so there is much greater accounting visible to the worker there. I suspect the "tipping should be illegal" idea stems from restauranteurs themselves.

I am certainly a proponent! Bring on making tipping illegal. Who doesn't want the cashflow through their own books? But until then, I am beholden to my customers and staff. Without them, I truly don't have a business.
Right? I can already imagine the government doing this to drop nuclear bombs on dissidents.
Alternatively, if prices stay affordable like they are currently, it democratizes skills that are required to do something interesting. I see it as empowering for very small creators.

Let’s say I’m an animator but can’t make music. Now I can add moderate quality custom music to my animations and make indie animations entirely solo. That was impossible before.

And let’s not ignore all the great artists out there who struggle programming in their game engine, and can use AI to hack together basic interactivity. Is it better than a professional? No, but it allows a solo artist to craft an experience entirely solo.

AI does for a lot of things what the internet did for publishing - give everyone the power to do it themselves at a smaller scale.
Curriculum for Andrej Karpathy's Upcoming Course Is Amazing
1. Deep blue isn't a LLM. I don't care how well you train a LLM, it's not going to be more efficient than an optimally trained human, not even close. It's actually arrogant as hell to assume that we can achieve a higher level of energy efficiency than billions of years of evolution, particularly so early in the game.
2. Chess is a closed form system with a finite and relatively small number of position compared with the real world.
> meanwhile, a lot of tooling nowadays is written in Go, and I have no idea why, it's not friendly for os manipulation at all

I'm not sure where you're going with this: My experience of Ruby and Go is that:

1. Go is a lot easier to do OS manipulation type stuff.

2. Go is a lot easier to modify down the line.

TBH, #2 is not really a consideration for shell-scripts - the majority of the time the shell script is used to kick off and monitor other programs, transforming an exact input into an exact output.

It's glue, basically, and most uses of glue aren't going to require maintenance. If it breaks, it's because the input or the environment changed, and for what shell is used for, the input and the environment change very rarely.
Ok folks, how does this impact our AGI (Aerial Gear Installation) timelines?
This is beautiful. Have you ever dropped a hat on someone's head a a surprise?
While neat in a "because we can" kind of sense, it really is maddening: Have we gone "compute-mad" and will end up needing a full-fledged VM to render ever-smaller subsets of UI or content until ... what?

What is the end game here?

It is kind of like a "fractal" attack surface, with increasing surface the "deeper" one looks into it. It is nightmarish from that perspective ...
It's hard to answer that without you saying what you think the obvious benefits are.

Consensus algorithms are important for all kinds of distributed computing problems. A simple example would be failover. If you have a leader database that replicates to 4 others, and you want another node to take over if the leader DB fails, then you need a consensus algorithm to prevent a situation where 2 different machines both think they're the new leader in a netsplit.

There are many other equivalent problems in distributed computing, from atomic transactions to "exactly once" messaging systems.

Asynchronous consensus is a model where you cannot make assumptions about the bounded nature of call timings, whereas in a synchronous model, you can assume everything is bounded.

Byzantine fault tolerance is important for security under byzantine faults, that is to say malicious actors acting deliberately against what the protocol specifies they should do.
There’s nothing intuitive about what “best effort” means, but if you know anything about udp and tcp you know which is “reliable.”

> UDP makes its best effort

TCP tries really hard, too, you know.
The surprisingly queer history of OpenAI's ChatGPT and other A.I. bots
Oh god the shame.
Bike lanes success are well measured and will often carry more people than a car lanes will.
I only tip for table service and taxis. If I see a tip on anything else, I happily hit no tip. I don't do delivery either since even with tips delivery drivers still bring my food cold. I'd rather get off my bum and guarantee hot food immediately without the risk of the driver eating it.
So the protocol seems to boil down to:

1) Already have a leader "Dealer"

2) The leader builds a K-of-N set of shared secret keys.

3) They publish a mapping of each participant (participant_i->hash(secret_i))

4) The leader transmits each key to each participant

5) Participants exchange secrets pairwise, armed with the upfront mapping of participants->secrets

6) Select K and a k-of-N secret scheme such that a majority of participants now have a shared key

lots of the claims aren't meaningful:

- "post quantum" for example isn't a special value in this situation.

- "minimal use of cryptography" isn't relevant to practicality

- The "experimental" component doesn't meaningful contribute to the conclusion.

- No public-key-encryption really means "outsource sender identification to the network layer"

- They pretend using a system of equations to solve for a shared key isn't"cryptography".

In general the contribution of the paper reads as "offusicated". The lack of "public key cryptography" sets them up for a novel problem to solve, but it is an arbitrary handicap that doesn't provide utility.

This is academic "make up a novel and nontrivial problem and then solve it", its of utility to the process of producing grad students and publication count but not something we need to get excited about. Read it like a survey paper of the space, which it does well as.
It's just that I have a hard time imagining that there were seas without any rain occurring for hundreds of millions of years so it didn't occur to me that these could be separate questions. And most of the comments here seem to be conflating them as well.
I spend an inordinate amount of time wondering how people discovered amadou, https://en.wikipedia.org/wiki/Amadou as well as glue.
Thanks, this was really helpful.
The OP's point was more that the Atlantic is the wrong pond to ship across from Japan :)
> the screens will mess up your night vision

This was a huge problem in a car I rented recently. There was so much light coming off the dash I could hardly see the road, and there was no obvious way to dim it (all my older cars have a dedicated knob or wheel to control the dashboard brightness).
If you think that's bad, until very recently, Windows used to parse ttf directly in the kernel, meaning that a target could look at a webpage, or read an email, and be executing arbitrary code in ring0.

Last I checked there were about 4-10 TTF bugs discovered and actively exploited per year. I think I heard those stats in 2018 or so. This has been a well known and very commonly exploited attack vector for at least 20 years.
The YouTuber Not Just Bikes made a great point in one of his videos: why in the world are public safety improvements up for debate? If people keep falling off a walkway, we don’t hold town hall meetings to debate the merits of pedestrian safety, we don’t do studies on the impact to traffic flow, we just put up a railing.

Here in Philadelphia, advocacy groups spent years fighting to have a wide, lethal stroad that runs through the middle of the city put on a road diet. Residents were polled, and something like 70% of people in the surrounding neighborhoods were in favor of it. The city spent millions in planning and engineering, and then right before paving was about to start, a local councilmember blocked it and canceled the whole project on the half of the road that runs through their neighborhood. So half of the road was narrowed to two lanes and has no speeding, no fatalities, and generally sane driver behavior. The other half is a reckless free-for-all that’s exhausting to drive on and terrifying for pedestrians and cyclists.

Millions in taxpayer dollars and the political will of a majority of citizens were wasted because our system allows one NIMBY to stop everything. A year later, there has already been a cyclist fatality on the road.
I've done this too. Although not at the "millions of clients" scale, but large enough to drive learnings. Everything above is true.

Migrations are painful, thankless and always run over budget and time. Unless I've been at the company long enough, have enough confidence and rapport with my reporting head and skip level, I'd rather not do it.

I'm never taking any big (more than 2-3 month) migrations. Only small predictable subsystems that i can rollback or run both v1 and v2 in parallel. First one third time is for discovering by making changes and seeing where things break and possibly come up with fast tests (manual or automated). Last one third is for actual testing, trying out small pieces in production and fixing unexpected issues. So take your dev estimate and multiply by 3.

Even then, you have to shoot down any demands to use new frameworks, new processes and new dependencies. And resist your own temptation. Remember no one gives a shit about migrations.

You will be asked a thousand times on the progress by people incapable of fathoming the complexity. They expect a percentage. Have one ready with a small roadmap, of cornerstones and publish as a report or something. Everytime someone asks, point to the report. No one ever opens that report.
Well, they didn't ask for a higher salary, they asked for higher tipping options. "That's not what I asked for" isn't exactly a great way to keep staff happy.
The better stick is escalating fines for repeat offenses. I’m fine letting a company off easy for their first offense. But that second one they should know better.
What obligation? They are paying taxes. That's more than enough.
Your ruminations about how they problem can or cannot be solved are not relevant to what is causing the problem. Individual lifestyle choices are what causes obesity, this is a plainly obvious fact that a lot of people are in a complete state of delusion about. What caused this massive shift in culture is a seperate question, that you will find plenty of other people eager to debate with you.

How to solve the problem this has created is again another seperate question. But I would suggest that problems caused by individual choices have very few (and very unsatisfying) solutions, other than personal responsibility. Which all tend to require denying people their liberties (like the way you might put a person in jail if they refuse to stop choosing to commit crimes).
will this create an organic HN meetup next under this dudes window?
Lane splitting motorcycles and bicyclists are literally always illegal btw.

Lane splitting is for air cooled engines stuck in traffic, where they literally need to move or shut down. (It is technically illegal to park the vehicle with engine shut off in case you can't restart). It has absolutely never been legal for anyone to shoot through gaps in traffic because of erectile dysfunction compensation. It is only in the absolute emergency that you need to walk your bike around to keep it from melting.

In general I do agree. Campaigns to "see motorcycles" just end up with 80yo biker gangs thinking it's okay yo blast their engines in residential. Campaigns to "share the road" lead to bicyclists who will absolutely charge an SUV just to get on the news. I'm all for road safety but it absolutely requires bike clubs of all types to stop being twits.
Yes though their displays were generally OEM.

In fact I'm pretty sure that Sun, SGI and HP all used the same OEM. They were really nice Trinitron displays though and this meant they were well interchangeable too. Which was great because by PC standard they used a weird DB25 with 3 composite RGB connector and sync on green iirc.
Also DeepBlue isn't an ML it's an "expert system, relying upon rules and variables defined and fine-tuned by chess masters and computer scientists" from Wikipedia. AlphaGo (or AlphaGo Zero) would be a better example.
Think about what the feature (potentially) buys you:

(1) zero-copy, zero-allocation request processing

(2) up to a 2x latency reduction by intermingling networking and actual work

(3) more cache friendliness

(4) better performance characteristics on composition (multiple stages which all have to batch their requests and responses will balloon perceived latency)

If you have a simple system (only a few layers of networking), low QPS (under a million), small requests (average under 1KB, max under 1MB), and reasonable latency requirements (no human user can tell a microsecond from a millisecond), just batch everything and be done with it. It's not worth the engineering costs to do anything fancy when a mid-tier laptop can run your service with the dumb implementation.

As soon as those features start to matter, streaming starts to make more sense. I normally see it being used for cost reasons in very popular services, when every latency improvement matters for a given application, when you don't have room to buffer the whole request, or to create very complicated networked systems.
Dinosaurs have also been around orders of magnitude longer than humans. Behaviourally modern humans have been around for 50k years, while Dinosaurs were dominant on this planet from the T-J to C-P extinction events, so approximately 140 million years. That's three orders of magnitude. Also, even though nowadays 95% of mammalian biomass is either humans or exists to serve human needs, we still will need a long period to catch up to the legacy of the dinosaurs.
>I hate this sentiment. Not every degree is going to lead to a high paying career, but knowledge is worth having in it's own right. If people are passionate enough spend four years studying art history or poetry or underwater basket weaving then I'm glad we are sharing and preserving that knowledge in our culture.

There's probably some non-zero value in learning underwater basket weaving or whatever, but I don't see why it should be publicly funded. I don't see any fundamental difference between someone wasting 6 figures on an useless degree, and someone wasting 6 figures on a useless hobby.
As shown in the video, the font is 280 GB, so opening such a page will practically be a nightmare, especially if you are on cellular.
There are Forths with richer types than just that -- it's not just one language, after all. I've never heard of statically typed Forth; the stack is a filthy pile, after all. But nothing stops you from writing an allocator, container types, etc..
Unless it's a total stripper meant for something like a highway maintenance department fleet vehicle, a "giant pickup" will cost 3 or 4 times that amount.
> 1. Routers do all kinds of terrible things with TCP, causing high latency, and poor performance. Routers do not do this to nearly the same extent with UDP

What things are you thinking of here?

> 2. Operating systems have a tendency to buffer for high lengths of time, resulting in very poor performance due to high latency.

Do they? I can only think of Nagle's algorithm causing any potential buffering delay on the OS level, and you can deactivate that via TCP_NODELAY on most OSes.

> 5. TCP's backoff model on packet failures is both incredibly aggressive, and mismatched for a flaky physical layer. Even a tiny % of packet loss can make your performance unusable, to the point where the concept of using TCP is completely unworkable

That's a property of your specific TCP implementation's congestion control algorithm, nothing inherent to TCP. TCP BBR is quite resistant to non-congestion-induced packet loss, for example [1].

> If you use QUIC, the server will attempt to send the packet again which.... is completely pointless

Isn't one of QUIC's features that you can cancel pending streams, which explicitly solves that issue? In your implementation, if you send update type x for frame n+1, you could just cancel all pending updates of type x if every update contains your complete new state.

[1] https://atoonk.medium.com/tcp-bbr-exploring-tcp-congestion-c...
Normalizing the complexity doesn't make it go away.

Ideally, I'd like not to execute any kind of arbitrary code when doing something mundane as rendering a font. If that's not possible, then the code could be restricted to someting less than turing complete, e.g. formula evaluation (i.e. lambda calculus) without arbitrary recursion.

The problem is that even sandboxed code is unpredictable in terms of memory and runtime cost and can only be statically analyzed to a limited extent (halting problem and all).

Additionally, once it's there, people will bring in libraries, frameworks and sprawling dependency trees, which will further increase the computing cost and unpredictability of it.
They carry more bicyclists, you mean.

/s
You're not missing anything. Systems like this assume there is a pre-created set of honest and independent nodes, which might later get hacked. They don't apply in the more realistic setting the PoW blockchain algorithm solves, where nodes can enter and leave the consensus at will and may be malicious or non-independent from the start.
It looks like a spike, not a bell.
I'm not sure what you think you've gained or stated with this remark.

"Mind's eye" and "visualization" refer to actual experiences. Those of us with aphantasia (no exceptions that I've encountered so far) did not realize these words referred to actual experiences.