MurphyA/hacker-news huggingface dataset:
by alnewkirkcom | 2025-08-31 00:26:00+00:00
"Collaborate by Contract" (CBC) is my framework; it's new, and I'm publishing it piece by piece. It's not an "industry standard" yet, but it's more than theory: it's how I've learned to get execution discipline in teams where vague goals and shifting priorities are the default. It doesn't need to be practiced by the entire org; as with any other type of agreement, you just need two willing participants.

At the simplest level:

A CBC agreement is a short written contract between leaders and reports. Ideally, person to person, but leader and team is fine too. It defines the objective, deliverables, dependencies, expectations, and outcomes (i.e., success criteria). Work doesn't start until all parties agree.

A journal of contracts is just the running log of those agreements. Think of it as the team/dept/org's public ledger, what was agreed, by whom, when, and why, and ideally the artifact captures the negotiations and tradeoffs made to arrive at the final agreement. Patterns show up quickly (who delivers, who misses, where scope creep hides). This makes performance reviews objective and enables meritocracy.

Okay, things change, and sometimes new info emerges: agreements aren't stone tablets. So, agreements might include predefined checkpoints or "if/then" clauses. Instead of pretending we never change, CBC forces us to renegotiate in daylight, with both sides explicit about the cost of changing.

What leaders commit to: clarity, timely decisions, and removing dependencies. If a leader misses their side, say they don't secure the promised resource or they blow their own deadline, that's a contract miss just like an IC failing to deliver code. Also, by signing the agreement, the leader is sayin,g "I agree with this plan/strategy." In CBC, credibility runs both ways.

It's early, and I'm still publishing examples and tooling. But the premise is simple: if you can't write it down, negotiate it, and sign it, it's not really a commitment, it's just vibes.

Also, no, it's not Waterfall, because it's more about documenting "expectations" and "outcomes" than about specifying particular work activities.

cc quag
by AnthonyMouse | 2025-08-31 00:26:06+00:00
It isn't the client side who does this, it's the server side. Doing it on the client side has a nominal benefit in the typical case but is very little value to you when the problem is some misbehaving third party AI scraper taking down the server when you need to get something from it that isn't already in the local cache.

If you have three local machines, you might be able to turn three queries into one, assuming they all visit the same site instead of different people using different sites.

If you do this on the server, a request that requires the execution of PHP code and three SQL queries goes from happening on every request for the same resource to happening once and then the subsequent requests are just shoveling the cached response back out the pipe instead of having to process it again. Instead of reducing the number of requests that reach the back end by 3:1 you reduce it by a million to one.

And that doesn't cause any HSTS problems because a reverse proxy operated by the site owner has the real certificate in it.
by vidarh | 2025-08-31 00:27:01+00:00
Americans pay first through taxes, and then again through insurance, so it's even worse. Medicare+Medicaid cost about as much per capita as the UK's NHS, in part because they have intentionally been barred from being as efficient as possible, with e.g. limitations on using their negotiating power.

As for ease of doing it: At least several European systems does delivery via private actors, at least one has decentralised the insurance (Germany), several has segmented the public delivery in regional or local trusts or similar (UK, Norway). In other words: Universal coverage doesn't mean a single top down healthcare system, not is that necessarily desirable. E.g. the UK model uses trusts that prevents failure of leadership in one organisation from causing the whole to fail, and let's trusts get put under alternative management if they underperform.

If anything, the EU is a demonstration of how it is possible to do in a heterogeneous way across a much larger population than the US.
by malkia | 2025-08-31 00:27:57+00:00
^^^ - This - my recent one, came to the realization that dealing with memory mapped files is much harder without exceptions (not that exceptions make it easier, but at least possible).

