skysight-inc/HackerNews huggingface dataset:
Not OP, but it's very simple - by historical standards, everything is crazy expensive, especially in the stock market, but not only (housing...).

Home price to median household income ratio is at all time high - current generations have to work almost twice as long to pay a house, compared to their parents.

S&P price / earnings ratio is around 27 now and it's been above 20 pretty much all the time since late 90s.

In the past it was hovering between 10-20 usually - here is a chart: https://www.multpl.com/s-p-500-pe-ratio

We have huge companies (the famous MAG 7) with PERs above 30. Given their scale, it's pretty much impossible to grow enough to reduce this PER significantly, unless we discover another planet with eager customers, or solve poverty worldwide.
So while they do make a lot of cash, if you were to buy the whole business, you would need to wait 30 years for it to pay back for itself...

I know people stopped thinking like that, and just hope the 'price will go up' and there will be a greater fool willing to buy even higher. But at some point, the music will stop, although nobody knows when though. And if you look at the history of when the music stops for the markets, it's not pretty.
That is a lot thicker than I was expecting.

The thing appears to be 2"-4" tall.

Why can't it be like.. max 1" tall? :). Maybe esp32 PC? (Kidding)
Done forget to have a secondary identifier to further divide the seat. I recommend using a short to represent the 65536 possible slices a seat can split.

Then on the ticket, there would be an extension section that tells you the alias of the person that is about to board. We can call it SNI or Sitter Name Indicator. Another section could be an indicator if the rider is alive when boarding. We can call the extension a heartbeat extension.
Record-oriented storage and SABRE strikes again!
Couldn't put it better myself.

It'll get better as more young people vote hopefully and we can start trying to undo some of the mess. Labor and Coalition are incredibly compromised, basically bought and paid for. The more alternative parties in the senate the better, they can't buy them all out can they?
> I still appreciate it, but just imagine if it goes down due to a lawsuit. Now that Google no longer shows cached results, an entire historical record would be gone.

Or somebody accidentally `rm -rf`'s an empty variable. Or The Big One hits San Fran. Or somebody in crisis breaks in with a crowbar, matchbook, and jug of gasoline.

They're a rather old-school shop. Own their own servers, all in one location I think. Bare metal admin stuff, and data's only mirrored across two disks per file IIRC. Keeps costs down. It's what makes the whole operation possible. But I also wonder sometimes.
Add that in the dotcom bubble, internet-flavored growth had never happened before, so it was relatively harder to predict the growth of (say) Google.

But today, deep-learning-flavored growth is a 10-year-old concept, and LLMs largely have leverage over existing (versus quite new) business models. There will probably be fewer new monopolies versus the dotcom era; in particular OpenAI has lots of competition.
There are lots of web archiving projects out there:

https://en.wikipedia.org/wiki/List_of_Web_archiving_initiati...

But the web is large. And public sector or academic librarian teams tend to be small. The IA's the one that people have coalesced around.
Unfortunately a reality if you care for vintage iPhone games. Piracy is sometimes the last line of defense for game preservation.

In our case, a group of hackers have released a fangame that is in many ways equal to a modern Tap Tap Revenge, and it can be found here: https://taptapreloaded.com/
Interesting approach.

It's interesting how FP community took one issue which affects many OOP implementations and decided to throw the baby out with the bathwater... Completely ignoring the reason why OOP was invented in the first place.

I've worked on several FP projects. First of all, they're never pure FP projects because that's just not possible. Those which were close to pure FP were a tangled mess of curried functions. Many modules had weird technical names with unclear responsibilities, most features had to traverse many different files/functions with lots of unrelated data passing through various modules with detailed child state which had to be passed down from high up in the 'module' hierarchy and traverse many layers to finally get to the module which would actually use that state. Higher level modules exposed complex functions with complex input and output parameters (had to concern themselves with the highly specific state requirements of child and parent modules; including configurations!) which would have to be modified for every single high level AND low-level requirement change... I'm not surprised why big companies who use FP started using monorepos; FP makes monorepos necessary because every small change requires updating a large part of the code hierarchy because everything is intertwined with everything else (tight coupling). The higher level components have to know exactly what state the child components expect because the data comes from a central place and must be passed down.

