MurphyA/hacker-news huggingface dataset:
by mjevans | 2025-06-01 06:48:37+00:00
Due to the tilt of the earth the length of a solar day is not constant (unless you're very near the equator along a specific, probably wobbly, line).

Even now, obtaining solar noon is comparatively easy. Then add half of an earth's rotation* (slightly affected by the earth's orbital period too), and that's midnight.

In the days of candle light, midnight wasn't a crazy time to draw that diving line. However these days even people with crazy early AM weekdays to avoid commutes sometimes cross over midnights on the weekend.

+

You are correct that the modern world really should just start counting the day at like 3 or 4 am, and continue counting past 2359 to almost 2700 or 2800.
by socalgal2 | 2025-06-01 06:50:36+00:00
It does not solve the same problem. The same way the majority of people prefer to wash their hand at a faucet with soap and water. They might put up with a wet wipe when they are near a faucet but it doesn't "solve the same problem". At best it's a temporary solution until you get to a place where you can really wash.
by userbinator | 2025-06-01 06:50:53+00:00
but the number of students failing exams increased dramatically because fewer people did the homework.

In a sane world that would be a "not our problem", as the horses have been brought to water and they just won't drink, but unfortunately institutions chasing pass rates metrics as a pure indicator of instructor skills pushes towards increased leniency in grading and that's another can of worms which I won't open here.
by motorest | 2025-06-01 06:51:21+00:00
Can you offer some detail into why you find this approach useful?

From an outsider's perspective, if you're sending around JSON documents so big that it takes so long to parse them to the point reordering the content has any measurable impact on performance, this sounds an awful lot like you are batching too much data when you should be progressively fetching child resources in separate requests, or even implementing some sort of pagination.
by austinallegro | 2025-06-01 06:51:22+00:00
(My lovely, lovely, lovely horse)

My lovely horse (My lovely horse) Running through the field (Running through the field) Where are you going, with your fetlocks blowing in the wind? (All Summer)

I want to shower you with sugar lumps And ride you over fences Polish your hooves every single day And bring you to the horse dentist

(My lovely, lovely, lovely horse)

My lovely horse, (My lovely horse) You're a pony no more (You're a pony no more) Running around with a man on your back Like a train in the night... like a train in the night (I Love You Anyway) My lovely, lovely, lovely horse
by pjmlp | 2025-06-01 06:51:43+00:00
I love bold statements, and if you mention either LLVM or Chrome, it isn't as if the Google's C++ style guide is any piece of art.

Which anyone that bothers to make such claims, should be aware what it actually says regarding exceptions.

"On their face, the benefits of using exceptions outweigh the costs, especially in new projects. However, for existing code, the introduction of exceptions has implications on all dependent code. If exceptions can be propagated beyond a new project, it also becomes problematic to integrate the new project into existing exception-free code. Because most existing C++ code at Google is not prepared to deal with exceptions, it is comparatively difficult to adopt new code that generates exceptions."

They don't use exceptions, because already started on the wrong foot, and like legacy code of Titanic size there is no turning around now.

What does the Bible of idiomatic C++ says, aka C++ Core Guidelines?

It has several advices on E section, regarding exception coding best practices.
by maxbond | 2025-06-01 06:52:19+00:00
Yep, you have to be explicit when coordinating across timezones. I never say "how about 11" in that context, I say "how about 11ET." If you want to do that by using UTC as a lingua franca and everyone does their own conversion, that makes a lot of sense. If you want to abolish timezones, that's just brushing the problem under the rug.

People keeping different hours in different locales is inherent complexity. This is the crux of it. If you want to abolish timezones, you need to explain why it isn't a problem that people keep different hours in different locales. If you can't, then it boils down to timezones being annoying. They are annoying, but that's not sufficient reason to eliminate them.
by wkat4242 | 2025-06-01 06:52:28+00:00
Uhm what am I not getting? This has always been possible.

Edit: I think what's new is the UI to add the new engine by typing the URL by hand. Previously engines needed to support OpenSearch to auto-add them (but you could easily add custom ones this way). However pretty much all of them do (it's no trouble, just some XHTML in the page). I don't know why you would do it by hand.
by reconnecting | 2025-06-01 06:55:41+00:00
> While our platform is primarily designed for live, logged-in users, it also works well for bot detection and blocking.