Why? Let's say you've opened a memory mapped file, you've got pointer, and hand this pointer down to some library - "Here work there" - the library thinks - oh, it's normal memory - fine! And then - physical block error happens (whether it's Windows, OSX, Linux, etc.) - and now you have to handle this from... a rather large distance - where "error code" handling is not enough - and you have to use signal handling with SIGxxx or Windows SEH handling, or whatever the OS provides

And then you have languages like GoLang/Rust/others where this is a pain point (yes you can handle it), but how well?

If you look in ReactOS the code is full with `__try/__except` - https://github.com/search?q=repo%3Areactos%2Freactos+_SEH2_T... - because user provided memory HAVE to be checked - you don't want exception happening at the kernel reading bad user memory.

So it's all good and fine, until you have to face this problem... Or decide to not use mmap files (is this even possible?).

Okay, I know it's just a silly little thing I'm pointing here - but I don't know of any good solution off hand...

And even handling this in C/C++ with all SEH capabilities - it still sucks...
by kavout | 2025-08-31 00:28:09+00:00
We just launched a new research agent called Global Market Outlook that provides real-time momentum analysis across global equity markets (US, Canada, Europe, UK, China/HK, and India). The Problem: Most retail traders make decisions with limited market context. They might analyze individual stocks thoroughly but miss the bigger picture - that 70%+ of a stock's movement is driven by overall market direction. Trading against the prevailing market trend is statistically one of the biggest reasons for trading losses. What We Built: Global Market Outlook processes real-time data streams from multiple exchanges and provides:

Live momentum indicators and trend analysis for each market Cross-market correlation analysis (important given how interconnected global markets are) Early warning signals for momentum shifts Unified dashboard to monitor all 6 markets simultaneously

Technical Approach: The agent uses a combination of price action analysis, volume patterns, market breadth indicators, and inter-market relationships to identify momentum shifts. It's designed to catch regime changes early - when markets transition from risk-on to risk-off (or vice versa). Why This Matters: In today's markets, what happens in Asia overnight affects US markets the next day. European banking stress can trigger global selloffs. Having a real-time pulse on global momentum helps traders:

Avoid taking positions against strong market headwinds Size positions appropriately based on market conditions Identify divergences between markets that often signal opportunity

This joins our suite of AI-powered research agents (technical analysis, fundamental analysis, news sentiment, trade spotting) as part of our broader platform for democratizing institutional-grade market intelligence.
by koverstreet | 2025-08-31 00:28:34+00:00
> To some extent drawing clear boundaries is good as a last resort when people cannot agree, but it can't be the main way to resolve disagreements. Thinking in terms of who owns what and has the final say is not the same as trying to understand the requirements from the other side to find a solution that works for everyone.

Agreed 100%. In an ideal world, we'd be sitting down together, figuring out what our shared priorities are, and working from there.

Unfortunately, that hasn't been possible, and I have no idea what Linus's priorities except that they definitely aren't a bulletproof filesystem and safeguarding user data; his response to journal_rewind demonstrated that quite definitively.

So that's where we're at, and given the history with other local filesystems I think I have good reason not to concede. I don't want to see bcachefs run off the rails, but given all the times I've talked about process and the way I'm doing things I think that's exactly what would happen if I started conceding on these points. It's my life's work, after all.

You'd think bcachefs's track record (e.g. bug tracker, syzbot) and the response it gets from users would be enough, but apparently not, sadly. But given the way the kernel burns people out and outright ejects them, not too surprising.
by tombert | 2025-08-31 00:29:07+00:00
Web frameworks for me are one of those things that's "great until it isn't".

If you're making a simple app then web frameworks can feel downright magical (like the original "Build a blog in 15 minutes with Rails" demo [1]), but for anything that gets even remotely complicated, I find that they generally just get in the way.

I personally have grown to prefer the "mid-level" HTTP setups, like Express with Node.js or Vert.x with Java.

[1]
by khimaros | 2025-08-31 00:30:26+00:00
i'm not one for internet arguments and really just want solutions. maybe you could point me at the details for a setup that worked for you?

based on my own testing, dm has a lot of footguns and, with some kernels, as little as 100 bytes of corruption to the underlying disk could render a dm-integrity volume completely unusable (requiring a full rebuild) https://github.com/khimaros/raid-explorations
by sublinear | 2025-08-31 00:30:34+00:00
I'm coming from the perspective of real world business concerns, not hobby projects.

It's inevitable that you will need to host the pages somewhere else like a CDN to lower latency, integrate with other backends, and the biggest one is allowing the frontend devs to have complete control of the HTML so that stylesheets and javascript don't randomly break for reasons out of their control. They should be able to develop everything locally with mocks instead of your server and use whatever build tools and frameworks they want. There are also SEO and accessibility concerns with the page structure. The backend devs should not be making decisions about any of that. Sometimes the client may want quick turnaround on simple but very specific changes to the pages. None of that process should depend on backend teams who don't care and will drag ass about it because they will have to refactor their junky code that hasn't been touched in years.

Getting rid of dependencies and having good boundaries in the code that align with the way dev teams are organized is always a good thing. I'm not sure why anyone would go for SSR unless they haven't done web dev in a while or are working on a legacy project. Even if this starts out as a hobby project, you need to keep things clean for future maintainers.
by magicalhippo | 2025-08-31 00:32:25+00:00
> XFS is quite a bit better than btrfs, and I believe ZFS, because they have a ton of ways to reconstruct from redundant metadata if they lose a btree root

As I understand it ZFS also has a lot of redundant metatdata (copies=3 on anything important), and also previous uberblocks[1].

In what way is XFS better? Genuine question, not really familiar with XFS.

[1]: https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSMetadata...
by rsync | 2025-08-31 00:33:37+00:00
A fools errand.

No matter how effective this list is, the settings will either revert, change, or be silently undone.

New settings will alter the efficacy of the old ones.

Existing settings will disappear.

The behavior you hoped to configure changed to its opposite.

Remember: there was one morning when we all woke up and saw every dns query sent to cloudflare doh by default, and with no opt-in.
by refurb | 2025-08-31 00:34:39+00:00
It’s statements like these that remind me to not take social media so seriously.

China does not have “very high grow momentum”, in fact growth has been seriously slowing since Covid

I’m not sure sure what “growth momentum” is what it has to do with living standards.

China’s PPP is not more comfortable than the US because it’s still 1/4th that of the US.

China has very serious growth problems, a massive debt overhang from real estate (that is still slowing the economy), a supply planning model that is leaving it with an oversupply of things like cars and batteries.
by verdverm | 2025-08-31 00:35:21+00:00
The PDS is closer to the Mastodon account and will run you the same amount of money. The relay or appview is what takes the load when one of your posts goes viral, whereas in mastadon your $5 VPs has to handle that spike in traffic. Been several a story about how AP has DDoS'd a small server because there is no equivalent to the relay
by AnthonyMouse | 2025-08-31 00:35:51+00:00
> Even SMTP is de facto centralized due to the spam problem.

It's important to note that this isn't "you have to be big in order to be able to filter spam". That's not true at all; decentralized anti-spam lists have been a thing for decades and the big sites don't have any significant advantage in filtering spam.

It's allegedly that big sites will mark small sites as spam even when they're not, which makes it hard to run a small mail server. And there is some of that -- they also have a perverse incentive to do it on purpose because it kills their smaller competitors.

But it's also somewhat overstated. If you have a reverse DNS entry pointing back at your mail server and have properly configured DKIM, it's not inherently the case that you're always going to be marked as spam. And it's not inherently the case that you won't just because you use one of the big services -- they have the same incentive to do that to each other, after all.
by pathartl | 2025-08-31 00:35:53+00:00
For some behind the scenes on Microsoft's QA and Dev I recommend people read "Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft". These days it's almost an ancient text, but it highlights a time in which computing was more fragile and the monumental challenge that comes with writing an operating system.

I think MS should be more transparent about their QA process, as I can only imagine how complicated it can be. I think we're past the era (mostly due to the high level of abstraction that exists between hardware and most end user facing software these days) where hardware variation has THAT amount of effect on the overall stability of a system, but we're also in an age where automation and reporting is actually mature.

So many of these controversies come from anecdotal scenarios that really should be treated woth
by alehlopeh | 2025-08-31 00:36:34+00:00
Hurricane categories just mean that winds are above a certain threshold. For cat 5 I think it’s 157mph, and that means if the hurricane has winds of eg 170mph it’s still a category 5.

Another problem with this system is that some category 2 or even 1 hurricanes can cause incredible devastation, depending on where they hit. But people see category 1 and they assume it’ll be nothing.
by squigz | 2025-08-31 00:36:52+00:00
> You want to start a plumbing business? Work hard 5-10 years, get out on your own with a van and tools and you have a turn key business idea. Provide good service at a proper rate. End of story.

This strikes me as underselling the hurdles here. Ignoring the whole "just start a self-sufficient business" thing, what happens when you get sick? What about medical costs as you age? Retirement plans?
by refurb | 2025-08-31 00:37:54+00:00
What do you mean “the rest of the world will take up the slack”?

Is the rest of the world suddenly going to start buying something they haven’t in the past? Why?

And the US consumer market is 2x the size of the next biggest (EU).

How exactly is the the rest of the world going to replace the demand of something several times its size?
by trehalose | 2025-08-31 00:38:33+00:00
That's not what the proposed change is about. (It's about replacing the scale with a different one that takes into account flooding and other dangers that better reflect the likelihood of fatalities than just wind speed alone. Category 1 hurricanes can sometimes be more dangerous than higher-category hurricanes under the current scale.) I worry that people might not take this seriously because they assume this is a frivolous rebranding to "market" climate change.
by williamstein | 2025-08-31 00:41:06+00:00
It can be useful to create a file server with one filesystem/subvolume per user, because each user has their own isolated snapshots, backups via send/recv are user-specific, quotas are easier, etc. If you only have a few hundred users, ZFS is fine. But what if you have 100,000 users? Then just doing "zpool import" would take hours, whereas mounting a btrfs filesystem with 100,000 subvolumes takes a seconds. This complexity difference was a show stopper for me to architect a certain solution on top of ZFS, despite me personally loving ZFS and having used it for a long time. The btrfs commands and UX are really awkward (for me) compared to ZFS, but btrfs is extremely efficient at some things where ZFS just falls down.

