skysight-inc/HackerNews huggingface dataset:
I don't think a regular stovetop can get a pan to 450°C, my gas stove gets an empty pan to about 300°C maximum. It doesn't happen in normal situations, if it happens it probably means you forgot your pan on the stove. Heating Teflon at 300°C for several hours is bad, but personally, in that situation, I would worry more about causing a house fire.

Teflon flu is a thing, but it is relatively rare, especially considering how widespread Teflon pans are. That's a few hundred cases per year in the US, by comparison, there are about 1000x more house fire, with cooking equipment being a leading cause.
I look down my nose at both x and tiktok users lol
The standard I was replying to was:

> I haven't found any pieces of the car functionality

Any functionality.

I agree though. Any critical driving function should be physical. Like the podcast ad skip button on the steering wheel, one of the most important control components in a modern car.
>the good things are the things you don't notice; the things that just work

sorry, no, at least in any meaningful sense, because init already just worked for me.

and when something didn't, I could find how to fix it in a way that was transparent and I understood and could even modify or make better, without being connected to the internet looking for cargo cult incantations on stack overflow

init was a tool; systemd is an adversary
Do you have a recent example of a professional designer doing “light-grey text on a white background”?

Because the designers I’ve worked with would never ship that. But maybe I’ve just worked with competent designers.
Cost is a big thing, but also configurability. While you can assign different functionality to different buttons, it's easier to add features after the fact to a touch screen. While this can be both a blessing and a curse, I own a new model vehicle from a startup car company, and the interface has improved significantly in the past 2 years with OTA updates.
> following non-Rust naming conventions […] impossible.

That’s indeed the point.
I agree, that was one step too far. I really think there needs to be some regulations around what controls should be physical.

Thankfully, Japanese and Korean cars still have ergonomics. Hope they stay that way.
I think you’re getting downvoted so heavily because most of HN dislikes anticompetitive behavior from big players. Having no FOSS solution for RCS is a problem. So is silently breaking the OSS user’s text messages.
Mobile-focused MitM tool with a built-in VPN setup and easy-to-use proxy UI?
Hey all,

I’m working on a MITM tool tailored for real-time mobile traffic analysis that might fill some gaps left by existing options like mitmproxy or Charles. Here’s the pitch:

VPN-Based Setup: The tool works via a VPN configuration that includes an automatic certificate installation process, so there’s no need to be on the same local network as the target device. This makes setup easy, even for mobile testing on the go.

MITM Proxy-Style UI: Users get access to a familiar proxy-style interface displaying all captured requests in real time, with filtering and sorting options.

I’m interested in feedback from those who regularly use tools like mitmproxy or Burp. What features or pain points could this address? Would the VPN setup be valuable in your work?

Thanks in advance for any insights!
No worries at all! I'm more commenting on this as a trend even from people who post Show HNs of their own than asking for specific changes to this project!

Do what's fun for you, no more, but definitely polish it up if you're looking for broader uptake.
There is no better way.

The general idea is that you should pay the cost of handling an error right there where you receive one, even if you're just going to return it. This reduces the incremental cost of actually doing something about it.

If you're given an easy way out, a simpler way of just not handling errors, you either won't even consider handling them, or you'll actively avoid any and all error handling, for fear of polluting your happy path.

I can't say I agree with the approach all the time, but I know I'm much more likely to consider the error flow doing it the Go way, even if I'm comstant annoyed by it.
The automatic stop-start system found in newer cars isn’t especially hard on the starter. These systems have reinforced bearings, faster engagement mechanisms, direct fuel injection or integrated starter generators, which start the engine without relying on a starter motor at all.
This is going to be impossible to answer definitively because we don't know exactly what materials the cloth was made of and what additives or dyes it may have contained or absorbed. If it was brand new I would be a lot more worried, if it has been previously washed a few times and only used to clean kitchen messes I would be less concerned. In very general terms polyester is food safe and they sell boiling bags made of polyester. Polyamide cooking utensils are advised not to be used above 70C due to potential leaching of contaminants, but there probably simply isn't very much material in terms of weight to create an issue.

