skysight-inc/HackerNews huggingface dataset:
You could have a pretty bleak outlook on government-corporate graft and corruption and still recognize how ridiculous the idea of Mike DeWine and Pat Gelsinger in a strip club is.
Coding Adventure: Optimizing a Ray Tracer (By Building a BVH) [video]
There’s also no package caching across venvs(?). Every time I have to install something AI it’s the same 2GB torch + few hundred megabytes libs + cuda update of downloads again and again. On top of that, python projects love to start downloading large resources without asking, and if you ctrl-c it, the setup process is usually non-restartable. You’re just left with a broken folder that doesn’t run anymore. Feels like everything about python’s “install” is an afterthought at best.
Attestation is going to be abused. The only thing it is useful for is establishing centralized control over client software. That'll eventually imply that all clients are user hostile, probably both from a surveillance capitalism perspective, and from a government surveillance perspective.

This isn't a theoretical concerns. All of the groundwork (except device attestation at login) has already been laid:

- The US CLOUD act already says that service providers have to provide the government with access to all information they're technically capable of accessing.

- Microsoft's existing client debugging mechanisms allow them to pull files from windows machines with management approval.

Once there's a de facto ban on running web browser binaries that aren't produced by a FAANG (established by the passkey standard), all the vendors have to do is add MS-style telemetry / debugging, and it's game over. In all likelihood, there will be legislation in a few years that forces any holdouts to implement that sort of a mechanism.
It reduces the number of shares on the public market, not the total number of shares.
This can drive the price up if there is high public demand for the now reduced number of shares available
I see a lot of confusing chatter about RCS (and maybe that’s the point).

Does anyone actually have a good write up on E2E encryption and whether or not all messages will actually go through google’s servers in plaintext? As in, not Google marketing.

Seen a lot of chatter and it seems like it’s is complicated on both fronts.

Only mildly worse (depending on the answer) than sending an SMS already but really makes me question the push for it in the first place
Except the "$200K" is purely paper, and has an expected value of closer to zero. Remember, common shareholders are the last ones to get paid. Investors have preferences and get paid back first (often with interest.)

Also realize you were probably forced to take a pay cut and have a below average salary due to cost-cutting measures from the board. We'll ignore the non-financial problems, like tons of stress, complaining employees demanding more equity because you couldn't give them raises...

No, it's not a good situation.
Relying on GPT style systems to translate high level math to lean stuff strikes me as dangerous unless you're going to double-check by hand that the LLM didn't suddenly decide to hallucinate parts of the answer.

Granted, the hallucinated part might not pass the final Lean verification, but ... what if it does because the LLM did not properly translate the mathematician's intent to Lean language?

I'm thinking the human will still need to read the Lean program, understand it and double-check that his original human intent was properly codified.

Better than having to produce it by hand, but still sub-optimal.
Could you imagine how different things would have turned out if the vaccine was ready while Trump was still in office?

The right wing media outlets would be praising it and claiming that it was everyone's patriotic duty to get vaccinated.

The left wing media outlets would be pushing out articles and documentaries about how vaccine compliance is rooted in implicit white supremacy.
I’m surprised they didn’t touch on the Internet as a factor. Before, dinner parties were the best way for friends to catch up and talk, and fill one another in on their lives. Everybody would gather around for hours, and talk about new things going on in their careers, their children, other friends, news, sports, you name it.

Nowadays, you can just hop onto your group chat(s) and fill everyone in on these things in real time. So, the dinner party became less of a necessity for social interaction; and the actual dinner itself was never the point. With less of a need to hang around for hours on end to catch up, it’s become more efficient to just go to a restaurant, spend an hour or so, and then leave. Nobody is left to clean up, or spend half the day preparing meals.
Tha vast majority of military chip requirements can be met with old processes. You don't need a 5nm chip with a 13 billion transistors in a F-35 or for the guidance module in a cruise missile.

Very modern chips are more suited for intelligence work no weapons systems per se. The physics of flight, artillery and balistic missiles is pretty much well understood, we don't need machine learning for that. Some modern systems use computer vision as a terminal guidance system, but again, you don't need state of art semis for that.
I can't even do that with other humans - or they can't do that with me, or some combination of that.
This assumes that the APIs work this way?

What if the first call is to get a resource that expires and then the last call fails?

Now it will retry but with an expired resource (first call is saved).
Rarely does one see a C++ quick start guide that's actually this quick: https://lexbor.com/docs/lexbor/#quick_start
Sure, you can reach out to 'hello' at our domain to send a message to the team!
Dunno but I believe the power of using LLMs to turn the light off and on might outweight much of the gains. No clue about proportions.
Stunning Shrine with Rare Blue-Painted Walls Unearthed at Pompeii
I use both, and I find WhatsApp much more fun, so maybe this is just a matter of habit/convenience.

