MurphyA/hacker-news huggingface dataset:
by kurthr | 2025-06-06 17:02:58+00:00
Actually, no. Anyone can be "creeped the Fuck out" about anything anywhere. It's their right. That's "just like uh, your opinion, man". One can be annoyed by business processes, vaguely offended by decor, or the stiffness of the uniforms at Dachau, and it's kind of irrelevant.

I'll try to be more clear. This reads like reality TV drama when there are bigger things going on. It misses the dark forest for the brown weeds.

To me the bigger point really IS the corporate dehumanization, but the details (other than the white gringos laughing about layoffs) distract from the deeper issues and sound more like gripes of a coddled coder than real criticism. When an individual is more concerned with their own personal jokes/disses than the work they're doing, you get folks at Enron joking about turning off "GrandMa Millie's" electricity in profitable, but unnecessary rolling blackouts.

They actually sold out.
by hombre_fatal | 2025-06-06 17:03:10+00:00
You know how it's always been a meme that you'd be mortally embarrassed if your browser history ever leaked?

Imagine how much worse it is for your LLM chat history to leak.

It's even worse than your private comms with humans because it's a raw look at how you are when you think you're alone, untempered by social expectations.
by southernplaces7 | 2025-06-06 17:03:35+00:00
In this case Musk should be careful if he cares about keeping what he has. It's Trump who, pun intended, holds all the trump cards. Musk can threaten some random expo of bad stuff about Trump but the president has been getting sprayed for years with his own shitty past activities and has pretty much built an entire persona of armour that lets them slide off like water from a duck's back. Trump's core of supporters loves him enough to not give a shit whatever new dirt they hear anyhow, while just about nobody, even among republican types, likes a socially unpleasant techbro on steroids like Musk.

Legally too, Trump can absolutely hammer even someone as rich as Musk with all kinds of tools through his FCC, FTC, AG's office and Justice Department. Musk can... tweet about how angry he is and share a document or two. Hardly a good balance of competing powers. There are the vital SpaceX tech contracts working in Musk's favor, but they're not an insurmountable problem for the notably reckless Trump admin.
by boris | 2025-06-06 17:03:56+00:00
I watched that but I don't see it as convincing. Let's take the AWS example brought up in the talk. The "compete on the interface, not (open source) implementation" idea I think misses (at least) the following points:

1. AWS will take your initial and ongoing investment in the implementation but they don't have to share theirs with you. Specifically, they will take your improvements but their own improvements (say some performance optimizations) they can keep to themselves. It's good business sense if it allows them to further differentiate their "improved" offering from your "vanilla" service.

2. Competing on the the interface in this case really means competing on related services like management, etc. So your thesis is that you will provide a better/cheaper managed service than AWS. Even if that's true (a big if), most of the time the decision which service to use will have little to do with technical merit. I.e. we already use AWS, have SLA painfully negotiated, get volume discounts, etc. Do we really want to go through all of this with another vendor just for one extra service.

Just a couple of thoughts that will hopefully help you sharpen your thesis.
by WorldMaker | 2025-06-06 17:03:57+00:00
My understanding, and it may be wrong, is you may be grandfathered in to an ancient Personal, Public Repo opt-out from a brief window of time just after GitHub was excited to announce the first/earliest version of Dependabot and was hoping it would clean up some Open Source supply chain attacks and just before GitHub realized Dependabot was a useful thing to charge people an upcharge on (now under the umbrella known as GitHub Advanced Security). I believe that GitHub auto-opted in a lot of personal accounts with "significant" Public repos (anything with a bunch of forks/stars, or a package identifier visible in the dependency graphs of the Ruby or npm ecosystems, or any of the things that awarded "badges" like Mars Rover badge or the Artic Vault badge). There's a page buried in your Personal Account Settings to turn off that ancient Dependabot option. (I'm on a work machine without access to my personal account at the moment or I'd directly tell you where to find it.)
by jihadjihad | 2025-06-06 17:04:05+00:00
Rule of 72: time for an investment to double is roughly 72 / the interest rate [0].

Annual return on small-cap stocks: ~12% Time to double: 72/12 ~= 6 years Number of doubling periods: 99/6 ~= 16 Final investment value: ~2**16 ~= $65k ~= $64,417