The alternative approach would be to have each child sync itself with a global store; but then, it implies that you no longer have a single owner for each piece of state; thus, you might end up with different children which have overlapping responsibilities which update the same part of the global state, creating 'spooky action at a distance' which makes it hard to trace where the change originated... This takes us back to the very reason why FP community invented FP in the first place. In other words, FP doesn't solve the 'spooky action at a distance' problem which was its entire raison d'etre.

Frameworks like React had to invent a whole host of technical concepts and tools to help manage and track complex state changes... E.g. Redux, Saga, etc... But then we still end up with a situation where all our components are tightly intertwined with the specific implementation of that specific framework since the number of variations of how people use Redux/Sagas, etc... across different projects/companies is substantial. This means that components built for one project are generally not immediately compatible with components built for a different project. If the two projects use a different global store mechanism or they use the same mechanism but have different names for the same actions (to dispatch state changes), the components will not be compatible across different projects without a lot of refactoring to bring the component into alignment with both projects. This isn't modular! This isn't easy to read! It's not maintainable!
I've been out of the space for about a decade, so I can't say how things have continued to evolve, but the only consistent antidote to fraud has been a trusted third party.

I spent a lot of my time back then pulling in metrics from third parties like Nielsen (who do traditional TV viewership numbers) as well as companies who specialized in "viewability". We could include that data in our real-time auction and bidders would adjust what they were willing to pay based on the reputation of the ad opportunity. At least that's the theory. In practice there was so much indirection and reselling that it was hard to say what was true.

As far as the technical answer: it's a game of cat-and-mouse but we found some interesting metrics we could dig in on. One was that fps of a video hidden behind another element on the page would have a drastically different rendered fps than one in the foreground. That would be different between browsers (and browser versions) but the viewability vendors would find all those quirks, measure, and analyze to give us a normalized score. For a hefty fee, of course.
If the plants are down for retool they aren’t making either one so that would be a problem. Also if yields are poor due to mfg issues and complexity of the Blackwell architecture that will directly go to profits.
This sounds really interesting, so there are no redirections to third party apps during the booking process?
Microcenter.com (US retailer) doesn't have anything newer than 14th gen CPUs for desktops, on their site. Did Intel release a newer desktop chip already?
Union of Finite Automata
I love that so many people here think they can think about the problem for 10 seconds and come up with a solution that hasn't already been considered a thousand times and discarded.
why? making a feedback-driven servo is a well understood task. it is not hard. and even if you knew the precise micrometer position to move the head to, magically compensated for ALL variables, you'd still need a PID controller to MOVE you there, and feedback to help you measure where you are. You'll have added a significant material science problem, but solved nothing
Censored by Rockstar/Take-Two no less. With presumably an ultimatum to discontinue the project as part of a settlement of a protracted legal case [1].

[1] https://www.gamesradar.com/gta-owner-settles-lawsuit-against...
The evidence does not support this when scoped to Tesla battery packs.

https://www.recurrentauto.com/research/impacts-of-fast-charg...
At least he is willing to put his name on his opinions… unlike the one using the throwaway account to lodge his complaint.
There's nothing magic about the number 20 that makes it better than 30. The number it's just based on the marginal value of capital at the time.

If there's enough capital built up and few enough opportunities, the per can go arbitrarily high.
FTA:
“ I will not make salsa because it is a sin to cook them”

Errr, umm, what? Yes, there is a category of cooked salsas, but 99% of the salsa I’ve ever had that didn’t come from a jar wasn’t cooked. I don’t recall ever getting a cooked tomato salsa in a Mexican, Mexi-Cali, or any other southwest restaurant.

Do Europeans really cook all their salsa???