tirreno is designed to work with logged-in users, so all actions are tied to usernames rather than IP addresses. From this perspective, we strongly avoid [1] making any decisions or taking actions based solely on IP address information.

[1] https://www.tirreno.com/bat/?post=2025-05-25
by socalgal2 | 2025-06-01 06:56:05+00:00
> squatting pose being a lot healthier than the standard sitting on a Western toilet

I'm not convinced though maybe I was just never properly trained. When I use a squat toilet I have my pants bunched up, when I squat the bunched up pants are between my upper and lower legs and cut off the ciruculation in my legs. If I'm constipated it my legs are screaming much sooner than on a seat.
by motorest | 2025-06-01 06:56:55+00:00
> If you're optimizing for time to first render, or time to visually complete, then you need to render the page using as little logic as possible - sending an empty skeleton that then gets hydrated with user data over APIs is fastest for a user's perception of loading speed.

I think that OP's point is that these optimization strategies are completely missing the elephant in the room. Meaning, sending multi-MB payloads creates the problem, and shaving a few ms here and there with more complexity while not looking at the performance impact of having to handle multi-MB payloads doesn't seem to be an effective way to tackle the problem.
by umanwizard | 2025-06-01 06:58:34+00:00
We would invent them for the same reason they were invented for the first time.

I don't really care what time it is in England; I care about the local solar time where I live. I live in Tucson; the local solar time at my house is about 7.4 hours before UTC. I and the people who live near me would quickly start informally referring to times based on the position of the sun: "let's get lunch tomorrow an hour after solar midday".