Math checks out.

0: https://en.wikipedia.org/wiki/Rule_of_72
by PeterWhittaker | 2025-06-06 17:04:39+00:00
I opted for a single history across all sessions on any given host: On my main machine, the first of 54,434 entries is timestamped 2020-08-22:12:39, while on the machine on which I do most development at the moment (it varies from product to product and release to release), the first of 34,771 entries is timestamped 2023-05-08:11:34.

For the curious, the salient .bashrc bits are:

function _setAndReloadHistory { builtin history -a builtin history -c builtin history -r } # preserve shell history set -o history # preserve multiline commands... shopt -s cmdhist # preserve multiline command as literally as possible shopt -s lithist # reedit failed history substitutions shopt -s histreedit # enforce careful mode... we'll see how this goes shopt -s histverify # timestamp all history entries HISTTIMEFORMAT='%Y-%m-%d:%H:%M ' # not the default, we like to be explicit that we are not using defaults HISTFILE=~/.bash_eternal_history # preserve all history, forever HISTSIZE=-1 # preserve all history, forever, on disk HISTFILESIZE=-1 # record only one instance of a command repeated after itself HISTCONTROL=ignoredups # preserve history across/between shell sessions... # ...when the shell exits... shopt -s histappend # ...and after every command... PROMPT_COMMAND="${PROMPT_COMMAND:+$PROMPT_COMMAND; } _setAndReloadHistory"

EDIT: Remembered just after submitting that since I am on MacOS, I ran the command

touch ~/.bash_sessions_disable

back on August 22nd, 2020, to prevent Terminal from saving per-session information. I've never cleaned out ~/.bash_sessions, suppose I should, but it hasn't been updated since that day.
by bityard | 2025-06-06 17:04:48+00:00
I said it was debatable, but you may be right. I still think if we hadn't already put a human on the moon by today and had a 10-year deadline to do it, it would basically not happen because it would get killed by bikeshedding, or red-vs-blue politics, or it would get highjacked by aerospace contractors and the funds milked dry with nothing to show for it.
by belden | 2025-06-06 17:05:10+00:00
I fall into the hoard-and-curate camp.

I use bash within tmux heavily, and got irked that a command I run in one shell session is not immediately available as a history item in other concurrent shell sessions. So I wrote a history plugin based on bash-preexec to track everything to two files: a per-directory history file, and a global history file.

I have a bash function which does history selection for me, by popping an fzf selector to look at the directory-specific history file. A keybinding within fzf allows me to switch to looking at the global history file instead.

Boring commands such as “cd”, “pushd”, and a few others don’t get logged. The log entries are in json format and include basic metadata; directory, timestamp, and pid.

Within the fzf history picker, another keybinding allows me to edit whichever file I’m actively using. So if I fumble a few times to construct a command, then when I get it right I just pop into the selector, edit the relevant file, and remove the lines I don’t want to misfire on again.

I’m sure this is basically what atuin does; now that I’m at the spot where directories are the unit of history relevant history, maybe I should give that tool another look.

One really interesting upside of all of this is that I now tend to make “activity-specific” directories in my repos. For example, I have a “.deploy” directory at the git root of most of my projects. There are no files within that directory; but my tool creates ~/.bash.d/history/home/belden/github/company/project/.deploy.json which contains the history of ~/github/company/project/.deploy/

Empty directories are invisible to git, but for me the directory “has” content: the log of how I need to deploy this service or that service.

It’s a weird way to use my shell, and just sprung out of the initial grief: I shouldn’t have to exit a shell session to have its history become available.
by GuB-42 | 2025-06-06 17:05:13+00:00
Overnight trains are awesome. Yes, they move slowly compared to planes, but you may actually waste less time using them, think of them as moving hotels. You don't travel to the hotel, the hotel travels for you!

The idea is that you get to the station in the evening, board the train, then on the train, you eat, relax or do some work depending on how busy you are, take a shower, and sleep and in the morning, you are at your destination. Train stations are usually closer to downtown than airports and you spend less time with security, check-in, etc... another advantage. If you account for the hotel stay you saved, net travel time can be effectively zero.