iMessage is regularly glitching out for me, doesn't work in the browser, has a more confusing sent/received/read indicator system than WhatsApp in group chats (not that I particularly care about the "read" part, but knowing who actually had signal and received the message is useful when traveling internationally), and most importantly isn't available with all of my contacts.

WhatsApp location sharing works just as well in my experience.
Cuba was more of a sovereignty/sphere-of-influence problem than a nuclear-warfare problem. That ship has long since sailed with regard to Russia's borders. Moscow is half-surrounded on the west, as well it should be given its history of combining expansionist behavior with atrocities like communism and the Holodomor.

The Russians have had more than ample opportunity to join the civilized world and stop acting like dicks, but that's apparently not what they want to do. So, containment it is.

And if they feared NATO encroachment on their borders, trying to take over Ukraine was a really stupid way to discourage that. Nukes are scary enough, but nukes in the hands of stupid people are downright terrifying. Personally I doubt any of theirs still work, but that's all too easy to say.
Data Structures and Algorithms, Correctly
What sounds revolting, sorbet?
Well, who you gonna believe?

A. Some random folks on the internet who have looked at a single picture of a chess piece and maybe play themselves, but apparently no other qualifications.

Or:

B. Medieval historians who have years of education and study, deep familiarity with the subject matter and publish books and papers on the subject, as well as consulting with historians of chess, and who have compared it to other well known, well studied chess sets from the era.

I don't think the latter are infallible, but without something pretty compelling from the former (evidence? what's that?), I'm gonna go with the latter.
Why would I use this instead of github code search, which appears to be quite comprehensive?
Europe was happily buying more and more gas from Russia and wanted to increase trading until the directional change from Putin.
Python was first released in the early 90s. If you compare Python packaging to other languages of its time, its not so crazy. For comparison, C++ was released in '85.
I think also you will see Democrats even in blue states back off on any unpopular policies so it can’t be used as ammunition against Biden as they see a Trump victory as that catastrophic.
https://en.wikipedia.org/wiki/Oil_City,_Pennsylvania
Don't think so. The article emphasizes that it's nearly as long as a football field. So, if it's an error then it's with their source.
I don't personally believe this immutability property should be used for handlers that run for more than say 5 minutes. Any longer than that, I'd suggest the use of delayed calls, which explicitly will serialise the handler arguments instead of saving the whole journal. I agree executing code that is even just an hour old is unacceptable in almost all cases.

Obviously you can still sleep for a month, but I really see no way to make such a handler safely updatable without editing the code to branch on versions, which can become a mess really quick (but good for getting out of a jam!)
What if the code was changed by the time it is retried? I imagine it would have to throw away its memorized instructions, and because the code isn’t idempotent…
Let's not forget that FAANG companies were all startups at one point. Early employees at those companies experienced significant upside. Startups can be very high risk, and in rare cases, extreme upside.
I have faith in Google.

They will surely create and shit-can a dozen texting apps in the next decade. One may even fit my purposes until it too is shit-canned.

Nobody has more experience in building text apps than Google.
There isn't a competitive market, there's a shortage of doctors and healthcare workers.
Because despite the a slight shift in political tone, making profits on HN is still hugely unpopular. Even if it is a for profit under a Non-profit Foundation.
Reminded me of Quake's trick[1] of calculating the perspective correction every 16 pixels, as you then effectively got it for free on a Pentium processor.

[1]: https://www.bluesnews.com/abrash/chap68.shtml
I’m Dutch and so live in a WhatsApp world. Still I lobbied my family hard to keep our family group in Messages. Reason being that we often share photos, and nothing ruins a nice photo as much as the insane compression and low resolution that WhatsApp applies.
I'm not on X much these days, but when I was, the greatest benefit of likes for me was when I would tweet something, I could see the folks who liked it. This has not changed.

My greatest annoyance around likes was how my feed would include "So and so like this" type tweets. Maybe that still exists, but if they removed that too, it'd be a welcome change.

Lots of great points being made in this thread, but for me personally, such a change would not affect my experience on the site.
> Use encrypted messaging protocols — iMessage, signal, WhatsApp…

Using RCS E2EE is trivial. The way google does it is to simply pack signal protocol messages in the RCS message payload. It works great and it's simple.

Key identities are managed with a central identity server (like signal does) of course but that's because it's only supported on Google's jibe platform.

This can be trivially resolved by having each carrier who supports E2EE to host a key identity server so that you can lookup keys by phone number (which RCS already uses to point you to the right federated carrier service).

All that's missing from RCS having E2EE by default is google having literally anyone else adopt RCS forcing them to properly federate E2EE.
Great point! From some of our case studies we see users catch 25% more 3 days earlier than other solutions.

To your point catching every threat or every alert especially on darkweb is always a cat and mouse game. Our idea is a prioritization problem – how do you mitigate the biggest risks quickly.