Overall, if it was a brand new cloth or had previously been used to clean toxic chemicals like motor oil, you should discard all of the remaining food. If the cloth had only been used food spills and previously washed...I still wouldn't eat it, but I could see why someone who is more chancey with their food might.
Perhaps you could elaborate? It would be helpful to understand what Redis can do that cannot be done easily with local memory.

Acting as shared memory for an inherently single-CPU language like JS is one I can think of. However, I don't use Redis, so you'd be better placed to drive the discussion forward with examples.
Ancient Paw Print on a Pottery Fragment Is Oldest Known Evidence of Cat Kneading
Same as mine. I also pass the `-r` flag to xargs so it doesn't run if there are no inputs.
Prank calling was definitely still alive and strong in the 90s. At least they were we me and my friends. And not the "heavy breathing" kind, just silliness. In middle school I spliced a phone cord so my friend and I could prank from the same room. When we got 3-way calling, we would be able to prank with each other from afar AND we could each call another (unsuspecting) party and get them on a you-called-me call together. Good times :)
One shouldn't be adjusting practically any of those things listed while driving. That makes having it as a physical control moot. And having physical buttons to navigate a selector on the screen is still a terrible thing to do when driving anyways.

My rule of thumb is if it's on the center console I shouldn't be messing with it when the car is in motion. If I'm supposed to mess with it while moving it's on the wheel or immediately around it.

And tbh between my car with a zillion buttons I shouldn't be pressing while driving and a small screen and the car where most of those functions I shouldn't mess with while driving are on the screen I prefer the screen. Far bigger screen to quickly glance at the maps when driving instead of a smaller one that's harder to see. Less space to actually see the media collection when I'm stopped and can safely navigate it.
But I don't want discoverability when my windshield suddenly fogs up and I can't see anything. I want to be able to just reach out and adjust the airflow without even thinking about it when I start noticing the fog in the first place.

Last time I had something useful was in my Volvo 740. After that it has been getting worse and worse. Even physical nobs can be bad, just round and smooth, without any physical notch that snows what direction it points.
To add some feedback as someone whose company replaced redis with PgSQL after I lobbied for it (leveraging my experience using it in bioinfo HPC beforehand):

- agreed, autovacuum is definitely something to keep a close watch on – but as long as disk I/Os are fast enough (i.e. not EBS), our queue tables could fill the space freed for PgSQL but not the OS (the non full VACUUM mentioned by my GP), so in the end, assuming the queue did not grow infinitely, actual disk usage stabilized, and we never had to VACUUM FULL outside of buggy (on our side) situations;

- high-throughput is relative: we ran in the range of hundreds to thousands of tasks per second without any issue nor any particular customization, so sure, PgSQL will not hold the load if you are Google, but I'd bet it should satisfy the needs of at least up to the last centile of companies.

- I like your idea about timestamp-defined partitions, I will definitely keep this one in mind if the need arises.

Now on the pros:

- being able to store & manipulate basically all the data handled by our stack from a single source sounds like a minute detail, but actually helps a lot when we have to debug an issue;

- being able to use virtually any language and still be able to access all the persistent data from our stack from a single source revealed itself to be an unexpected advantage to develop a quick'n dirty e.g. python/nim/racket script to explore data/debug/generate stats/etc.;

- our PgSQL machines ran much better “by themselves” than we feared at first, and finally were far from being the main point of contention on day-to-day ops – in the end we just altered a couple of settings and just... let them be;

- PgSQL provides a lot of tools to inspect it live, which provides additional help to identify bottlenecks in (i) your server setup and (ii) your stack;

- PgSQL support of JSON/JSONB is actually very good, and very helpful to store that hard-to-normal-form-ize last part of your data.
Regardless of how you feel, patients aren't the ones paying most of the bills so their desires are way down on the list of priorities for the healthcare system. If you want your desires to matter, and you have the money, then you can pay extra for a concierge medicine service. Otherwise since we have increasing demand for healthcare with flat supply you can expect longer waits and less personalized attention from increasingly stressed out doctors.