(Aside: this isn't just hypothetical. It has happened in the real world. In the far west of China, people have settled on a different time zone for colloquial everyday use, which differs from the Beijing-imposed official standard time by two hours.)

So far so good, but someone on the far east end of Tucson is more than a minute later than me; if we want to be precise, we'll need one standard for the whole city, so maybe they'd build a big sundial at the University of Arizona and that would serve as the reference for the whole city.

But people drive around Arizona a fair amount; it'd be annoying to have to adjust my model of time by five minutes every time I go to Phoenix, and I wouldn't mind the few minutes of slop applied to my own life in Tucson, so I'd probably just start referring to everything in terms of offset from "Phoenix midday" and "Phoenix midnight" to make things easier. And if we're going that far, we might as well make it an even bigger area: big enough to include the whole Southwest, but small enough that the difference from local time doesn't bother anyone. Let's say we base it on Denver.

Bam, we just reinvented Mountain Standard Time.

Well, almost. Meanwhile, people on the East Coast would have (almost) reinvented Eastern Standard Time, presumably based on their most important city, which is New York. New York is about 1h55 ahead of Denver in solar time. Dealing with these almost-but-not-quite hour offsets would be annoying, so we'd probably just standardize on one system for the whole country, with nice, even, easy to reckon hour-multiple offsets for everyone.

Canada and Mexico, whose economies are highly dependent on trade with the US, would soon standardize on the US-imposed time zones. Even if doing so might hurt their patriotic sense of national pride, the practical value would be too great. But what about the rest of the world? Well, our historical closest friend and ally in a far-off longitude is the UK, so why not sync up with them and make all those easy to reckon hour-multiple offsets from their most important city, London, or more precisely, the point they've chosen for London's standard time: the Royal Observatory in Greenwich.

Now we really have reinvented Mountain Standard Time, exactly as it exists in the real world.

Why wouldn't we go further and just use Greenwich time for everything? Well, because we still do care about local solar time. The difference from my house's solar time to the newly invented MST is less than an hour, which I can live with, but dealing with a 7-hour difference would be annoying.
by jazzyjackson | 2025-06-01 06:58:48+00:00
Some chatbots plan a query and summarize what a search returns instead of trying to produce an answer on their own; I use perplexity a lot which always performs a search, I think ChatGPT et al have some kind of classifier to decide if web search is necessary. I especially use it when I want a suggestion without sifting through pages of top ten affiliate listicles (why is there a list of top 10 microwaves? I only need one microwave!)
by Arisaka1 | 2025-06-01 06:59:59+00:00
As someone who has been dealing with flared hemorrhoids since I was a teenager, I improvised my post-2 work by simply washing with the shower pistol whose cord is long enough to reach behind me while I'm sitting on the toilet.

Since then, whenever I search for a new apartment to rent, this became one of the criteria I look for! I simply can't go back to just dry wiping, ever.
by adrian_b | 2025-06-01 07:01:12+00:00
If you cannot predict the running time of an algorithm without running it on the target processor, then by definition the documentation of that processor is incomplete.

For a processor that is completely documented one must be able to run a simulation model that provides the running time for a given program, when the processor is so complex that simpler methods for computing the execution time do not work.

For older NVIDIA GPUs, there exist such simulation models, but they are only partially accurate, because they are based on reverse engineering, without cooperation from the GPU vendor.
by flomo | 2025-06-01 07:02:00+00:00
Itsamystery what Apple was thinking, but I suspect almost zero external customers actually bought an ANS. Apple probably used it internally (dogfood), and maybe some external partners got one.

Sorta like CHRP "Windows NT on PPC", it was printed on the CD-ROM, but the machines were never actually sold to the public.

Also edit to clarify: OP is about porting Doom to an old UNIX, not the usual small computer. The ANS was a big computer. (OP says IBM ported Quake.)
by pjmlp | 2025-06-01 07:02:17+00:00
Legacy code writen as if it was C with a C++ compiler, or that predates the C++98 standard (during the 1980-90's, where C++ARM was the only guidance), the Orthodox C++ folks, claiming that they are too slow or bloated (most of the time based on hearsay and not profiled), on embedded computers better than everything I owned since 1980's until 2000's, put together.

The same folks won't have a second thought distributing statically linked binaries that triple the size, while using languages that don't do exceptions, but then it isn't bloat, talk about being coherent.
by wkat4242 | 2025-06-01 07:04:34+00:00
Huh no? I've just added it in settings. No custom extension needed. I'm pretty extension-averse because I already need so many :) Ublock, Sponsorblock, Dark Reader, password manager, consent-o-matic, sideberry I really can't do without.

But I've always been able to do it. All I had to do was to simply visit my SearXNG instance once, then it would pick it up and put it in the list of search engines (OpenSearch API) and then I could just set it as default.

One thing I could not do was edit search engines (e.g. the URL they visit). I still can't do that in fact but maybe that's new?
by wildpeaks | 2025-06-01 07:04:36+00:00
All you need is a bookmark, no extension needed: the "keyword" value is how it's called and "%s" in the url is the placeholder for the query.

For example, create a bookmark with keyword "youtube" and url "https://www.youtube.com/results?search_query=%s".

Then whenever you type "youtube something" in the address bar, it shows you the results directly.

The %s trick existed for so long, it even worked back in Internet Explorer.
by wkat4242 | 2025-06-01 07:06:43+00:00
Edit: Actually, I don't have browser.urlbar.update2.engineAliasRefresh configured at all (neither true nor false, just not configured).

But for me I've always been able to do it. All I had to do was to simply visit my SearXNG instance once, then it would pick it up (OpenSearch API) and then I could just set it as default.

In fact I remember setting up my new tablet a few months ago, and I didn't need to mess with about:config at all, it worked like I mentioned above. On firefox mobile they make it super hard editing about:config for some reason so I'm sure I didn't do that.
by motorest | 2025-06-01 07:07:01+00:00
> There's nothing wrong with "accidentally-overengineering" in the sense of having off-the-shelf options that are actually nice.

Your comment focuses on desired outcomes (i.e., "nice" things), but fails to acknowledge the reality of tradeoffs. Over engineering a solution always creates problems. Systems become harder to reason with, harder to maintain, harder to troubleshoot. For example, in JSON arrays are ordered lists. If you onboard an overengineered tool that arbitrarily reorders elements in a JSON array, things can break in non-trivial ways. And they often do.
by baobun | 2025-06-01 07:07:43+00:00
I guess it's a regression fix (perhaps Windows-specific) where it used to work and broke at some recent version? Because the feature as described is indeed nothing new in Firefox.

From the linked bug:

> Firefox now supports adding your own custom search engines. Just right-click a search field of a supported website and select Add Search Engine, or go to Settings > Search > Add (below the search shortcuts table) to manually enter a search URL.

https://support.mozilla.org/en-US/kb/add-or-remove-search-en...

Mozilla documentation of the feature (updated 2024): https://support.mozilla.org/en-US/kb/add-or-remove-search-en...
by adrian_b | 2025-06-01 07:08:35+00:00
While you are right that in general it may be very difficult or quasi-impossible to generate optimal programs, there are also plenty of cases where an optimal program is achievable.

The latter happens when there is one dominant bottleneck for the algorithm, which is determined by the hardware, e.g. the maximum throughput of a certain instruction, like multiplication or memory load. When the implemented program reaches a throughput almost equal with that absolute limit, then one can be certain of its optimality.
by roenxi | 2025-06-01 07:10:19+00:00
It might be more proper to deduce that community vetos are a bad idea although the practicalities of that are complex. I can imagine a situation, for example, where a community bans running a business from a residence and accidentally wiped out a major tech company from being founded. In fact, I suspect that probably did happen in the 90s although for obvious reasons it is impossible to prove.

We've seen a huge amount of economic success from allowing talented motivated people to do what they think is a good idea without developing a consensus on the proper course of action. That probably scales down into to the small too. Progress depends on letting outliers happen.
by motorest | 2025-06-01 07:10:36+00:00
> Progressive loading is easy, but figuring out which items to progressively load and in which order without asking the developer/user to do much extra config is hard.

Do developers even control the order in which stuff is loaded? Tha depends on factors beyond a developer's control, such as the user's network speed, the origin server's response speed, which resources are already cached, how much data each request fetches for user A or user B, etc.
by js8 | 2025-06-01 07:11:10+00:00
Somewhat agree, but it depends. I agree that core of the operating system (kernel) should be responsive, but there are many tasks in the operating system that don't require immediate response and can be run in batch. Usually these are higher-level decisions, such as any housekeeping tasks like file backup and indexing, workload reprioritization and optimization, system update and reconfiguration, and the like.
by jorvi | 2025-06-01 07:12:44+00:00
Haha, don't get me wrong, I am not asking for official days to be anything but 24 hours.

I guess I am arguing that "morning" "midday" "evening" and "night" should hold no official definition, since they are much more about the vibe rather than an absolute position on the clock. However, if they do remain as official definitions, they should be heavily revised.
by arcanemachiner | 2025-06-01 07:13:16+00:00
I ended up just converting to a method where instead of running the pomodoro on a timer, I run a stopwatch instead.

Then concept is still the same, in terms of focusing on the topic at hand. I no longer count down to my breaks, I just count up until I want/need to take a break.

It's basically just a glorified time tracker, I guess, but it was my solution to the pomodoro "break" problem, i.e. sometimes I don't want to take a break.
by scbrg | 2025-06-01 07:15:25+00:00
I believe all these problems are caused by time zones, not solved by them. If the current date/day of week wasn't vaguely connected to sleep/wake cycle, we wouldn't be conditioned to assume it was.

For instance, we handle 24 hour clock (with 60 minute hours?! WTF?) fine, even if it's insane and we use the decimal system elsewhere. Because we got used to it when we grew up. Many even have the clock reset in the middle of the day, ending up with things like two hour activities spanning from eleven to one! (Don't get me started on shit like "half four" - it means different things depending on where you are, but it never means two!)