The existing OSINT tools we used are keyword search based / pretty noisy so we’ve been focusing on the idea that given there’s no way analysts can find or triage every alert, how do you catch the biggest stuff. We do a few things from AI crawlers to continue to expand data collections to AI categorization, clustering, data extraction etc to make it easier to track the cover the most ground.
Goodhart’s law at work.
You should be able to unload the kernel modules that talk to the mic, and then set up some sort of software source using ALSA or one of its successors.

It'll probably be extremely fragile vs. the openbsd mechanism of having a bit set in the kernel though. (Most Linux configuration stuff is extremely fragile + complicated these days, so that's kind of par for the course.)
this isn't a cool take (specifically words like "kinda obvious" and generally the sentiment which obligates the reader to have awareness of the subject) and we shouldn't assume readers here know everything or a single thing is "well known".
I don’t think I am understanding what you mean, but isn’t one of the potential use cases of AI to say: “Siri order me the thing I always get from _restaurant_ and it navigates the app for you in the background? Potentially this can be done without API integration; the AI synthetically operates the app. Maybe it “watches” how you used the app before (which options you choose, which you dismiss, etc) to learn your preferences and execute the order with minimal interaction with the user. This way annoying, bad, UI can be avoided. AI “solves” UI in this way?

Are you saying this type of scenario kills the app, or are you saying the app needs to die, replaced by an API that AIs can interact with, thus homogenizing the user experience, and avoiding the bad parts of Apps?
> Could you elaborate on that?

What I mean is that executing a software artifact from, lets say, a month ago, just to get month-old business logic, is extremely dangerous because of non-business-logic elements. Maybe it uses the old DB connection string, or a library with a CVE. Its a 'hack' to address old code versions in order to get the business logic that a request originally executed on - a hack that I feel should be used for minutes, not eve hours.
I don't doubt that, and have heard it several times from other people as well.

Sometimes I think that keeping SMS and especially MMS ridiculously expensive was the greatest unintentional gift European mobile network operators could have ever given their customers:

People now just accept OTT messaging as a fact of life, and enough people will be able to provide that type of tech support, just like they'd fix a parent's or friend's internet connection in case of problems.
The problem with all the original iterations on these assistants is that they fail so often that people stop using them for anything except for the few things that they can do reliably which for most people is basically setting timers, playing music and turning the lights off and on.

They're annoying to use, because the interface sort of implies affordances (like, you know, just talking to it like a person) that aren't actually available, and really it's just a menu tree that's barely more sophisticated than a customer support call tree.
500'000 million packages, times n versions, all of that evolving over 30 years.
Huh, I assumed Nvidia would have already surpassed both of them. I guess it is still in third place.
The only fair way to analyze this is by looking at opportunity cost, which isn’t what TFA does.

Founders often have slightly higher market value (though not always) than first employees, so they are giving up more to go the startup route.

Separately, TFA further underestimates founder risk as they are typically not taking salary during pre-seed, and no or low salary during seed. However employees 1-5 typically get mostly cash, often much closer to market.

Thirdly, there is also often a lot more stress in being the founder. It is a complex, all day job. You have the weight of keeping things going for all employees, and when cash is low it’s your paycheck that gets delayed/cut first, not your employees.

That said I am all for reasonable early stage liquidity where it makes sense, but as many other commenters have mentioned, it tends to not be life changing super early for most early employees. Most employees would rather keep the bet on the table. Also, I am strongly against large founder secondaries. I think it’s helpful for founder to remain feeling “not financially successful”, especially first time founders, so that they keep their heart in the game. I followed this practice with my companies.
That is what you get when you cut the budget of the EPA over and over. Hate to be snarky, but there is a reason for EPA oversite.

Maybe this will get people in Texas understand why the EPA is needed.
Brain's structure hangs in 'a delicate balance'
The title should include that it is from 2013.
This could be really useful if it searched other code forges as well.

It would increase visibility for projects that don't want to use GitHub as a host for their code.

Most open source projects are completely dependent on Microsoft for their visibility.
uv by astral is cleaning up and improving a lot in this area right now
On the other hand, an open kitchen makes it easy for children or pets to get into the kitchen and accidentally turn the stove knobs, grab/eat something they shouldn't, or knock something over (including glass and knives).

But yeah if you can keep your kid contained but within eyesight I guess it works. You can always use a camera for the eyesight part, though.
So non-response time bound workloads that need to reliably dispatch other processes to completion?

Would a good example be something like, automated highway toll collecting? i.e. I drive past a scanner on the highway, my license plate is scanned and several state bound collection events need to be triggered until the toll is ultimately collected?
Yeah we prefer to keep our messages out of the hands of Facebook
Luma Dream Machine: Generative text/image to video
> where the code doesn't have to be idempotent