Also, salsa is one of the 3 greatest destinies a delicious tomato could aspire to.
Friend.com launch trailer
Then what was your point? Say it explicitly then, instead of speaking in riddles.
Ha! I went to a British polytechnic. There wasn’t a lot of very practical degrees ( there were some though), but there was a lot of hands on computer work in my Computer and Communications degree

It is strange on a resume listing a university I never technically went to, but now only Wikipedia remembers! And I was there before Thor destroyed it in a movie
Who's advocating for discarding the olympics? All I'm saying is that we shouldn't glorify this guy.
GP claims in profile to be Dan Green, and implies the username is to be read Dan G's UX... If that's true and just a coincidence, it's pretty dang funny. (I do doubt it though.)
They most certainly can be null as can “this”.
Ex-pat Croat here. I came for a visit recently and I can't figure out how in the world there are so many Kauflands/Lidls/Konzums everywhere. Compared to Boston Metrowest the density just seems way out of whack. Is it the lack of property taxes? Maybe it's the tourists?
But have they considered 5 digit numbers :^)
This reminds me of the Avro Arrow - the beginning of the gutting of Canada's technology and innovation development: https://en.wikipedia.org/wiki/Avro_Canada_CF-105_Arrow

One day the US President met with the Canadian Prime Minister at the time. The next day the PM scrapped the program, ordered all schematics and documents of the aircraft be destroyed.

The something like 40,000 engineers mostly then got jobs in the US.
Laser resistance can take a lot of forms. In the case of weeds, I’d bet that cat briers are already effectively laser proof. You can burn them down, but they send off shoots and store up massive amounts of energy in fragmented little potatoes. Miss any of them, and they come back up and keep going.

So that’s one solution, and it’s a big space for biology to play in. The bigger question will probably be whether or not there’s a route where weeds can make incremental progress toward better resistance from where they are right now.

For insects, as someone else pointed out, the easiest route is probably mimicry. But we might also see insects capable of recognizing the laser bots, noticing the chemical signals of burning bugs, etc.
If you know you might want to prove something's authenticity later, post the SHA256 somewhere now. E.G. Multiple social media sites. Large and trusted web archives. Cryptocurrency blockchains. The last one's a stronger proof, with lots of money making sure it stays immutable.

Or hash everything you produce/consume. Then hash the list of hashes, and post that.

Or alternatively, counter forgeries by capturing more data. For web, but all data in general. Sensor RAWs to prove an image isn't "AI". Browser and network stack RAM dumps to prove a website's authenticity. Etc. There's what, a couple dozen accelerometers, GPS's, LIDARs etc. on the latest iPhones?
rgit - https://git.inept.dev/~doyle/rgit.git/about

https://news.ycombinator.com/item?id=32213671
Interesting! I worked in an Indian food truck - owned by an Indian family - in Tucson, and we had "chili chicken" (with that spelling) on the menu. I wonder if they spelled it differently at some point.
>HTTPS is shrouded behind inscrutable crypto, but nearly everyone trusts it with their credit card details.

Credit card via HTTPS has a second layer to it though, the accountings/auditing layer. You can't achieve that with secret ballot voting without throwing out the secret part.
Cheaper is better, having to pay more for productive assets isn't a good thing.
I am 75 now. Honestly, contracting jobs were part-time at best, so work just wound down. My wife at the time was a Registered Nurse (you want to talk about job security?) and 5 years younger, so she never understood how hard it was to be an older techie without a big network.

She filed for divorce and I'll say more to matt_s in this thread about what to do or not do in retirement as I collect my thoughts. Divorce is not helpful, but I started collecting Social Security, and then we got separate places just before and after the home sold. Kind of a rough landing.
SSI is a very useful (and underdocumented!) RPi feature - it’s how socket-compatible Raspberry Pi 68k emulators work with the ~60ish latches that interface with the 68k bus.
I mean, a bunch of those are timing issues in speculative execution, you could make an argument that it's working as designed but people didn't anticipate the existence of timing exploits. I'd call that different from computation errors.
Ask HN: Why victimize a previously reference page in second-chance algo?
https://web.cecs.pdx.edu/~harry/os/slides/Ch3-MemMgmt-2.pdf