Heck, there's a whole, huge country that gets by on inches and ounces and pounds and miles and whatnot - a mind boggling amount of extra mental energy required, and with the exception of some recent lapse when selecting their boss dude they seem to be doing mostly as well as (and over the previous century arguably somewhat better than) the rest of us in the thinking department.

If we grew up with date/day changing in the afternoon, every kid in preschool would have it figured out already. "Early morning flight confusion" would seize to exist (except, perhaps, for the poor bastards who'd happen to live close to wherever we decided to place the prime meridian), because everybody would know what "1:20" meant, and not randomly guess at something based on when they happen to sleep.
by motorest | 2025-06-01 07:17:13+00:00
> So you have two prompts, one is ambiguous and the second is the same prompt but with the ambiguity resolved.

No. You have an initial prompt that is vague, and then you have another prompt that is more specific.

- "draw me an automobile"

- "here's a picture of an ambulance."

- "could you make it a convertible instead? Perhaps green."

- "ok, here's a picture of a jaguar e-type".
by thayne | 2025-06-01 07:18:22+00:00
It looks like it addresses some of go, including:

- a better type system, that includes union types, and makes types non-nullable by default

- pattern matching

- designed with generics from the beginning

- try/catch error handling. This is controversial, and some people like checking every return value for errors, but it is a common complaint about go

- it looks like it is meant to have better c interop than go
by adrian_b | 2025-06-01 07:19:21+00:00
I have also used only UTC for any time display in any of my devices, clocks, computers, mobile phones, but for much more time, for at least 20 years.

I find it easier to keep in mind the current time zone offset and add it mentally to the displayed value when that is necessary (i.e. for comparison with time values coming from external sources, e.g. event schedules), regardless if it is summer or winter or I am in a business trip in another time zone, than to change the displayed value to reflect the correct local time when needed, and then to account for that.
Show HN: I Made Notorium – AI Notes and Mind Maps from Live Lectures
by pranav_harshan | 2025-06-01 07:19:41+00:00
Hi HN,

University lectures are long, dense, and fast-paced. Like many students, I used to record them thinking I’d revisit them later — but that never really worked. Even transcripts felt like raw logs.

So I built [Notorium](https://www.notorium.app) — an AI assistant that records live lectures and automatically turns them into structured notes, flowcharts, and mind maps— within minutes after class.

What it does: - Record lectures inside the app (in-person, live) - Transcribe using Whisper - Send the full transcript to LLM - Use a custom system prompt to: - Summarize the lecture - Break it into topics - Generate visual aids: flowcharts and mind maps

Extras: - Download notes as clean PDFs - Tap Simplify to make notes more digestible - Tap Expand to deepen explanations - Tag notes by subject (e.g., Physics, CS) for filtering and fast retrieval

Built for - In-person learners - Visual learners (flowcharts, concept trees, diagrams) - Students who want control — skim when you're tired, expand when you're focused

Coming soon: A spaced-repetition-based flashcard mode — so you can actively review and retain the key points from your lectures.

Tech Stack: - Transcription: Whisper - LLM: Open source model via Groq - Frontend: Next.js + Tailwind + shadcn/ui - Backend: Firebase

Why Groq?: Speed and consistency. Fast enough to generate full notes right after class ends.

Would love your feedback: - What other visual formats or study modes would help?

Thanks! – Pranav
by krior | 2025-06-01 07:19:51+00:00
As a celsius-user: you dont need more precision to judge how a temperature feels. The ranges you mention for Farenheit exist for Celsius as well. And if you need more precision you can use fractional numbers but I have rarely seen more precision in household thermometers than just rounding to 0.5 or the next whole number. I assure you that it is a completely usable scale.
by mattlondon | 2025-06-01 07:25:27+00:00
Same here but for urban foxes.

We had motion triggered sprinklers that worked great, but they did not differentiate between foxes and 4 year old children if I forgot to turn them off haha.

We have more or less 360 degrees CCTV coverage of the garden via 7 or 8 CCTV cameras so rough plan is to have basic motion pixel detection to detect frames with something happening then fire those frames off for inference (rather than trying to stream all video feeds through the algorithm 24/7) and turn the sprinklers on. Hope to get to about 500ms end-to-end latency from detection to sprinklers/tap activated to cement the "causality" of stepping into the garden and then ~immediately getting soaked and scared in the foxes brains. Most latency will be for the water to physically move and make the sprinklers start, but that is another issue really.

Probably will use a RPi 5 + AI Hat as the main local inference provider, and ZigBee controlled valve solenoid on the hose tap.