I'm not trying to be mean to you, just explaining the reality of the situation.
People voluntarily watching their favorite stuff that occasionally offends yyour sensibilities. Perish the thought!

The situation on the ground is that YouTube suppresses a lot of harmless videos and channels under the pretense that it is "extreme" stuff. They also demonetize anything they like and you have no recourse as an uploader, unless your channel is making them insane money and they want to keep you at all costs. What good would subscriptions be for if they did not increase the odds of you seeing sub videos in your feed? Stop trying to tell people they shouldn't watch stuff you disagree with.
I think there is one use-case for them: Plugging them into public usbc charging ports.
> Perhaps you could elaborate?

IPC, I suppose?
Taking this on a tangent, but an awesome easter egg in that scene is the Terminators other finger is pointing to an entry for "John Connor" in the same phone book.
Over the network became feasible when HDD got markedly slower than NICs. It’s a nearer thing with NVMe.

I want a “redis” with something akin to the Consul client - which is a sidecar that participates in the Raft cluster and keeps up to date, cheaper lookups for all of the processes running on the same box.

The few bit of data we needed to invalidate on infrequent writes went into consul, and the rest went into the dumbest (as in boring, not foolish) memcached cluster you can imagine.

But as you say there was the network overhead, and what would be lovely is a 2 tier KV store that cached recent reads locally and distributed cache invalidation over Raft. Consistent hashing for the systems of record, broadcast data on put or delete so the local cache stays coherent.
Close-Quarters Kinematics, used in robots in tightly constrained environments.
Looks interesting, I’ve been investigating Postgres CDC solutions for a while, so I’m curious if this could help my use-case.

Can you elaborate on failure modes? What happens if e.g. NATS server (or worker/replicator) node dies?

In principle, how hard is it move data from Postgres not to another PG but e.g. ElasticSearch/ClickHouse?
And VS on an old laptop or Virtualbox might actually work, still. Good luck recreating some random services tangle from the year 2024 in 2034.
That doesn't sound like it secures anything. I can't verify that my prime number is unique (I vote for A. There is already a vote for A at 3. The machine logs a vote for B at 5 and reports to me my number is 3). So it'd be a scheme where nothing can be proved to me that I didn't already know. I still have to trust all the same middlemen, and I don't gain any knowledge about the integrity of an election.
I don't mean to belittle your app, I can't try it 'cause I don't have iOS.

We did solve the problem in a much easier way though. We do have 40 recipes we usually cycle through. I wrote them in a spreadsheet and marked them based on who can cook them, if it's brunch, lunch or dinner, quick or elaborate, summery or wintery.

Then in another sheet I just create a list of those recipes/dishes picked randomly based on the day of the month.

If we start the discussion "what do we eat tonight", I can just open the spreadsheet. 99% of the time proposing the option for that day on the sheet gives us closure and we're done.
> How many people eat McDonalds?

If you’re already starting like this it’s obvious that the following text will be non-scientific non-sense.

As a reminder: There is no such thing as “healthy food” and “unhealthy food”, there is just healthy and unhealthy nutrition.

Still baffles me that people think it would actually be legal to sell actual unhealthy food, i.e. poisonous food.

Also, “organic food” is just a marketing scam. If you think your nutrition is better off if you stick to nature, you’ve missed a large part of human history where people starved to death by the thousands every year because they exclusively relied on “organic food”.

systemd runs on billions of systems worldwide and everyone who ever professionally maintained enterprise servers understand what a bad approach the crude hack that SysVInit with its collection of shell scripts was.
That's more the risk than the purpose. Some people do CLA's for that purpose, but sometimes it really is about having a paper trail that the software is open source, or to make it easier to sue people who violate the license.
I mentioned this in the article, as it's pretty ironic.