And that's just the "transportation" aspect. In addition, train cruises are a thing. Not as big as cruise ships, but that's the same idea.

If I had first-class air travel money, which is probably their target demographic, I would definitely ride such a train.
by BitwiseFool | 2025-06-06 17:05:37+00:00
MIPS was a genuine attempt at creating a new commercially viable architecture. Some of the design goals of MIPS made it conducive towards teaching, namely its relative simplicity and lack of legacy cruft. It was never intended to be an academic only ISA. Although I'm certain the owners hoped that learning MIPS in college would lead to wider industry adoption. That did not happen.

Interestingly, I recently completed a masters-level computer architecture course and we used MIPS. However, starting next semester the class will use RISC-V instead.
by sachnk99 | 2025-06-06 17:05:48+00:00
Hi -- Sachin here, one of the founders of Clear Street. To clarify:

- The investment in TigerBeetle was done personally, not through Clear Street.

- I'm no longer actively involved day-to-day as CTO at Clear Street, but while I was, TigerBeetle was a solution we very much had in mind as our volumes were increasing.

That said, roadmaps change, priorities shift, etc. If TigerBeetle existed when we started Clear Street, I very much would have used it, and saved me from many headaches.
by rbanffy | 2025-06-06 17:05:59+00:00
> The Adam came with a dot matrix printer.

It was a daisy wheel printer. No graphics, but "letter quality".

> Back then, using audio tapes to hold data was revolutionary, in terms of storage space and price.

Those aren't ordinary cassettes - while it is possible to make an Adam cassette out of a normal audio cassette, it's a somewhat involved process. There was hardware sold back then to do it, as the Adam itself couldn't.
by wpm | 2025-06-06 17:06:03+00:00
1. They don't exist. No, "Nokia Bell Labs" is not the same. Lucent is not the same.

2. Bell Telephone doesn't exist. No, AT&T is not the same.

3. Since Bell Telephone doesn't exist, the money faucet doesn't exist to pay for Bell Labs.