Visit page 16 of the slide.
You'll see second chance page replacement algorithm.

When page fault occurs and reference bit was 1, it is set to 0. I don't get the reason behind doing this? What problem are we trying to solve here?
Arguably the question is whether:

- The edge is large enough

- The provider has sufficient capital to exploit the edge

I guess if you can prove the edge, you could find capital, but I really have no clue how difficult that might be.
Decline in data for AI bots to scrape
> Have I been living in a fantasy bubble where CPU's do exactly what you asked of them (and errors come from not holding it right)?

These are gaming CPUs clocked right up to the threshold of stability (and in some cases, past it)

Server CPUs with ECC RAM are significantly better.

However, if you haven’t experienced much CPU instability, you may not have operated at scale where it appears. Get into the scale where operations occur across 100,000s of CPUs and weird things happen constantly.
And it has, clearly
From MLOps to ML Systems with Feature Training Inference Pipelines
Obviously the solution is airline code + iata source airport + iata dest airport + airline scheduled flight # for the day/week

UA-LGA-LAX-001

LH-LHR-FRA-012

/obviously/
Can confirm college campuses are a gold mine at the end of the spring semester. TVs, iPads, speakers, mini fridges, furniture galore mostly in like-new condition. I worked for the school while I was a student so I stuck around in the summers and had the opportunity to make a bit of extra cash dumpster diving once everyone was gone.
It looks like the entire purpose of the project was to turn "Never Gonna Give You Up" into "Take On Me" in the most indirect and random way possible.
I remember my wife was on a charter flight with 3 initial letters many years ago (in Europe). And when I tried to look up the arrival, many systems could not handle the flight number.

Now slightly unsure whether I did not dream up the whole episode, I did a web search and found https://travel.stackexchange.com/questions/157429/what-is-th...