The main criticism in this thread about btrfs involves multidisk setups, which aren't relevant for me, since I'm working on cloud systems and disk storage is abstracted away as a single block device.
by danabramov | 2025-08-31 00:41:13+00:00
This makes sense, but a Relay isn't something you'd expect a normal user to run.

It doesn't meaningfully make you "more independent" because all Relays are trivial (they're just dumb re-broadcasters of a stream) and it makes sense to use one run by somebody else — a company or a community that's pooling resources.
by Animats | 2025-08-31 00:41:24+00:00
The actual report is four links down and paywalled.[1]

Their source for future estimation is apparently Google Trends tallies of searches for trade schools.

Actual growth over the last few years is 3.2% per year, from 2019 to 2024.

US population growth is about 0.5% per year, so deduct that.

Always look for the actuals.

[1] https://validatedinsightstradeschools2.carrd.co/
by verdverm | 2025-08-31 00:42:19+00:00
https://roost.tools is working on open-source options for both social (fedi or not) and beyond social. Generally the idea is that we can fight the bad things better if we are working together instead of independently

ATProto's Stacked Moderation is an interesting approach to combine platform, community, and user level choices

https://bsky.social/about/blog/03-12-2024-stackable-moderati...
by kragen | 2025-08-31 00:42:20+00:00
Nobody has any idea what AI is going to look like five years from now. Five years ago we had GPT-2; AI couldn't code at all. Five years from now AI might still break down at even a small bit of complexity, or it might be installing air conditioners, or it might be colonizing Mercury and putting humans in zoos.