4. See 1.
by homebrewer | 2025-06-06 17:06:19+00:00
In some countries it has become difficult to live without a WhatsApp account. I'm doing it, but it's a pain since WhatsApp is used for everything that phone calls were once used for: schedule appointments, keep in contact with your kids' teachers, buy and sell goods, etc. The same numbers often won't pick up the call, or it will be simply turned off (since it's used just for WhatsApp).

Imagine living without a phone, or whatever is equally important in your area. Sure, it is possible, if you're at the right level of masochism.
by Al-Khwarizmi | 2025-06-06 17:07:24+00:00
In Spain, apart from the grant application, you have to write countless reports that take a lot of time, do endless bureaucracy to hire people or buy things, justify every expenditure. Probably you also need to hunt for a second simultaneous fellowship because typically they're too small to do meaningful research. And all this is on top of teaching, and endless evaluations where you need to submit various versions of your CV and supporting documentation (we often have 2-4 such evaluations a year). When all is said and done, time for actual research tends to zero. We live off PhD students who don't have to do all that.

The UK seems considerably better (much less bureaucracy and fewer hours of teaching) but still, you probably need to do reports and stuff on top of the grant applications.
by raja159 | 2025-06-06 17:07:26+00:00
EXCLUSIVE INVITE to the Medroid Founders' Club

I would really grateful if you could please try it out and give me your feedback. Help us shape the future of healthcare.

Join now: https://app.medroid.ai/join-founders

Meet Medroid, your new AI Doctor! (Currently in Private Beta)

Get instant evidence-based medical advice 24/7 with Medroid - powered by advanced medical AI that understands symptoms, suggests treatments, and provides evidence-based care guidance.

Get exclusive access to Medroid with: Founders Club badge & priority support Early access to advanced AI features $10 welcome bonus Private Slack access Direct access to our founders

Be among the first to have an AI Doctor in your pocket #AIDoctor #Health #HealthTech #Innovation
by Fnoord | 2025-06-06 17:08:17+00:00
I do not mind an occasional swear + excuse me, if genuine. We all make mistakes. In WoW, some people can rage, or an entire realm spams Anal [Achievement]. E.g. Anal [You're Doing It Wrong] or (and this one I find terribly inappropriate) Anal [For The Children]. Sure, I can see humor in such, too, but repeated endless and some combos are disgusting...
by quonn | 2025-06-06 17:08:18+00:00
> The person lamented the ongoing economic volatility — caused by tariffs and Trump’s unpredictability — during a presidency that they had been promised would be a boon to business. “We’re all experiencing a liquidity crunch,” they said. “We need public markets to open.”

"Promised", boohoo. These people really don't understand what a society is and are operating at the level of toddlers to put it mildly.

If they ever manage to destroy many jobs by building strong AI, we will hear "We're experiencing a lack of demand".
by amlib | 2025-06-06 17:08:32+00:00
Censorship by private parties is only a problem when they are allowed to be a monopoly in that market segment. If we had hundreds of viable and independent youtube sites and hundreds of viable and independent social networks around the world private censorship wouldn't be much of a problem at all, you just take your junk to whoever accepts it, be it from a jurisdiction point o view or from a policy point of view. If none of them accepts you, you likely need to spend a long time reflecting upon yourself... or try creating your own service (which has a much bigger chance of staying afloat on such fair market) that accepts your junk.
by ajross | 2025-06-06 17:08:42+00:00
Even weirder that this definition holds even here on HN, a site literally dedicated (originally) to Building Something People Want.

The whole demographic of the "tech" scene has shifted from products to finance, up and down the stack. And that's absolutely being reflected in the political cynicism we're seeing. Tech bros couldn't get what they wanted from a Democratic administration so they figured they'd just grease a few orange palms and get it from republicans.

What no one predicted, though, was the abject buffoonery of the whole process. Watching billionaire after billionaire get played, laughed at and discarded by a Trump administration that never cared a bit about any of the issues the VC set wants is just amazing. These are the people we're supposed to trust to guide us into the future?
Show HN: Lightweight Durable Workflows Built on Postgres
by qianli_cs | 2025-06-06 17:09:28+00:00
Hi HN! This is Qian here with Peter (KraftyOne) and Jeremy (jedberg). We’re building DBOS, an open-source, lightweight durable workflows library that you can add to Python apps in just a few lines of code. It’s comparable to popular open-source workflow and queue libraries like Airflow and Celery, but more lightweight with a greater focus on reliability and automatically recovering from failures.

Our goal in building DBOS is to make workflows lightweight and flexible so you can add them to your existing apps with minimal work. Everything you need to run durable workflows and queues is contained in this Python library. You don’t need to manage a separate workflow server: just install the library, connect it to a Postgres database (to store workflow/queue state) and you’re good to go.

DBOS workflows make your program durable by checkpointing its state in Postgres. If your program ever fails, when it restarts all your workflows will automatically resume from the last completed step. You add durable workflows to your existing program by annotating ordinary functions as workflows and steps:

from dbos import DBOS @DBOS.step() def step_one(): ... @DBOS.step() def step_two(): ... @DBOS.workflow() def workflow(): step_one() step_two()

The workflow is just an ordinary Python function. You can call it any way you like–from a FastAPI handler, in response to events, wherever you’d normally call a function.

We’ve just released DBOS Python 1.0. This enhances workflows with many powerful features we’ve been building over the last few months, including:

- Durable queues. Postgres-backed queues with all the queuing features of BullMQ/Celery (concurrency limits, rate limits, timeouts, priority, deduplication, etc.). Plus, they integrate with durable workflows, so you can write a workflow that enqueues 1K tasks, waits for and processes their results, and automatically recovers from any interruption.

- Programmatic workflow management. Your workflows are stored as rows in a Postgres table, so you have full programmatic control over them. Write scripts to query workflow executions, batch pause or resume workflows, or even restart failed workflows from a specific step. This makes it much easier to diagnose and recover from bugs and failures that affect thousands of workflows.

- Full support for both sync and async Python–write your workflows and steps as code either synchronously or asynchronously, it all works out of the box.

- Improved tooling, including dashboards, workflow graph visualization, workflow management via web UI, and more.

We’d love to hear your feedback and hope you can try DBOS out!
by quotemstr | 2025-06-06 17:09:30+00:00
> If you write a program that wants to have a million files open at once

A file descriptor is just the name of a kernel resource. Why shouldn't I be able to have a ton of inotify watches, sockets, dma_buf texture descriptors, or memfd file descriptors? Systems like DRM2 work around FD limits by using their own ID namespaces instead of file descriptors and make the system thereby uglier and more bug-prone. Some programs that regularly bump up against default FD limits are postgres, nginx, the docker daemon, watchman, and notoriously, JetBrains IDEs.

Why? Why do we live like this?
by pawellakomski | 2025-06-06 17:09:37+00:00
just released a small tool I’ve been working on called BitCache. It's designed to help backup and manage BitLocker recovery keys more easily. Here's the gist:

What it does:

Scans and backs up BitLocker recovery keys Entra ID

Saves them into a local database for easy access

Completely portable – no installation required

Open source (MIT license) – feel free to inspect, fork, or contribute

Why I built it: It may be used for storage and archiving but mainly it solves a problem I noticed - when a computer objects is remvoed from Entra ID, all BitLocker keys disappear. This may pose a problem if you need to unlock a volume on a computer that was in a storage for last 2 years.

Where to get it: pawellakomski/bitcache

Looking for testers & feedback: I'd love for others to try it out and let me know what you think. Whether it's feature requests, bugs, or thoughts on security/privacy – all feedback is appreciated.

You can also provide feedback to bitcacheteam@pm.me

Thanks for checking it out!
by epistasis | 2025-06-06 17:09:43+00:00
I definitely want to keep every single shell command I ever executed, including mistakes. And I want to track across machines, projects, etc.

Lately I have been using atuin for this. I have some gripes about interface defaults, and how the interactive search for history wipes out most of what was on my terminal view and causes a big "wtf was I doing again?" moment when it changes the terminal so much, but the tradeoff of shared history is very very much worth it for me.
by ndiddy | 2025-06-06 17:09:52+00:00
From looking at his Xorg contributions on FDo, his technical work amounts to mostly code style changes and cosmetic-level refactors in an attempt to clean up the codebase. In the course of this, he's broken the master branch on multiple occasions and introduced a large amount of churn in the Xorg ecosystem, all while not fixing any bugs or improving anything user-facing. The reason why he started this fork seems to be that his changes pissed off everyone working on Xorg who could review his MRs, so they started piling up without getting reviewed.

I think this comment from an Xorg maintainer sums things up (from this issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1797 ):

> Changing calls pScreen->DestroyPixmap to dixDestroyPixmap doesn't meaningfully improve the code or make it easier to reason about. Moving byte-swapping of requests and events from one function to another doesn't make the code more robust. Cosmetic changes to the way length fields are written doesn't help with byte vs. word unit confusion, or keep you from writing the wrong amount of data. You're just moving the complexity from point A to point G, not reducing it.

> It is possible to reduce the complexity of the code, by delving deep into the interactions between DIX/MI/FB/DDX to flatten the code flow, making some deep structural changes. Or by using structured (de)marshalling through XCB. Doing this would be incredibly risky, but at least have a much higher payoff than just cosmetic shuffling because it is 'cleaner'.

> The immense value X11 has - that it always had and will have for decades to come - is its backwards compatibility, still being able to run 40-year old apps. You correctly called the codebase 'fragile' - you've been finding this out as your changes repeatedly break things. If you're breaking apps, then what exactly is the value in a codebase which is 'cleaner' to your subjective standard but doesn't actually work?
by jcranmer | 2025-06-06 17:09:53+00:00
The reason why I say RISC-V is probably most influenced by MIPS is because RISC-V places a rather heavy emphasis on being a "pure" RISC design. (Also, RISC-V was designed by a university team, not industry!) Some of the core criticisms of the RISC-V ISA is on it carrying on some of these trends even when experience has suggested that doing otherwise would be better (e.g., RISC-V uses load-linked/store-conditional instead of compare-and-swap).

Given that the core motivation of RISC was to be a maximally performant design for architectures, the authors of RISC-V would disagree with you that their approach is compromising performance.