Apparently Fi doesn't warrant a dedicated carrier bundle, meaning Fi subscribers will need to wait until the generic T-Mobile MVNO setting gets flipped on. I've read (on Reddit) that Apple does this because Fi doesn't sell iPhones, but I obviously don't know if that's true. Afaik it took Apple 2 years and a half to enable 5G on Fi, which makes me believe it's indeed Apple being petty, and not some conspiracy theory.
> you can not eat the skin

But the skin is the best part! Seems lika a stupid cooking method.
I don't mean to belittle your app that unfortunately I can't try it since I don't have iOS.

We did solve the problem in a much easier way though. We do have 40 recipes we usually cycle through. I wrote them in a spreadsheet and marked them based on who can cook them, if it's brunch, lunch or dinner, quick or elaborate, summery or wintery.

Then in another sheet I just create a list of those recipes/dishes picked randomly based on the day of the month.

If we start the discussion "what do we eat tonight", I can just open the spreadsheet. 99% of the time proposing the option for that day on the sheet gives us closure and we're done.
I wrote a lot of code for lotus notes circa 1995 for an early web app. It was still code (lotus notes script), just that I had to figure out how to do things without loops and recursion.
Yep, to make RCS business messaging useful, you'll have to use a middle-man like Twilio. They take care to sign contracts with individual RCS carriers. And some carriers might refuse interconnections entirely (as a result, Twilio supports only a subset of countries).

And of course, this is not cheap. Carriers don't have any market pressure to compete on the RCS interconnection price. So you'll be paying not-insignificant per-message fees over the IP infrastructure.
What if there are multiple processes that require access to a shared cache?
I've wondered about just being able to pass an error closure to a function. And if you don't it'll execute a default error closure.

void oops(error_t error) { exit(1)};

int sum = addints(a, b, .error = oops);
We did a similar thing. Started all in on Heroku and then slowly moved database, redis, MQ and CICD off to dedicated providers over a 4 year period. Then we spent several months creating an architecture in a different cloud provider that we felt would be our next step in evolution and finally migrated our servers off Heroku.

I'm still a fan of Heroku and would highly recommend it to a brand new startup. But, after awhile, you start realizing the limitations of Heroku and you need to move on. The fact that your startup is still around and growing enough that you need to migrate off Heroku should be seen as a sign of success
https://redis.io/docs/latest/commands/
Not really embedded, but one of the easier classes of wins I've had over the years is moving prod servers to a non-systemd Gentoo. Random (rare) 200ms latency spikes and whatnot just disappear, and the system jitter drops down to the tens of microseconds range, significantly improving the qualitative performance of basically every piece of software I care about.
The misery of RCS ultimately was rooted in money, not technology. Carriers wanted a way to monetize messaging services on LTE like they did in the 1990s with SMS. They thought that inventing a new standard, ostensibly built around SIP (ie more integrated into the telco session layer than SMS, which was a bit kludgier), would be the path.

What they failed to realize what that LTE brought easy access to data, and in particular OTT messaging like WhatsApp. Consumers, remembering only too well the horror stories of being gouged by telcos for heavy SMS messaging, were not inclined to trust the carriers. So WhatsApp etc. took off while RCS stagnated.

On the technical side, vendors soon discovered that every telco wanted to do RCS slightly differently, and that implementing RCS in an IMS network was not as easy as slapping in an app server. So when Jibe showed up, a lot of the air left the room. Problem was, the telco people saw precisely what Google were doing: taking away a potential revenue stream from their control and monetization. So again, things languished.

The technical people I worked with at mobile operators across this time were very sharp people who could make most anything work. But the leadership was so terrified of losing money, and so bad at making money, that many good plans never saw the light of day.
Perhaps if one coupled this with a multimodal LLM we could achieve a singularity
Maybe companies / product designers started listening to what customers actually wanted.
Please expand on this.

You're saying the analog functionality behind a button, like an analog volume control is no longer a pontiometer, but rather a tactile UI element?
I think the scope of lazy constructs should usually be far less than that of strict constructs, so it's only in the cases where the librarified lazy abstractions don't fit that you need a rewrite. Lazy to strict isn't hard, but I don't want the performance and cognitive overhead of lazy-by-default.
While many years ago the AMA did lobby to limit the supply of doctors they reversed their position and are now lobbying for an increase.