Anyone who tells you they know what the future looks like five years from now is lying.
by Nextgrid | 2025-08-31 00:42:44+00:00
Presumably people who are on the verge of death and beyond any kind of proven treatments. They're technically alive but have a very short predicted lifespan.

You can try a novel treatment on those but at the same time are limited by ethical concerns regarding pain and future survival (if the transplant "works", you are now in a tricky situation, as you can't easily do anything that has the potential to make the situation worse... and given it's uncharted territory, anything has the potential to make it worse).

Brain-dead people don't have such limitations. You don't have to worry about causing pain nor shortening potential survival, so you can try things that are likely to "kill" them (cause the transplant to fail, or other issues) and learn from the outcomes.
by williamstein | 2025-08-31 00:42:52+00:00
Incidentally, the application I'm reworking to use btrfs is cocalc.com. One of our main use cases is distributed assignments to students in classes, as part of the course management functionality. Imagine a class with 1500 students all getting an exact copy of a 50 MB folder, which they'll edit a little bit, and then it will be collected. The copy-on-write functionality of btrfs is fantastic for this use case (both in speed and disk usage).

Also, the out-of-band deduplication for btrfs using https://github.com/Zygo/bees is very impressive and flexible, in a way that ZFS just doesn't match.
by ori_b | 2025-08-31 00:43:01+00:00
Not copy pasting code also makes it harder to change the system correctly at some point later on, because you transformed a local decision ("does this code do what the caller needs?") onto a global one ("does this code do what any possible caller needs, including across code maintained by other teams?")