Is that true? I don't think that makes any theoretical sense, since I'm pretty sure the whole thing relies on transparent retries for external calls.

If I complete some action that can't be retried and then die before writing it to the log (completing an action unatomically) there would seem to be no way for this to recover without idempotency.
I wholeheartedly agree!

I worked with the IMS (the standard on which the RCS standard is based) in grad school and the best article I read on it was called something like : "IMS, a useless subsystem"
The Python packaging ecosystem is 25+ years old, and was largely informally specified until ~12 years ago. Most of the complexity in Python packaging can be traced back to (1) a large degree of pre-existing permissive behavior that needed to be encoded in early standards to get standardization off the ground, and (2) the fact that Python packaging is still largely federated, with multiple independent groups performing tool development (and interpreting the standards).

(2) has historically also been a strength of Python packaging, and has been a big source of modernization efforts over the years that (IMO) have made packaging much better: things like pyproject.toml, build backends, etc.

(I think there have been a few recap talks at PyCon over the years on packaging's history. There are definitely people way more qualified than me to provide a more detailed summary :-)).
> I was of course just thinking about the "front" of the execution, when you're sleeping for 2 days and you want to switch out a future step. Switching out logic that has already been committed is a harder problem. That's a goo point.

You make a good point - this is the idea behind 'delayed calls' which are really one of my favourite things about Restate. Don't save all the intermediary state - just serialise the service name, the handler name, and the arguments, and store that for a month or whatever. That is a very tractable problem - ie just request object versioning
That is mostly SMS fault. It doesn't guarantee reliable delivery either in theory or practice, and the carrier will happily drop messages if a resource limit is exceeded. Essentially all of the IP-based chat protocols are reliable, whether that is WhatsApp or iMessage.
> All you’re saying is that in the contemporary context it’s exceedingly foolish to be an employee at an early startup. The VCs and founders have optimized away all the incentive. Eventually the message will reach even naive 22 year olds.

My startup idea is a firm that uses generative AI to flood the internet with pro-startup, pro-VC, pro-founder propaganda, so that message will never reach the naive 22 year olds. Personally, I think it's like saving the environment, since naive 22 year olds are precious resource we cannot allow to be destroyed.
> The article is written in english which is important here.

From said article:

> This paper is a translation of the original paper in Spanish “Computadoras Mexicanas: Una Breve Reseña Técnica e Histórica” by Daniel Ortiz Arroyo, Francisco Rodríguez Henríquez, Carlos A. Coello Coello
The part of my family that all uses Samsung phones still can't rely on group chats between themselves, so I think it's them.
Cool. Thanks. Started in with the newest version of VS 2022 recently for C++, and then find out there's apparently something better in a different internal fiefdom that people actually like.
It would be nice if all packages (and each version) were cached somewhere global and then just referred to by a local environment, to deduplicate. I think Maven does this.
Given that OCB (appears to be?) is more computationally efficient than GCM, is there any reason why OCB shouldn't be favoured nowadays given there are no IP issues?
The BBC generally tends towards the center-left, but also takes some characteristically right-wing stances - they they have at times been vocally anti-trans), they were on balance pro-brexit, and they tend to lean right on immigration and religion.
'One of the great wonders of nature': Insect migration superhighway discovered
This 100%. Really the only reason to work at a startup as an engineer is if you really want to, because everyone pays low and the tiny bit of equity is essentially worthless in 99% of cases, which gives it a very low value.
Great question! https://news.ycombinator.com/item?id=40659687
An interstellar cloud may have caused an Ice Age on Earth
> edit the raw files

Shit, I didn't even consider the editing part.

A pair of 4K images (one 4K image per eye) with 8 bits per channel is nearly 50 MB per frame uncompressed. At 90 fps, it's a whopping 4.48 GB per second. 268.8 GB per minute.

I can't imagine they're actually doing the editing in uncompressed form. Even a modest 15 minute scene would be 4 TB, which after typing out, I suppose isn't actually THAT big. If they had an hour of footage, that's 16 TB, which is certainly big, it's not insanely big and could be done on consumer-grade SSDs.
This is an incorrect summary: if you read beyond that, name canonicalization is not a significant hurdle. The larger hurdle is the fact that wheel filenames support compressed tags, which themselves lack canonicalization.
In my experience the best Canadian devs came to the US specifically because they could make so much more. Not sure if that's changed much over the past 5 years given the explosion of remote work.
Looks really awesome. Always been looking for some easy to use async workflows + cronjobs service to use with serverless like Vercel.

Also something about this area always makes me excited. I guess it must be the thought of having all these tasks just working in the background without having to explicitly manage them.

One question I have is does anyone have experience for building data pipelines in this type of architecture?

Does it make sense to fan out on lots of small tasks? Or is it better to batch things into bigger tasks to reduce the overhead.