https://savegme.org/

Since demand for healthcare is growing rapidly I expect that doctors will still be well paid even if the AMA succeeds in getting Congress to add more residency program funding, and thereby increase the supply.
They're already laying the groundwork for a rug pull.

The fact that the developers will happy let you hide any button in the UI except the sign in button is a giant red flag.

https://github.com/zed-industries/zed/pull/11802
My wife does the same kind of thing, except she wrote a whole web app that I host on my homelab server (we're both rails devs). The app keeps track of upcoming meals on a calendar, number of leftover servings in the freezer, ingredients needed for upcoming meals, etc.
Genuinely unsure how this is relevant in any way.
Macros, Safety, and SOA
Beer can math – recycling vs. reducing consumption
I'm really looking forward to taking this for a spin. Thanks for sharing.

Question: Can this handle network disconnection/instability mid copy?
A $1M teacher scheme left uncertified teachers in Texas
Yeah I think there is a lot of potential here.

Especially in city building games etc.
That compensation is better isn't in dispute. My question is about worker rights, how much of the stuff you posted is just your company vs US law? Are you protected better by law than someone here would be?
And X is owned by a Trump propagandist.
org-babel-eval-in-repl
Why AI Can't Exist Without Taiwan [video]
After the accident, the Massachusetts legislature passed a law to require a licensed professional engineers stamp on all gas infrastructure designs of this type
> You don't need a set, map, heap, stack, array, hash etc database.

On the contrary, redis is super popular, and that is basically what it is.

> More concretely I'm pretty sure you could demonstrate using relational algebra that any graph can be formed pretty trivially using relations. So I think there is probably provably no use case that can't be done with a more traditional RDBMS.

The question would be more about efficiency & ease of use than if you could literally just store a graph in a rdbms
Hypervelocity Tether Rockets (2022)
Ask HN: Why Doesn't ChatGPT Have the Memory Feature Enabled for O1 Models?
Anyone know why ChatGPT’s memory feature isn’t active in the O1-preview and mini versions? I’ve been tinkering with them, but they seem to forget earlier parts of the conversation. Is this intentional, a bug, or something else? If anyone’s got the lowdown, spill the beans!
Between how fast X has been losing money, and its reluctance to pay amounts owed to its [attorneys|employees|landlords|etc.] - I'd be concerned about X actually allowing customers to withdraw the funds they'd deposited.
In regards to dealing with windows fogging, I prefer the system in my car that automatically detects conditions where it might fog and adjusts itself accordingly. On top of that the car has a physical max defog button close to the actual driver controls.
It would be worse than nothing. Allowing Russia to come away from the current conflict with freshly-annexed territory just emboldens Putin to invade again later, much like taking Crimea in 2014 ultimately led to today. If he can't take all of Ukraine now, he'll settle for invading again later once he's regrouped and rebuilt.
If you took every penny from all the billionaires in the USA it would fund the US government for 8 months.

The threat is the Government.
When you require that your "algebraic" types always be tagged, so that `type X = A + B` and `type Y = A + B` are always different, you lose most of your capacity of seamlessly composing the types.

In other words, Rust doesn't have a type that means "either IO Error or Network Error", so it can't just compose those two behind the scenes into something that you can later decompose. You have to create some tag, and tell the compiler how to apply the tag, because each tag is different.
Is it already possible to join rooms without revealing your global address like in XMPP?
Easy enough to replace icons just doing a get info and a copy/paste, but will this app handle auto-replacing the icon again after an app update? Example: I dislike the stock VSCode icon, so I found another icon that I like better and replaced it. Easy peasy. However, every time there is an app update, that icon gets wiped out. If this app solves that, I’d gladly pay for it.
However it was added to the 1999 revision of the SQL standard, so its been there for 25 years.
New survey puts human face on pollution caused by U.S. wood pellet mills