There's no one rule. It takes experience and taste to make good guesses, and you'll often be wrong even so.
by 1659447091 | 2025-08-31 00:43:42+00:00
> The fact remains that the P320 malfunctions.

This is why I came around to appreciating the California Roster of Handguns regulation. Firearm manufacturers should be held to a higher safety standard.

Originally I thought it was ridiculous that my first conceal carry sub-compact Springfield XD-S came in a case with a large sticker across one side saying it was illegal in CA. At which point I learned about the stringent drop, firing and performance test that was required and how manufacturers will make a separate and specific quality and safety upgrades to the model variant legal in CA. After a fair amount of use I understood why the XD-S was not and is still not legal in CA. Mine had a higher-than-I-am-comfortable-with rate of jamming. I'll be buying CA approved firearms from now on.

Interesting info about the P320 M18:

The P320 M18 has 3 variants: 320CA-9-M18-MS, 320CA-9-M18-MS-10, 320CA-9-M18-MS-CA.

The 320CA-9-M18-MS-CA is the only one legal in CA [0]

According to Sig Sauer site wording, the CA tested version came after the version issued to the military -- thus I am taking a guess that t was not as rigorously tested as the CA version (and probably has fewer safety or other military specific features that make it less reliable)

[0] https://www.oag.ca.gov/firearms/certified-handguns/search?ma...
by kyle-rb | 2025-08-31 00:44:05+00:00
No I think ATProto is "built this way". The firehose is just the output of the Relay. If Bluesky wanted to shut off the firehose, they would have to make changes to ATProto or stop conforming to ATProto.

I understand that Bluesky's conformance to ATProto is just a promise, but it's a better promise than you get from most websites. Also in the meantime, if you migrate to a self-hosted PDS, you can ensure that even if Bluesky restricts access to their Relay's firehose, 3rd party Relay servers can still pick up your posts and publish their own unrestricted firehose.
by trehalose | 2025-08-31 00:44:33+00:00
That's not what this is. (The person you're responding to didn't read the article.) They're not looking to add a "total-er destruction" category; they're looking to replace the current scale with one that takes into account more factors than just wind speed, such as storm surge and flooding. Under the current scale, a category 1 hurricane can be deadlier and more destructive than a higher-category hurricane. They want to use a different scale that better indicates the dangers. It goes up to 6 when multiple factors rate 5 on each factor's specific scale under the proposed system.

I think the title of this article is misleading and clickbaity. :/