So IATA seems to have formally introduced that in 1994. (Whether they have abandoned it again later I don't know.) So big airlines could just get a additional 3rd letter(s). The first 2 would not have to change, which makes it easier for humans.
I worked at a company that did this.

Here is the formula for viewability:

Percent In View = Area of the Intersection of the Ad and the Viewport / Area of the Ad

You would get the area of the ad using getBoundingClientRect, and the area of the viewport using window.innerWidth and window.innerHeight.

It was not possible to do this if the ad was within a hostile iframe (cross origin iframe) so you needed to use a third party source for this information like SafeFrame.

All of this was greatly simplified when Intersection Observer was officially supported by modern browsers.
OP - any relationship to your username?
tar -zxvf git-2.46.0.tar.gz
cd git-2.46.0
make configure
./configure --prefix=/usr/local
make
sudo make install

rm -rf /usr/local/libexec/git-core/git-credential-cache*
As the original comment suggested, about 5-6 of these are not related to timing exploits (or at least, not the Meltdown/Spectre variants which claim so many patches to their name). Summaries from LKML and Kernel.org:

> apic_c1e

Both ACPI and MP specifications require that the APIC id in the respective
tables must be the same as the APIC id in CPUID.

The kernel retrieves the physical package id from the APIC id during the
ACPI/MP table scan and builds the physical to logical package map.

There exist Virtualbox and Xen implementations which violate the spec. As a
result the physical to logical package map, which relies on the ACPI/MP
tables does not work on those systems, because the CPUID initialized
physical package id does not match the firmware id. This causes system
crashes and malfunction due to invalid package mappings.

The only way to cure this is to sanitize the physical package id after the
CPUID enumeration and yell when the APIC ids are different. If the physical
package IDs differ use the package information from the ACPI/MP tables so
the existing logical package map just works.

> taa

TAA is a hardware vulnerability that allows unprivileged speculative access to data which is available in various CPU internal buffers by using asynchronous aborts within an Intel TSX transactional region.

> itlb_multihit

iTLB multihit is an erratum where some processors may incur a machine check error, possibly resulting in an unrecoverable CPU lockup, when an instruction fetch hits multiple entries in the instruction TLB. This can occur when the page size is changed along with either the physical address or cache type. A malicious guest running on a virtualized system can exploit this erratum to perform a denial of service attack.

> srbds

SRBDS is a hardware vulnerability that allows MDS techniques to infer values returned from special register accesses. Special register accesses are accesses to off core registers. According to Intel's evaluation, the special register reads that have a security expectation of privacy are RDRAND, RDSEED and SGX EGETKEY.

> mmio_stale_data

Processor MMIO Stale Data Vulnerabilities are a class of memory-mapped I/O (MMIO) vulnerabilities that can expose data. The sequences of operations for exposing data range from simple to very complex. Because most of the vulnerabilities require the attacker to have access to MMIO, many environments are not affected. System environments using virtualization where MMIO access is provided to untrusted guests may need mitigation. These vulnerabilities are not transient execution attacks. However, these vulnerabilities may propagate stale data into core fill buffers where the data can subsequently be inferred by an unmitigated transient execution attack. Mitigation for these vulnerabilities includes a combination of microcode update and software changes, depending on the platform and usage model. Some of these mitigations are similar to those used to mitigate Microarchitectural Data Sampling (MDS) or those used to mitigate Special Register Buffer Data Sampling (SRBDS).
It’s a very, very low effort shitpost about Peter Thiel feigning to “understand” him but just talking shit about him. Did you even read it? It should be flagged if anything. It is uncharitable from the headline downwards.

I’m calling it out for what it is. People are free to attach their name to whatever they like. HN is an anonymous tech discussion forum.
Reverse engineering a day's worth of websites
Are the car/rocket that different?

There’s the stories of college professors who split their class into two groups, one group that is graded on quality of a single photo/pottery submission, and the other group graded solely on quantity of work produced, and the group tasked with producing quantity always produces higher quality.

I guess I don’t see why building a car or rocket would be different, other than we now know how to do it well.

When people were first building rockets, it was just a blooper real of failures.

Is there some distinction along figuring out the theory/physics, versus figuring out the application, real world, material science angle? Like I could see spending a long time on the theory side, but once that’s understood, it seems like figuring out which materials can produce the required physics is quick iteration’s bread-and-butter.
It's possible for bots to bypass the "hard" captchas or tracking captchas too. Or even pay click farms to solve captchas for you.

The only real value in captchas isn't to stop bots, but to make it more expensive, or slower, for an adversary to abuse your service at scale.
Building the Micro Journal
Date-fns: Modern JavaScript date utility library
I came across a recipe [1] for salt curing without doing a water rinse after curing. The idea of using only enough salt to cure the meat made a lot of sense to me, most recipes end up with way too much salt that you have to wash off afterwards.

I stuck with the 2.5% by weight ratio of salt to bacon. We have a nice chamber vacuum sealer so I used that to seal the meat while curing it. I don't have a slicer unfortunately, but partially freezing the slab right before slicing made it easy enough. Slicing soft pork fat is no fun, getting the meat a bit stiff and icy works wonders when slicing!

On the first batch I used maple syrup basically the same as the recipe. The author noted wanting to double the amount of syrup - I stuck with 2% by weight and it was almost too sweet for me, I wouldn't do more.

I actually just sliced and packaged another slab tonight. For this one I did half as much syrup and did a pretty strong costing of cracked black pepper. No clue how it will turn out, but it smelled great when slicing it! I'll probably try a few slices tomorrow morning before freezing most of it for later.

[1] https://tasteofartisan.com/how-to-cure-bacon/
Generally it's easier to book a trip with legs on different carriers if they have a codeshare arrangement, because you can just do it as a single itinerary through one carrier's web site. Otherwise you often need a travel agent to be able to put together the itinerary (that's not strictly necessary though, just the way they make it work so no technical reason they couldn't just offer non codeshare flight numbers)

The other thing is airline points/status - sometimes you get no status points/miles on non-codeshare partner flight numbers but you do on the codeshare flight numbers.